Adding Agile to Improve Breakthrough Innovation in Product Development

Adding Agile to Improve Breakthrough Innovation in Product Development

Authors: Mitch Beaumont, Ben Thuriaux, Prashanth Prasad, Chandler Hatton, Colin Davies

 

Phase-gate, or waterfall, approaches, which companies have used for the last three decades to improve innovation performance, are being found to hold companies back when it comes to breakthrough innovation. Instead, senior executives in the product- and process-technology companies are turning to agile approaches. To apply the principles of agile, the best tactic is to create a separate path tuned specifically to using those methods.

Tackling the challenges of breakthrough innovation

Business executives have always been under pressure to generate growth, and today’s fast-moving and competitive business environment do not make that any easier. Arthur D. Little’s eighth Innovation Excellence Survey revealed that leading companies expect their share of revenue from a breakthrough, as opposed to incremental, innovation to double over the next five years. However, achieving breakthroughs is easier said than done: we also found that 88% of business leaders were dissatisfied with their breakthrough innovation performances. They have become increasingly frustrated with the limitations of their current innovation systems on producing significant results.The underlying issue for these organizations is usually that they are applying a non-optimal

The underlying issue for these organizations is usually that they are applying a non-optimal innovation approach to realize breakthrough innovation. For the past three decades, most technology-based companies have employed phase-gate (or waterfall) approaches to all of their innovation efforts. In fact, they have made significant investments in the design and adoption of these approaches so they would become rigorous and mechanical. Their fundamental goal has been to minimize variances (i.e., risk) from a well-understood set of requirements and a detailed plan, which are both established at the beginning of a development project. As a result, they have created the perfect environment for incremental innovation, reducing cycle times and improving on-time delivery. Unfortunately, this well-honed model is not conducive to breakthrough innovation, in

Unfortunately, this well-honed model is not conducive to breakthrough innovation, in which requirements are rarely set in stone and uncertainty is not only the norm but a vehicle to explore beyond the usual boundaries.

In the meantime, for the past two decades the information technology and software world has been applying its own, highly dynamic innovation model – the agile approach. For some time agile has been applied almost exclusively to software development, and this has borne fruit: the software industry has consistently produced patents at three times the level of the next-most prolific sectors.

Today, agile approaches are increasingly being deployed alongside phase-gate processes in engineering and R&D functions outside software, with positive results. Arthur D. Little’s research reveals 4 that companies that have successfully added agile methods to their toolboxes, and tailor their innovation approaches by the type of innovation, perform significantly better than those that stick to single waterfall approaches.

 

Want to know more about Customer-Centric changes in the business? Take a look at this infographic!

Key agile principles with a different twist

When applying an agile approach to product development the key agile principles remain the same. However, certain elements take on a different twist.

Iterative approach

 figure 1

The heart of the agile approach in product development is the use of a series of rapid, iterative loops, similar to an agile iteration for software. At the early “exploration” stages of the development lifecycle, each loop focuses on answering a key question that is determined to have a high degree of importance and uncertainty, in order to build a progressively clearer picture of the desired solution. Through these loops, the team is effectively building the user stories. A key artefact of each typically two- to four-week loop is a prototype used to test the part of the concept in question. Prototypes need to be fast and inexpensive – simple mock-ups, models, videos and simulations are appropriate. Prototypes are shared with a sampling of customers, the key questions tested and the learnings assessed to determine if the team can move on to a new objective for the next loop.

Teams

figure 2

Clear roles and responsibilities and the right balance of authority and accountability are important for team success in an agile product development environment. Teams must be nimble and the individual members comfortable with ambiguity and experimentation. In the product development environment, agile teams are multidisciplinary teams of specialists that expand and contract depending on their current focus. This is different from the skills needed to do a technology-feasibility loop. To support this model, agile product development teams are often put together with part-time or limited-time resources. A very small “core” stays constant, and there is a designated team leader throughout the development cycle.

Governance

While governance is not often identified as a key element of agile software development, it is critical within product development. In the agile environment, governance acts less like a go/no-go decision-maker and more like a coach to project teams. Governance also serves to mitigate “organizational antibodies” that try to impede or marginalize breakthrough innovations.

Loop reviews are done at the end of each loop to assess whether the key question has been addressed are discussions between project teams and their governance, using poster boards, prototypes and other visual aids to facilitate the conversation. To enable this environment, it is important that an agile governance group is comprised of individuals who can foster a culture of experimentation and learning, a sense of urgency and agility, and a passion for helping teams jump over hurdles (versus governance being the hurdle itself).

Creating a separate, synonymous path

figure 3

Phase-gate and agile approaches are distinct in their implementation and generally suited to different innovation objectives when applied in the context of companies with engineered products. We see companies adopting two general approaches when trying to introduce agile into an existing phase-gate process: integrating agile into a single innovation process and adding a partly parallel agile path.

Integrating agile into a single innovation process typically involves using iterative loops within the existing phase-gate process, but with the overall structure retained as-is. Our experience is that attempting to integrate approaches will sub-optimize at least one of them. A better solution is to run them side by side, so an organization can apply the right approach across an innovation portfolio of both incremental and breakthrough innovation. In this model, the agile path is the right size to handle the anticipated flow of breakthrough innovation as per a company’s particular innovation strategy, which is usually substantially less volume than the phase path.

Conclusion

figure 4

Breakthrough innovation is increasingly important for companies. However, outside of the software industry most organizations, especially those with complex engineered products and longer development lifecycles, struggle to deliver it systematically. This is principally because the agile approach needed to realize breakthroughs is a challenge to the established practices that have served them well.

 

Like our content? 
Click here and subscribe for more!