Stage-Gate

What it is

Stage-Gate is a structured product development framework that divides the innovation process into stages (where work happens) separated by gates (where decisions happen). At each gate, a cross-functional team reviews evidence and makes an explicit go / kill / pivot / recycle decision before allowing the initiative to proceed.

Originally developed by Robert Cooper in the 1980s for physical product development, Stage-Gate has evolved through five generations. The 5th-generation model (current) integrates Agile practices, AI-assisted decision-making, and adaptive gates — it is not the rigid, waterfall process of earlier versions.

Companies using modern Stage-Gate achieve 63–78% product success rates, compared to ~24% for ad-hoc approaches (PDMA benchmarking studies).

---

Authoritative sources (external)

---

Core structure

Stages and gates

The classic 5-stage model, adapted for software products:

Gate decisions

Each gate uses explicit criteria — not opinions:

5th-generation adaptations

---

Discovery-to-launch reference framing (seven stages)

There is no single universal PDLC phase model. Teams differ on how many phases they use, where one phase ends and the next begins, and whether the lifecycle stops at launch or continues into post-launch learning. Strong practice is to define each phase by purpose, required activities, deliverables, exit criteria, and gate decisions, while treating the flow as iterative and cross-functional, not as a rigid one-way handoff. (See also ProductPlan — product development cycle.)

The table below is a mainstream seven-stage discovery-to-launch shape (similar to Stage-Gate’s discovery-to-launch material), with one distinct decision question per stage — a quick sanity check that each stage earns its place. Forge’s canonical lifecycle remains P1–P6 plus embedded SDLC A–F in Product development lifecycle (PDLC) and PDLC ↔ SDLC bridge; use the mapping column to translate vocabulary.

Merging or splitting phases is normal. For example, some teams merge design into development; others treat post-launch learning as its own emphasis inside P5. What matters is that each phase still has a clear purpose, explicit deliverables, and exit criteria — not the label count.

---

Mapping to PDLC phases

Stage-Gate maps directly to PDLC phases and gates:

Using Stage-Gate within this blueprint

Use Stage-gate review — [Initiative Name] to document gate decisions. The template captures: - Gate identifier and date - Evidence reviewed (with links to artifacts) - Criteria assessment (met / not met / partially met) - Decision (go / kill / pivot / hold) - Conditions for proceeding (if any) - Resource allocation for next stage

---

Anti-patterns

---

Further reading

• PDLC.md §4 — Stage gates — Gate definitions G1–G5 in this blueprint
• PDLC-SDLC Bridge §6 — Decision framework — Meeting questions, when to use heavy vs light gates, plain-language gates vs G1–G5
• Lean Startup — Complementary: hypothesis-driven validation within stages
• Design Thinking — Complementary: human-centered methods for Stages 1–2

Related pages

• PDLC approach guides (blueprint)
• External reference URLs (PDLC approach gui…
• Design Thinking
• Dual-Track Agile
• Lean Startup