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.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/stage-gate-process/
01What 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.[1][2]
- 01Discover + scopeExplore opportunity
- 02GateReview evidence
- 03Business caseCustomer, technical, commercial
- 04GateCommit, hold, recycle, stop
- 05Develop + validateIterate readiness
- 06Launch + reviewObserve results
Gatekeepers can go, hold, recycle, or stop.
02Why 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.
03When 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.
04How it works
- Define stages, gate criteria, decision rights, and evidence requirements appropriate to product risk.
- Explore and scope opportunities before committing to detailed development.
- Build a business case using customer, technical, operational, and commercial evidence.
- Develop, test, and validate the product and organizational readiness iteratively.
- At each gate, review evidence and decide to go, hold, recycle, or stop.
- Launch, evaluate in-market results, and improve the process using observed outcomes.
05A 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.
06Where 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.
07Sources
- Discovery-to-Launch ProcessStage-Gate International · Creator framework guideDiscovery-to-Launch Process
- TISC Project Management Toolkit — Learner’s GuideWorld Intellectual Property Organization · Intergovernmental practice guideTISC Project Management Toolkit — Learner’s Guide