The stage gate process splits a project into a sequence of phases, with a formal go/kill decision point, called a gate, between each one. At every gate a small group of decision-makers reviews the project against agreed criteria and chooses to fund the next phase, stop the project, hold it, or send it back for rework. It is the mechanism that stops weak work from quietly consuming budget for months because nobody scheduled the moment to question it.
The model is sometimes called phase gate, and it was popularized for new product development by Robert Cooper. It applies just as well to any sizable initiative inside a portfolio: a system migration, a facility build, a regulated program. This guide walks through the five stages, what actually happens at a gate, who approves them, and where stage gate fits next to agile.
Key takeaways
- A stage gate process alternates work phases (stages) with go/kill decision points (gates).
- The classic model has five stages: scoping, build the business case, development, testing and validation, and launch, with a discovery step before stage one.
- At each gate, a predefined group of gatekeepers decides go, kill, hold, or recycle against criteria set in advance.
- Stage gate and agile are not rivals. Use gates for the few irreversible funding decisions and iterate inside each stage.
What is the stage gate process?
The stage gate process is a project management framework that divides an initiative into defined phases separated by decision gates, where stakeholders review progress against set criteria and decide whether to continue, stop, pause, or rework the project. The point is to make funding a series of conditional commitments rather than one upfront bet. You release money one phase at a time, and you only release the next tranche if the phase you paid for actually earned it.
That structure does two useful things. It catches weak projects early, before they have absorbed most of their budget, and it forces the project team to produce evidence on a schedule instead of asking leadership to take delivery on faith. The discipline is most valuable exactly where it is hardest to apply: large, expensive, multi-department efforts where the cost of running a bad project to completion is enormous.
What are the 5 stages of the stage gate process?
The five stages of a classic stage gate process are scoping, build the business case, development, testing and validation, and launch, usually preceded by a discovery stage where ideas are generated and screened. Each stage does a distinct job and feeds the gate that follows it, where the work is judged before more money is committed.
| Stage | What happens | Gate that follows |
|---|---|---|
| Discovery (Stage 0) | Ideas are generated, screened for obvious fit, and the most promising are nominated. | Idea screen |
| 1. Scoping | A quick, low-cost investigation of the opportunity, market, and technical feasibility. | Second screen |
| 2. Build the business case | Detailed research produces a defined project, a justification, and a plan. | Go to development |
| 3. Development | The actual solution is designed and built; production and launch plans take shape. | Go to testing |
| 4. Testing and validation | The solution is verified through tests, trials, and limited market validation. | Go to launch |
| 5. Launch | Full-scale rollout, production, and the marketing and sales push. | Post-launch review |
Notice that the early stages are deliberately cheap. Scoping is meant to be a few weeks of light investigation, not a full study. The investment ramps up only as the project survives gates, which is the entire economic logic of the model: spend little to learn whether a project deserves the spend that comes next.
What is a gate review?
A gate review is a formal checkpoint where a governance group examines the project against pre-agreed criteria, such as the updated business case, the risk profile, and technical results, then decides whether the project proceeds to the next stage. It is not a status update. It is a funding decision with the authority to stop the work. The review usually moves through three parts: the team prepares deliverables, the gatekeepers evaluate them against the criteria, and a decision is recorded.
The decision at a gate is one of four outcomes:
- Go. The project clears the bar and is funded into the next stage.
- Kill. The project is stopped. This is the outcome that justifies the whole process, and a stage gate model that never kills anything is not working.
- Hold. The project is paused. It is still viable but something (capacity, a dependency, market timing) means now is not the moment.
- Recycle. The work is sent back for more development before the gate is revisited. The deliverables were not strong enough to decide on yet.
Good gates publish their criteria before the stage begins, so the team knows exactly what evidence it must bring. A gate that invents its standard on the day is just an opinion poll, and teams quickly learn to game it.
Who approves a gate in the stage gate process?
A predefined group of senior decision-makers, called gatekeepers, approves each gate, and they are chosen because they own the resources the project needs for its next stage. For early, low-cost gates this can be a single sponsor or a small portfolio board. For the expensive later gates, three through five, the gatekeepers are usually the business leadership team, because the resources at stake are theirs to commit.
The reason ownership of resources matters is that a gate decision is only real if the people making it can actually grant or withhold the money and people for the next phase. A gate run by reviewers who cannot say no, or cannot fund a yes, produces decisions nobody honors. This is the same principle that makes project portfolio governance work: decision forums need genuine decision rights, not just a calendar invite.
Stage gate vs agile: which should you use?
Stage gate and agile solve different problems, so the honest answer for most portfolios is both. Stage gate governs the few large, irreversible funding decisions through sequential gates; agile delivers the work inside a stage through short iterations with continuous adjustment. Stage gate protects a big upfront investment from running unchecked. Agile protects you from building the wrong thing in the first place.
| Dimension | Stage gate | Agile |
|---|---|---|
| Cadence | Sequential phases with formal gates | Short, repeating sprints |
| Decisions | Go/kill at scheduled gates | Continuous reprioritization |
| Best for | Large, costly, irreversible commitments | Evolving requirements, fast feedback |
| Main risk it controls | Funding a weak project to completion | Building something nobody wants |
The practical pattern, often called agile stage gate, keeps the gates for the irreversible money decisions and runs each stage as a series of agile iterations. You get the financial discipline of gates and the responsiveness of sprints. The mistake is treating them as a binary choice. A portfolio that uses only gates moves too slowly inside each stage; one that uses only sprints loses the ability to kill a project before it has spent its budget.
When is the stage gate process the right fit?
Stage gate earns its overhead when the cost of a wrong project is high and the decision to continue is genuinely worth pausing for. New product development, capital projects, regulated programs, and large system changes all fit, because each involves rising investment and a real option to stop. The gate structure gives leadership controlled exit points instead of a single all-or-nothing bet.
It is a poor fit for small, fast, low-cost work where the gate ceremony costs more than the risk it manages. If a project is cheap enough that running it to completion wastes little, do not wrap four gate reviews around it. Reserve the discipline for the work where stopping early actually saves something. And size the gates to the project: a small initiative might face one lightweight gate, while a major program faces all five with full review boards.
Stage gate process best practices
A few habits separate a stage gate process that protects the portfolio from one that becomes theater.
Define gate criteria before the stage starts. The team should know on day one of a stage exactly what it must prove to pass the next gate. Criteria invented at the review are unfair and unworkable.
Be willing to kill. The single most valuable thing a gate does is stop a project. If your gates only ever say go, they are decorative. Track your kill rate; a healthy process stops a meaningful share of what enters it.
Keep early stages cheap and fast. The economics depend on learning a lot for a little in scoping and the business case. If your early stages cost as much as development, you have lost the protection the model exists to provide.
Right-size the ceremony. Match the weight of the gate to the size of the bet. A uniform heavyweight process applied to every project teaches teams to route around it.
Connect gates to the portfolio view. A gate decision is also a capacity decision. Saying go to one project means saying not yet to whatever its people would otherwise do, which is why gating works best inside a clear picture of resource and capacity planning across the portfolio.
How stage gate fits the wider portfolio
Gates do not run in isolation. The work that reaches a stage gate process has usually already passed through an intake process and been ranked in prioritization. Intake decides what is worth considering, prioritization decides where it sits against everything else, and the gates then govern each surviving project as it spends real money phase by phase. Together they turn a portfolio from a list of things in flight into a managed set of conditional commitments, each one funded only as far as it has earned. That is the difference between a PMO that steers and one that simply records what already happened.