# Stage-Gate Process

A product-innovation process that separates cross-functional development stages with evidence-based investment gates and go, hold, recycle, or stop decisions.

- Type: framework
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/stage-gate-process/>)

## What it means

The Stage-Gate process, developed by Robert G. Cooper, organizes product innovation from discovery through launch into stages of work separated by management gates. Teams gather evidence within each stage, while gatekeepers assess defined deliverables and criteria before committing further resources; modern versions can incorporate iterative and agile work inside stages.

## Why it matters

Large product investments often grow through momentum without explicit evidence or stop decisions. Stage-Gate makes escalating commitment visible, coordinates commercial and operational readiness, and creates points to compare opportunities for scarce portfolio resources.

## When to use it

Use a proportionate version for costly, regulated, hardware-linked, manufacturing, or cross-functional product innovation where investment rises materially over time. It is usually excessive for small reversible software changes and should not replace continuous discovery within a stage.

## How it works

1. Define stages, gate criteria, decision rights, and evidence requirements appropriate to product risk.
2. Explore and scope opportunities before committing to detailed development.
3. Build a business case using customer, technical, operational, and commercial evidence.
4. Develop, test, and validate the product and organizational readiness iteratively.
5. At each gate, review evidence and decide to go, hold, recycle, or stop.
6. Launch, evaluate in-market results, and improve the process using observed outcomes.

## A practical example

A medical-device company uses gates before feasibility investment, clinical validation, production tooling, and launch. Within development stages, its software team works iteratively and tests prototypes with clinicians, but evidence on safety, manufacturability, and market access controls larger commitments.

## Where it breaks

Rigid gates can create handoffs, document theater, delayed feedback, and political approval rituals. Evidence remains uncertain, gatekeepers may favor visible sunk costs, and a one-size process can burden low-risk work. The framework must be scaled and permit iteration.

## Common mistakes

- Treating stages as isolated functional handoffs.
- Using document completion instead of decision-quality evidence at gates.
- Applying identical rigor to every product change.
- Making go decisions without the authority to stop or reallocate funding.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/stage-gate-process/#visualization-stage-gate-process>)

## Sources

1. [Discovery-to-Launch Process](<https://www.stage-gate.com/about/stage-gate-innovation-performance-framework/discovery-to-launch-process/>) — Stage-Gate International · Creator framework guide
2. [TISC Project Management Toolkit — Learner’s Guide](<https://www.wipo.int/documents/d/tisc/docs-en-tisc-toolkit-learners-guide.pdf>) — World Intellectual Property Organization · Intergovernmental practice guide

## Related topics

- [Business Case](<https://wiki.soroush.uk/topic/business-case/>)
- [Product Governance](<https://wiki.soroush.uk/topic/product-governance/>)
- [Product Portfolio Management](<https://wiki.soroush.uk/topic/product-portfolio-management/>)
