From product innovation to innovation systems…
...and the role of software
We frequently encounter organizations transforming their innovation systems and organization “on-the-go”. In recent projects we had the situation that traditional, well-doing companies have forgotten how to innovate. Some of these firms date back more than a 100 years and have seen significant phases of growth, all associated with innovations across many types but mostly with new products.
The central role of software platforms
At the portfolio level roadmaps are quickly in focus to find out how core products as well as new services interact with each other. Building complex end-to-end products in a connected world dominated by software is no longer possible in isolated projects but must build upon software platforms that are structured and layered to optimally balance re-use of commercial, open-source and proprietary components.
Coming from organizations dreading software as #1 problem such clients quickly step up to become able to master changes in an agile way. As software is developed as an evolution built on a sound platform basethis thinking will positively influence other disciplines as well.
Business will profit dramatically as the evolutionary cycles will uncover new learnings during the customer journey. Using a proven innovation framework — not just a process — will finally connect strategy, initiatives, product management and development.
From innovation projects to enterprise-wide innovation systems
Once organizations master multiple projects and platform roll-outs we often get the request how to institutionalize the success patterns. Or, how can we act as an innovative organization with a steady stream of ideas, inventions, and innovations? Working in streaming or pipelining mode makes sure the way of success and innovation is not forgotten.
The way to ensure such a working mode is to employ an innovation framework.
In contrast, a process is just part of that. While the framework describes all kinds of activities and capabilities, the software-related aspects differ quite a bit when applied to the discovery and execution phases:
- Discovery is focused on learnings, data and validation of hypotheses through experimentation; the experiments help to define a problem further and quantify an approach. Software applied here relates to low-res prototypes, landing pages, facades or simulated business processes.
- Execution is about adding value to the solution and enhancing it; also here iteration is key to verify the solution does what it must do. Classical agile and DevOps organizations provide the right processes and tools to crank out MVPs, prototypes, solutions for beta-testing and after go-live a continuous stream of versions improving the customer experience.
When working on software innovations a strategy update for the digital world is usually needed as a prerequisite. Once in place software roles regarding different innovation aspects have to be defined and assigned:
- Overall strategy and business model: is software the business itself or just an enabler? Does it need additional sales and support skills once conceived? Are strategic and financial goals aligned?
- Type of innovation strategy: do we need hackers (as in hackathon) or site gurus for existing large scale services? What is the maturity of the solution landscape
- Innovation strategy chosen matching objectives and direction: do developers need to think leading edge or will proven technology achieve the same targets? What is “old” software lacking, and, can it be at least partially be reused? What would an architect with good business judgment tell you?
- Leadership regarding innovation: how do software people drive growth? Is M&A and assessing existing solutions important? What about integration?
- Types of innovations used, potential of new and complementary types: beyond services, business model, operational innovations or hardware complements require different skills than for the existing solution.
- Personas (different innovators at work, predominant culture within the enterprise): last but not least, to uncover needs and to create value calls for learning persona intermixed with building and organizing persona.
In a nutshell, with more projects going “digital”, software reviews, innovation frameworks and systems become more important. Sometimes they get even dominant in terms of pressure for launching and need for new growth.
Click here for the full article on medium.