One of the greatest challenges in the ever-changing world of IT is to create and maintain an innovation culture and align innovation activities with company strategy. This book provides a fresh perspective on innovation management activities in an IT environment using examples from both start-ups and established companies such as Cisco, Ericsson Nikola Tesla, Lufthansa Systems, Worldline, Amdocs, Telefonica and Enea.
This book addresses the following issues:
The software development environment offers many possibilities for innovation, yet also places some constraints on the innovation process at the same time. It considers how this can be bypassed to bring success to the company.
It is a challenge to create and maintain an innovation culture using an agile process in the area of software development with its short cycles. This book describes how to bring innovation challenges closer to developers and use their experience and vision to create new projects.
It also shows how to inspire software engineers using incremental and often small but useful money-saving improvements.
The fourth industrial revolution changes companies from the inside and brings changes to common agile product management processes in IT. This book examines the effects on innovation management and what mechanisms are used for success in this new environment.
Software innovation, like almost every other kind of innovation, requires the ability to collaborate and share ideas with other people, and to sit down and talk with customers and get their feedback and understand their needs.
âBill Gates
Information technology has had a high growth rate for years and there is a reason for that: a constant flow of innovations in technology, but also in business processes, as growing competition on the market has made innovation a must for every organisation.
On the other side, the top skills missing among job applicants1 in the current world are problem solving, critical thinking, innovation and creativity.
In the ever-changing world of IT, it is challenging to create and maintain innovation activities. With more than ten years of experience working in three different companies as an innovation manager, I will try to give a fresh perspective on innovation management in the IT environment and show examples from companies all over the world. A software development environment provides many possibilities for innovation, but also puts some constraints on innovation processes that can be bypassed, bringing success to the company and innovators.
Using the agile process in the area of software development with its short cycles, it is a challenge to create and maintain an innovation culture. With this in mind, the following questions are raised:
How to bring innovation challenges closer to developers and use their experience and vision to create new projects? How to set up fast and clear focus topics or customer challenges oriented toward new business ideas? On the other hand, how to inspire developers about incremental, often small but useful and money-saving, improvements?
As I mentioned, Iâve been working in innovation management for more than a decade. In that time, I was involved in creating an innovation programme using a new reward system that successfully increased innovation results. The next big topic was the creation of specially tailored innovation activities for a customer-oriented software company. Product innovation was also part of my efforts, but I will come back to all these topics later. Now, letâs see what place innovation has in IT companies.
The environment in a software company is much different than in other industries and most tools and activities, which are common in other industries, must be either adapted or totally neglected.
Letâs start with people. Software engineers, developers, coders, or however you call them, are a bit different from âordinaryâ people. They are in deep in thought, donât like disturbing meetings and they often have short-term milestones which makes them people who havenât got too much time to think âoutside of the boxâ. Hence, the shape of every innovation initiative has to be carefully adapted to this special environment.
Processes are also a bit different than in other industries. Planning is done differently, and the time to deliver the new product is shorter as all process stages are shorter.
Deadlines in the agile world are focused on a short-term pace instead of a long-term time cycle in a waterfall system or in other industries. These make life easier, but can prevent innovation as shorter cycles could mean less or no time for ideas.
Sometimes it looks like we are working in a zero-defect culture where no errors are expected, as we are concentrated on new incremental improvements, but innovations need a different error-tolerant environment to allow for breakthrough ideas.
In addition, the export of software is done differently. When a customer buys the software, it is not necessary to ship it with trucks, trains, ships or planes. The customer just needs access to the latest release versions and the user rights to download it. There is no direct contact with the customer, no physical stores or warehouses, just websites and servers.
What is very positive in this industry is that here the most common thing is change, which is really important for innovation. Software engineers are used to changing direction, projects, tasks and technologies; hence establishing innovation ecosystem should not be a too hard a job. Software engineers must educate themselves and constantly be ready for change. So, the future where there will be no more workers but only creatives is ideally shaped for todayâs IT workers.
In a time when itâs not so difficult to launch a product, but itâs extremely difficult to achieve success with it, product managers are key figures in starting and maintaining innovation activities.
The product managerâs view
Now, letâs look at what is important to software product managers, here is an insight from a survey of 40 product managers in a software company (done with a colleague, Denis Faivre). They were asked to indicate how important (or not) they consider several tools and techniques related to innovation and product management, and whether they would do more (or less) of them.
From the answers shown in Figure 1.1,2 we can see that the activities seen as most important are input from the front line, customer interviews, customer workshops and market watch. We classify these as the most important practices in customer and market intimacy group (black dots), in which we also include insight from fairs and trade shows. Together, these are insights that make a direct connection with customers and the market as fast feedback on the companyâs activities.
Figure 1.1: Practice of innovation-related activities.
Next come competitive intelligence, tech watch, market research, trend spotting and strategic workshops in strategic insights group (green dots). These are insights that could be taken from externals, but also from internal experts or strategic groups.
Quick prototyping, innovation workshops, ideation workshops, idea challenges, internal co-creation, external co-creation and design sprint make up the innovation management tools group (grey dots). This group is connected with the usual activities of an innovation manager.
The next group is less popular: profitability assessment, portfolio assessment, insights from research and academia, focus group, hackathon and insights from consulting. This is connected to internal and external tasks and connections.
Finally, we find a smoke test and patent watch, with a very low score: these practices seem to be not important to product managers who filled the survey. It would be interesting to investigate whether this results from a lack of knowledge, interest, or effectiveness.
However, this survey shows that product managers gave most trust to:
customer and market insights and research
technology and strategic insights
innovation management specific activities
external connections and internal focus groups
All four groups are directly related to innovation activities and are part of them in a larger or smaller way; and all are important in setting up the innovation ecosystem in any IT company. Product managers can change their thoughts after successful practices in organisation, but they will surely always state that the most important practice is a connection to the customer and market â so, this should be the most important aspect of every innovation activity.
However, the most important asset in this industry is people; but can people be grouped by some kind of creative perspectives?
People: I, T or X?
I first heard for âT-shapedâ people when reading Tom Kelleyâs book The Ten Faces of Innovation3 where he described them as:
They enjoyed a breadth of knowledge in many fields, but they also have depth in at least one area of expertise.
âT-shapedâ people have skills with depth in many areas; the vertical bar in the âTâ refers to expert knowledge which a person has in his or her âmainâ area, while horizontal means the ability to be open to thinking in other disciplines and to be open to using that knowledge. âT-shapedâ people are great fellow workers, they will collaborate, communicate. In the IT sector, these people are ideal, as they have in-depth knowledge of their main tasks, but also the ability to understand the needs of other areas.
On the other hand, âI-shapedâ people are mainly skilled in depth only in one direction, like a developer with expertise in one programming language, which is needed for her job. These people also fit into the IT world, but they would need to educate themselves because of the challenges of the future. Such people are passing the usual scans of recruiting and hiring processes, but later they could find it hard to adapt to future challenges.
âX-shapedâ persons have leadership skills as they have subject knowledge of their subject and credibility, but also the skills to lead and support teams. Great managerial candidates.
âTree-shapedâ people have deep knowledge and experience in many areas. They have knowledge in the core area, but also a background in other fields, which makes them the best problem solvers.
In an innovation or creative process, these skills take their place and could fit several roles. It could be quickly noted inside of innovation teams which people have the skills to collaborate, think differently, the ability to lead or connect the dots and solve problems. It is very important to know people, but wouldnât this be too late? Maybe this should be done when people are hired. Many companies take care of various skills during employment, but many donât, as they just hire developers with the one currently needed skill, which will solve their current needs. Many companies are in constant need of a group of developers, which should be hired ânowâ and they donât care too much about all the skills people have; they certainly donât detect them.
It is said that to have a high IQ without social skills is the same as having the super-fast computer without an internet connection.
Therefore, âT-shapedâ people can look at the task from another point of view, and as they have skills from other areas, they can be inspired and flown into the challenges for topics that are not their main area, a very interesting characteristic for future innovation tasks.
How to transfer people from I to T?
Job rotations or trainings could widen the perspective of people, but they must voluntarily step out of their comfort zone. They can make this step, but they need to be interested in other topics, reading and communicating to broaden their horizons.
Figure 1.2 shows how different shapes relate to IT and creativity. âI-shapedâ people could be experts in their field, but they would probably generate only improvements from their working field. âT-shapedâ people with expertise across several topics have more of a chance of generating innovations than âI-shapedâ people, as they have a wider perspective and more diverse knowledge. They are also a nice addition to any innovation team. With their leadership skills, âX-shapedâ people could be candidates for managing innovation teams and have grounds to become intrapreneurs. In the end, âtree-shapedâ people have the ability to solve problems with their deep knowledge and experience; they could fit anywhere in innovation activities. They must be recognised and be a part of the innovators community.
Figure 1.2: Different shapes of people according to IT-related skills and creativity-related skills.
Table des matiĂšres
Title Page
Copyright
Contents
Preface
1âIT and Innovation
2âIgniting the Innovation Process
3âThe Fourth Industrial Revolution Will Change Companies From the Inside
4âLife in the Agile World
5âInnovators Inside Companies
6âDevelopment Cycle, Agile Process, Innovation Process
7âReward Programme and Effects of Rewarding
8âBrainstorming as an Ideation Tool
9âLife After Brainstorming
10âFrom Ideation to Realisation
11âIntroverts as the Majority?
12âInspire Developers
13âEnvironmental Effects
14âInnovation Challenges
15âImprovements in Development Environment
16âLife After Agile
17âEvery Engineer Needs a Businessman
18âStartups
19âBe Original
20âMechanisms for Success
21â7innovation Method
22âDo Nothing in Dark Times?
23âTechnology Management
24âThe Effect
Further Reading
About
Thanks
Index
Normes de citation pour Developing Innovation
APA 6 Citation
BuljubaĆĄiÄ, T. (2020). Developing Innovation (1st ed.). De Gruyter. Retrieved from https://www.perlego.com/book/1449268/developing-innovation-innovation-management-in-it-companies-pdf (Original work published 2020)
BuljubaĆĄiÄ, T. (2020) Developing Innovation. 1st edn. De Gruyter. Available at: https://www.perlego.com/book/1449268/developing-innovation-innovation-management-in-it-companies-pdf (Accessed: 14 October 2022).