Stage-Gate Process (Cooper)

1. Overview

The Stage-Gate process, developed by Dr. Robert G. Cooper, is a comprehensive product innovation and management framework that has become a cornerstone of new product development (NPD) for many of the world’s most successful companies [1]. It serves as a structured roadmap for guiding a new product project from its initial idea to a successful launch, with the goal of improving the effectiveness and efficiency of the innovation process. The process is designed to improve the effectiveness and efficiency of product development by breaking it down into a series of manageable stages, punctuated by decision-making gates. This systematic approach ensures that projects are continuously evaluated for their business value, technical feasibility, and market relevance, thereby mitigating risks and maximizing the return on investment. The Stage-Gate model has become an industry standard, widely adopted by organizations across various sectors to bring discipline, clarity, and a higher success rate to their innovation initiatives [2].

At its heart, the Stage-Gate process is a risk-management tool. It is based on the premise that innovation is inherently risky, but that this risk can be managed by breaking down the development process into a series of smaller, more manageable steps. At each step, the project is evaluated, and a decision is made whether to continue investing in it. This incremental approach to investment ensures that resources are not wasted on projects that are unlikely to succeed. The framework is also designed to be flexible and adaptable, and can be tailored to the specific needs of the organization and the project [3].

2. Core Principles

The Stage-Gate process is founded on a set of core principles that are integral to its success. These principles are not merely theoretical constructs but are based on extensive research into what makes new products successful. The six key principles are:

1. Optimize the Entire Innovation Process: The Stage-Gate model provides a holistic view of the innovation journey, from ideation to post-launch review. This end-to-end perspective helps teams anticipate challenges, manage risks, and align their efforts with strategic goals. It brings visibility to what can often be a chaotic and creative process, enabling teams to contribute more effectively [2].

2. Embrace Risk by Managing It: Innovation is inherently risky. The Stage-Gate process encourages calculated risk-taking by breaking down the development process into smaller, more manageable stages. Investment and commitment increase incrementally as more information is gathered and uncertainties are reduced. This allows organizations to take on more ambitious projects without exposing themselves to an unacceptable level of risk [2].

3. Accelerate the Creative Process: Contrary to the misconception that processes stifle creativity, Stage-Gate is designed to foster it. By providing a clear framework and common language, it enables cross-functional teams to collaborate effectively and focus their creative energies on developing winning solutions. The process allows for iterations within stages, driven by the project management methodology of choice, such as Scrum or PMBOK [2].

4. Options-Based Decisions: The gates in the Stage-Gate process are not just project reviews; they are decision points where the organization has the option, but not the obligation, to continue investing in a project. This allows for agility and the ability to reallocate resources to more promising initiatives. This is a critical element of the process, as it allows the organization to kill projects that are no longer viable, and to redirect resources to those that have a higher probability of success [2].

5. Activate Performance Through Visibility: The Stage-Gate process brings visibility to the entire innovation pipeline. This transparency enables better decision-making at all levels, from project teams to senior executives, and facilitates a more agile and responsive approach to portfolio management. This visibility is key to driving a high-performance, strategically driven innovation pipeline [2].

6. Culture of Accountability and Discipline: The framework fosters a culture of accountability by clearly defining roles, responsibilities, and expectations. It also instills discipline by requiring teams to complete a prescribed set of tasks in each stage before moving on to the next. This creates a common language and framework that helps to coordinate, collaborate, and manage the expectations of all stakeholders [2].

3. Key Practices

The Stage-Gate process is characterized by a set of key practices that bring its principles to life. These practices are the building blocks of the framework and are essential for its effective implementation.

• Stages: The development process is divided into a series of discrete stages, typically five, each with a specific set of prescribed and parallel activities. These activities are designed to gather the information needed to make sound decisions at the next gate. The stages are cross-functional, and the activities are completed in parallel by a team of people from different functions [1].
• Gates: Between each stage, there is a gate, which serves as a decision point. At each gate, a cross-functional team of senior managers (the gatekeepers) reviews the project’s progress and makes a go/kill decision. This ensures that resources are allocated to the most promising projects. The gates are structured meetings with a fixed agenda, and the decisions are based on a set of predefined criteria [1].
• Deliverables: For each gate, there is a predefined set of deliverables that the project team must produce. This ensures that the gatekeepers have the information they need to make an informed decision. The deliverables are based on the work that was completed in the previous stage, and they are designed to provide a comprehensive overview of the project’s status [1].
• Criteria: Each gate has a set of clear and transparent criteria against which the project is judged. These criteria typically include both business and technical measures. The criteria are used to assess the project’s attractiveness and its probability of success. They are designed to be objective and to ensure that all projects are evaluated on a consistent basis [1].
• Cross-Functional Teams: The Stage-Gate process emphasizes the use of cross-functional teams, with members from different departments such as marketing, R&D, and manufacturing. This ensures that all aspects of the project are considered and that there is buy-in from all stakeholders. The team is responsible for the project from beginning to end, and it is empowered to make decisions and to take action [1].

4. Application Context

The Stage-Gate process is a versatile framework that can be adapted to a wide range of application contexts. It is most commonly used for the development of new physical products, but it can also be applied to the development of new services, software, and even business processes. The framework is scalable and can be tailored to the specific needs of the organization and the project. For example, a more streamlined version of the process can be used for low-risk projects, while a more rigorous version can be used for high-risk, complex projects [4].

The framework has been successfully implemented in a wide range of industries, from consumer goods and industrial products to financial services and healthcare. It is used by both large multinational corporations and small and medium-sized enterprises. The key to successful implementation is to adapt the framework to the specific context of the organization and the project. This may involve modifying the number of stages and gates, the deliverables and criteria, and the composition of the project teams [5].

5. Implementation

Successful implementation of the Stage-Gate process requires a systematic and well-planned approach. The following are the key steps in implementing the framework:

1. Define the Stages and Gates: The first step is to define the stages and gates of the process. This should be done in consultation with all stakeholders to ensure that the process is tailored to the specific needs of the organization. The number of stages and gates will depend on the complexity and risk of the projects that the organization undertakes [4].
2. Define the Deliverables and Criteria: For each gate, the deliverables and criteria must be clearly defined. This will ensure that the decision-making process is transparent and consistent. The criteria should be a mix of financial and non-financial measures, and they should be aligned with the organization’s strategic goals [4].
3. Establish the Gatekeepers: The gatekeepers, who are responsible for making the go/kill decisions, must be identified and their roles and responsibilities must be clearly defined. The gatekeepers should be senior managers with the authority to allocate resources and to make decisions that will have a significant impact on the organization [4].
4. Train the Teams: All project teams must be trained on the new process to ensure that they understand their roles and responsibilities. The training should cover all aspects of the process, from the stages and gates to the deliverables and criteria. It should also include training on the tools and techniques that will be used to manage the projects [4].
5. Pilot the Process: It is often a good idea to pilot the new process on a small number of projects before rolling it out to the entire organization. This will allow for any issues to be identified and addressed before the full-scale implementation. The pilot should be carefully monitored and evaluated to ensure that the process is working as intended [4].

6. Evidence & Impact

The Stage-Gate process has a proven track record of success. Numerous studies have shown that organizations that use the framework have higher success rates for new products, shorter cycle times, and a better return on their R&D investments. For example, a study by the American Productivity & Quality Center (APQC) found that 88% of U.S. firms use a Stage-Gate process for their new product development. These companies reported significant benefits, including a 30% reduction in cycle times [1].

A more recent study by the Product Development and Management Association (PDMA) found that companies that use a formal NPD process, such as Stage-Gate, have better new product performance than those that do not. The study also found that the use of a formal process is associated with a number of other benefits, including improved cross-functional teamwork, better project selection, and a stronger market orientation [6].

7. Cognitive Era Considerations

While the Stage-Gate process originated in the industrial era, it has been adapted to remain relevant in the cognitive era. The latest versions of the framework incorporate principles from agile development, such as iterative development and rapid prototyping. This allows for greater flexibility and responsiveness to changing market conditions. The integration of digital technologies and data analytics into the Stage-Gate process can further enhance its effectiveness by providing real-time insights and enabling more data-driven decision-making [7].

The Agile-Stage-Gate hybrid model is a promising new approach that combines the strengths of both methodologies. It uses the Stage-Gate framework for the overall governance of the project, but it incorporates agile principles and practices into the stages. This allows for a more iterative and adaptive approach to development, while still providing the discipline and control of the Stage-Gate process. The benefits of this hybrid model include a faster and more adaptive response to changing customer needs, better integration of the voice of the customer, improved team communication, and faster time to market [8].

8. Commons Alignment Assessment

The Stage-Gate process has a moderate alignment with the principles of the commons. While it promotes collaboration and knowledge sharing within the organization, it is primarily a proprietary framework that is designed to create a competitive advantage for the firm. The framework is owned by Stage-Gate International, and organizations must pay a license fee to use it. This limits its accessibility and its potential to be used for the development of common goods and services.

However, the principles of the Stage-Gate process can be applied in a more open and collaborative manner to support the development of common goods and services. For example, the framework could be used to manage open-source projects or to develop new technologies that are freely available to the public. The key is to adapt the framework to the specific context of the project and to ensure that it is used in a way that is consistent with the principles of the commons.

9. Resources & References

[1] Stage-Gate International. “The Stage-Gate Model: An Overview.” https://www.stage-gate.com/blog/the-stage-gate-model-an-overview/

[2] Stage-Gate International. “The 6 Principles of Stage-Gate.” https://www.stage-gate.com/blog/6-principles-of-stage-gate/

[3] Cooper, R. G. (1990). Stage-gate systems: a new tool for managing new products. Business Horizons, 33(3), 44-54.

[4] Cooper, R. G. (2008). Perspective: The Stage-Gate® Idea-to-Launch Process—Update, What’s New, and NexGen Systems. Journal of Product Innovation Management, 25(3), 213-232.

[5] Edgett, S. J. (2015). Idea-to-Launch (Stage-Gate®) Model: An Overview. In Encyclopedia of Creativity, Invention, Innovation and Entrepreneurship (pp. 995-1001). Springer New York.

[6] American Productivity & Quality Center. (1996). Benchmarking in new product development: The best of the best. Houston, TX: APQC.

[7] Sommer, A. F., Hedegaard, C., Dukovska-Popovska, I., & Steger-Jensen, K. (2015). Improved product development performance through agile/stage-gate hybrids. Research-Technology Management, 58(1), 34-44.

[8] Cooper, R. G., & Sommer, A. F. (2016). The agile–stage-gate hybrid model: a promising new approach and a new research opportunity. Journal of Product Innovation Management, 33(5), 513-526.