Stage-Gate Process: How It Guides New Products from Idea to Launch
Stages build the evidence. Gates commit the resources.
Earn the next commitment.
Review a gate- Ideas beginDiscovery
Find opportunities and generate ideas.
- Gate 11Concept
Scope the market and technical feasibility.
- Gate 22Business case
Investigate need, economics, risks and the plan.
- Gate 33Development
Build the product and delivery processes.
- Gate 44Validation
Test the product, market and operating system.
- Gate 55Launch
Commercialize and review performance.
Work happens within stages. Each gate precedes the next stage and can send the project back for more learning.
One design. Two gate reviews.
14 of 20 users value the folding design. Several struggle to clean the hinge.
Resolve the cleaning problem before committing to full development.
On this page
The Stage-Gate Process is a structured way to move a new product from an initial idea toward launch. It divides the work into stages, where a cross-functional team gathers evidence and develops the product, and gates, where decision-makers decide whether the project deserves further investment.
Robert G. Cooper developed the approach from research into new product development. Its logic is simple: larger commitments should require better information.
What is the Stage-Gate Process?
A stage is where the team does the work. It may research customers, test technical feasibility, build a business case, develop a prototype, validate the product or prepare a launch.
A gate is a decision point before the next major stage. The team presents what it has learned, decision-makers compare the evidence with agreed criteria, and the business chooses what happens next.
Typical gate outcomes are Go, Kill, Hold or Recycle. A Go decision should also approve the resources required for the next stage.
Stage-Gate is therefore not just a project schedule. It is a sequence of increasingly informed investment decisions.
Why does it matter?
New product projects begin with uncertainty. Stage-Gate helps a business avoid making its largest commitment while it still knows the least. Later work receives more resources only when stronger evidence justifies it.
How the stages work
The official model for major new product projects includes discovery followed by five stages. Organizations can adapt the rigor to the size and risk of the project.
| Part | Main purpose |
|---|---|
| Discovery | Find opportunities and generate ideas. |
| Stage 1: Concept | Perform quick market and technical scoping. |
| Stage 2: Build the Business Case | Investigate customer need, feasibility, economics, risks and the development plan. |
| Stage 3: Development | Design and build the product and the processes needed to deliver it. |
| Stage 4: Testing and Validation | Test the product, market assumptions and operating system. |
| Stage 5: Launch | Commercialize the product and review performance after launch. |
Each stage should produce the information required for the next decision. A gate precedes each major stage; it is not simply a meeting at the end of the project.
How a gate works
A useful gate has three parts:
- Deliverables. The team brings the evidence produced during the previous stage, such as customer research, technical results, prototype feedback, financial estimates and updated risks.
- Criteria. Decision-makers compare the project with questions agreed in advance: Is there a clear customer need? Is the solution feasible? Does it fit strategy? Are the economics still plausible?
- Decision and resources. The gate ends with Go, Kill, Hold or Recycle. A Go should approve the budget, people, timing and next deliverables.
A simple example
Hypothetical example: A small kitchenware company is considering a reusable lunch container that folds flat when empty. The interviews, user tests and decisions below are illustrative, not actual research or proof of product safety.
| Point | Evidence produced | Gate decision |
|---|---|---|
| Concept | Ten customer interviews suggest that storage space is a genuine inconvenience. A supplier confirms that a food-safe flexible material is technically plausible. | Go |
| Business Case | A simple prototype is tested with 20 target users. Fourteen value the folding design, but several struggle to clean the hinge. Estimated unit cost remains within the target range. | Recycle |
| Revised Gate | A second prototype removes the difficult hinge and passes the team's basic cleaning test. Updated costing remains acceptable. | Go |
| Development | A production-ready prototype is built and the supplier confirms the manufacturing process. | Go |
| Validation | A small pilot confirms that users can clean, fold and reuse the container as intended. | Go |
The Recycle decision prevented the company from scaling a design with a known usability problem. A larger commitment followed only after the evidence improved.
The revised gate repeats the business-case decision; it is not an extra development stage. These simplified checks do not replace the full safety, technical, commercial and operational validation a real product may require.
When should you use it?
Stage-Gate is most useful when a project requires meaningful investment, several functions, prototypes, testing or important technical and commercial decisions.
Small, reversible changes may not justify formal gates; rigor should match risk.
A Product Roadmap explains product direction and priorities. RICE Prioritization can compare candidate initiatives. Stage-Gate asks a different question: what evidence should justify the next investment in a project already being developed?
How to interpret a gate result
A gate decision is not a score of whether the team performed well.
- Go: The evidence is strong enough to justify the next commitment, with the required resources approved.
- Kill: Continuing no longer makes sense.
- Hold: Preserve the option while waiting for conditions to change.
- Recycle: Important work or evidence is missing; specify what must change before the gate is repeated.
Stopping or recycling early can protect resources from a weak investment.
Common confusion: Stage-Gate and waterfall
Stage-Gate is sometimes mistaken for a rigid waterfall plan.
The stages define blocks of learning and development; the gates govern major investment decisions. Teams can prototype, test, revise and repeat within a stage before reaching the next gate.
Common mistakes
- Turning gates into status meetings instead of real decisions.
- Deciding "Go" before reviewing the evidence.
- Using vague criteria that teams cannot prepare for.
- Applying maximum bureaucracy to every project.
- Continuing mainly because money has already been spent.
Limitations
Stage-Gate cannot remove uncertainty or guarantee success. Poor evidence can still produce poor decisions, and excessive process can slow small projects. It works best when criteria are explicit, evidence is updated and process rigor matches project risk.
Quick checklist
Before approving the next stage, ask:
Put it to work
Choose one product idea and write the next major investment you are considering. Then list the three most important facts you should know before approving it.
Turn those facts into gate criteria, define the evidence that would satisfy them, and consider all four outcomes: Go, Kill, Hold and Recycle. For a Go decision, write the exact resources that would be approved next.
Test one project's next gate in 25 minutes
- 5 minutes: name the next commitment. Write the money, people, tooling, production, research or launch activity the business would approve next.
- 5 minutes: define the evidence. List the three most important unknowns that should be reduced before that commitment.
- 5 minutes: set the criteria. Turn each unknown into a decision question with a clear minimum condition.
- 5 minutes: review what you actually know. Mark each criterion as supported, unsupported or uncertain and attach the evidence.
- 5 minutes: decide. Choose Go, Kill, Hold or Recycle. If Go, state the resources and next deliverables. If Recycle, state exactly what must be learned before the gate is repeated.
The exercise is complete when another manager could understand why the decision follows from the evidence. A first review is a working draft, not formal investment approval.
Your next investment decision
18 items still to record
- project
- current stage
- next commitment
- decision
- decision rationale
- decision owner
- Criterion 1: question
- Criterion 1: minimum condition
- Criterion 1: evidence / assumption basis
- Criterion 1: evidence status
- Criterion 2: question
- Criterion 2: minimum condition
- Criterion 2: evidence / assumption basis
- Criterion 2: evidence status
- Criterion 3: question
- Criterion 3: minimum condition
- Criterion 3: evidence / assumption basis
- Criterion 3: evidence status
Reader-supplied draft. No automated approval or AI assessment. Notes stay on this page until you leave; download to retain them.
Finish by asking: Would this gate allow us to stop or change the project if the evidence is weak?
If the answer is no, you have created a checkpoint, not a decision gate.
Key takeaways
- Stage-Gate separates work stages from investment decision gates.
- Major new product projects typically move from discovery through concept, business case, development, validation and launch.
- Gates should review defined deliverables and criteria, then produce a clear Go, Kill, Hold or Recycle decision.
- A Go decision should include the resources required for the next stage.
- Stage-Gate is not necessarily rigid or linear; teams can iterate within stages while preserving governance at major investment points.
Final takeaway
The Stage-Gate Process divides new product development into stages of work and gates of decision-making. Teams gather progressively better evidence while leaders make progressively larger resource commitments.
Its value is not in adding meetings. It is in making the business earn the right to invest more.