Stage-Gate Process

The stage-gate process breaks a large initiative into a series of stages, each followed by a gate. During each stage, the team completes a defined set of activities, such as research, design or testing. At each gate, a group of decision makers reviews the results against agreed criteria and decides whether the initiative should proceed to the next stage, be changed, be put on hold or be stopped. The idea is that money and effort are committed step by step, with each step justified by what has been learned so far.

The approach was developed by Robert Cooper for new product development and has since been applied widely to projects and investment programs. It gives leaders regular opportunities to stop work that is no longer worth pursuing, which is one of the hardest decisions in portfolio management. For portfolio leaders and IT finance teams, gates are natural points at which to check business cases, release funding and compare initiatives across the portfolio.

Definition of the Stage-Gate Process

The stage-gate process is a structured approach in which an initiative passes through a sequence of work stages and decision gates, with each gate using defined criteria to decide whether to invest in the next stage.

It is also called a phase-gate process or stage-gate model. It is closely linked to project governance and to the project lifecycle, since gates often mark the transitions between lifecycle phases.

Typical Stages

Discovery generates and screens ideas, with a light assessment of whether each one is worth exploring. Little money is spent at this stage, so many ideas can be considered.

Scoping makes a quick assessment of the market, technical feasibility and likely value.

Business case development carries out more detailed analysis and produces a plan, budget and business case.

Development builds the product, system or change.

Testing and validation confirm that the result works and meets the needs it was designed for, followed by launch or implementation. The number and names of stages vary between organizations.

What Happens at a Gate

The team presents its deliverables from the previous stage, such as research findings, designs, test results or an updated business case.

Gatekeepers assess the initiative against criteria such as strategic fit, value, risk, feasibility and readiness for the next stage.

The gatekeepers make a decision: go, kill, hold or recycle. A go decision approves resources for the next stage, while kill stops the initiative. Hold pauses it, and recycle sends it back for more work. Recording the reasons for each decision helps future teams understand what gatekeepers look for.

Importance of the Stage-Gate Process in Strategic Portfolio Management

The stage-gate process limits the cost of poor decisions. By committing money in steps, organizations avoid spending the full budget on initiatives that turn out to be weak.

It improves the quality of decisions. Each gate brings new information, so decisions about large commitments are made with more evidence than was available at the start.

It also creates regular points for portfolio-level comparison. Initiatives at the same gate can be compared with each other and with other priorities competing for the same resources.

The Stage-Gate Process and Financial Management

Gates are natural points to release funding. Many organizations approve only the budget for the next stage at each gate, rather than the full project budget at the start.

Business cases are updated at each gate with better estimates of cost and benefit, which improves the accuracy of portfolio forecasts.

Stopping initiatives at early gates saves money that can be redirected to stronger opportunities, and tracking how much is saved this way helps show the value of the process.

Gate decisions can also be linked to capital budgeting approvals, so that large capital commitments are only made once an initiative has passed the relevant gates.

Common Challenges

Gates can become formalities where almost every initiative passes, which removes the main benefit of the process. This often happens when gatekeepers are also the sponsors of the initiatives they review.

Heavy documentation requirements at each gate can slow work down, especially for smaller or lower-risk initiatives.

The traditional sequential model can fit poorly with agile delivery. Many organizations now use lighter gates focused on evidence and outcomes, combined with agile work within stages.