Project & Product ManagementintermediateApplied throughout the full product development lifecycleEst. 1990 by Robert G. Cooper

Stage-Gate Process

Also known as: Phase-Gate Process, Cooper's Stage-Gate, New Product Development Process

A product development framework that divides the innovation process into stages separated by gates (decision points), where management reviews progress and decides to go, kill, hold, or recycle the project.

Quick Reference

Memory Aid

Stages do the work. Gates make the decisions. Kill early and cheaply. Only the best survive to launch.

TL;DR

Divide product development into stages separated by gates. At each gate, senior leaders review deliverables against criteria and decide Go/Kill/Hold/Recycle. Kill bad projects early; invest more as risk decreases.

What Is Stage-Gate Process?

Stage-Gate breaks new product development into stages (Discovery, Scoping, Business Case, Development, Testing, Launch). Between each stage is a gate — a decision meeting where senior management reviews the project and decides: Go (continue), Kill (stop), Hold (pause), or Recycle (go back).

The Stage-Gate system is both a conceptual and an operational model for moving a new product from idea to launch. It is a blueprint for managing the new product process to improve effectiveness and efficiency.

Robert G. Cooper, creator of Stage-Gate

Each stage involves cross-functional activities to reduce risk and uncertainty. Each gate has defined criteria (must-meet and should-meet) and deliverables. The process ensures that projects increase in investment as they decrease in risk. Early stages (discovery, scoping) are low-cost explorations; later stages (development, launch) involve larger investments but have lower uncertainty because of the work done earlier. The framework has evolved to include 'agile-stage-gate' hybrids for faster-moving environments.

📊

Stage-Gate Process

Alternating stages (work phases) and gates (decision points) from idea to launch.

Discovery

Ideation

Gate 1

Screen

Scoping

Quick investigation

Gate 2

Go/Kill

Development

Build it

Gate 3

Go/Kill

Launch

Commercialize

Origin & Context

Cooper developed the Stage-Gate system based on research into what distinguishes successful new product launches from failures. Published in 'Winning at New Products.'

Core Components

1

Discovery

Generating and capturing new product ideas.

Example

A company uses customer interviews, trend analysis, and hackathons to generate 200 ideas per quarter.

2

Gates

Decision points where gatekeepers evaluate deliverables against criteria and decide Go/Kill/Hold/Recycle.

Example

At Gate 3 (post-business case), the executive team reviews market analysis, financial projections, and development plans to decide whether to fund full development.

3

Stages

Phases of work where the project team gathers information and does development work.

Example

Stage 3 (Development) involves detailed product design, prototyping, and initial customer testing.

4

Gatekeepers

Senior managers who own the resources and make the go/kill decisions at gates.

Example

The VP of Product, VP of Engineering, and CFO form the gatekeeper team for all new product gates.

💡

Did You Know?

Research by Robert Cooper found that companies using a formal Stage-Gate process achieve 30% shorter development cycles and are twice as likely to launch successful products. Over 70% of leading US product developers use some version of Stage-Gate.

When to Use Stage-Gate Process

Scenario 1

New product development in manufacturing

Problem it solves: Provides a structured process for moving products from idea to launch with appropriate risk reduction.

Real-World Application

Procter & Gamble uses a Stage-Gate process for all new product development, with each gate requiring specific market research, technical, and financial deliverables.

Scenario 2

Managing a portfolio of innovation projects

Problem it solves: Ensures resources are allocated to the best opportunities by killing weaker projects at gates.

Real-World Application

A pharma company manages 50+ drug candidates through its pipeline, with rigorous gates ensuring that only the most promising compounds advance to expensive clinical trials.

Kill bad projects early and cheaply. The biggest value of Stage-Gate isn't launching winners — it's killing losers before they consume resources. A well-run Stage-Gate process kills 3-4 projects for every one it launches.

How to Apply Stage-Gate Process: Step by Step

Before You Start

  • Defined gate criteria and deliverables
  • Senior management commitment to serving as gatekeepers
  • Cross-functional project teams
Tools:Stage-gate templates and criteriaPortfolio management toolsProject tracking software
1

Define Stages and Gates

Design the stages appropriate for your product type and industry.

Tips

  • Customize stages for your business — don't use a generic template

Common Mistakes

  • Too many stages/gates making the process slow, or too few providing inadequate risk management
2

Set Gate Criteria

Define must-meet and should-meet criteria for each gate.

Tips

  • Include strategic fit, market attractiveness, technical feasibility, and financial criteria

Common Mistakes

  • Making criteria so loose that every project passes
3

Execute Stages and Conduct Gates

Teams do the work; gatekeepers review at gates and make decisions.

Tips

  • Gates should be short (1-2 hours) and decisive — not presentations

Common Mistakes

  • Gates becoming lengthy status meetings instead of crisp decision points
4

Track and Improve

Measure stage-gate process performance and continuously improve.

Tips

  • Track time in stage, kill rate, and post-launch success rate

Common Mistakes

  • Never reviewing whether the stage-gate process itself is working

Value & Outcomes

Primary Benefit

Increases new product success rates by systematically reducing risk through staged investment and gate decisions.

Additional Benefits

  • Kills bad projects early before they consume resources
  • Creates discipline in the innovation process

What You'll Learn

  • How to structure product development with appropriate decision points
  • How to make objective go/kill decisions on innovation projects

Typical Outcomes

Higher new product success ratesBetter allocation of R&D resourcesFaster time-to-market through disciplined decision making

Best Practices

📋 Preparation

  • Customize stages and gate criteria for your industry
  • Train gatekeepers on their role

🚀 Execution

  • Make gates decisive — Go, Kill, Hold, or Recycle
  • Ensure gates are cross-functional, not just engineering

🔄 Follow-Up

  • Track post-launch results and feed back into gate criteria
  • Continuously improve the process based on outcomes

💎 Pro Tips

  • The best Stage-Gate processes include a 'fuzzy front end' — a less structured discovery stage that encourages creativity before formal gates begin
⚠️

Don't let gates become rubber stamps. If gatekeepers approve everything, the process loses its value. Real gates require real criteria and real willingness to say 'Kill.'

📌

3M's Innovation Funnel

3M famously processes thousands of ideas through its Stage-Gate system each year. For every 3,000 raw ideas that enter the funnel, about 300 are submitted as formal proposals, 125 become small projects, 4 receive major funding, and 1.7 become commercial launches — demonstrating Stage-Gate's power as a disciplined innovation filter.

Limitations & Pitfalls

Can be too linear and slow for fast-moving markets

Mitigation: Use agile-stage-gate hybrids that combine gate governance with agile sprints within stages

Gate criteria may miss breakthrough innovations that don't fit standard evaluations

Mitigation: Create a separate 'fast track' for disruptive innovations with different gate criteria

Apply Stage-Gate Process with Stratrix

Turn this framework into a professional strategy deck in under a minute. Stratrix applies Stage-Gate Process automatically to your business context.

Try Stratrix Free