The stage gate process, and how to track value through it
What is a stage gate process?
A stage gate process divides a project or an initiative into stages, with a decision point, called a gate, between each. At every gate a named person decides, on agreed criteria, whether the work goes on, changes or stops.
The stage gate process is one of the most widely used ideas in management, and one of the most often misused. Used well, it stops weak ideas early and protects strong ones. Used badly, it becomes paperwork that everyone fills in after the decision has already been made.
This guide covers the classic process, how transformation programs adapted it to track value instead of products, and the mistakes that turn gates into theater.
Where it came from
The stage gate model grew out of new product development. Robert G. Cooper studied why some new products succeeded and others failed, and described a process in which product ideas pass through a series of stages, each followed by a go or kill decision. The general idea, stages separated by decision points, is now used far beyond product development. Stage-Gate written with capitals is a registered trademark; this guide uses stage gate process as the general term.
The classic version runs from discovery and scoping, through building a business case, development, and testing, to launch. Each gate asks whether the evidence so far justifies the next round of investment.
Stage gates for value: L0 to L5
In a transformation, the thing that passes through the gates is not a product. It is a promise of value. Each gate asks how real that promise has become. Many transformation programs use six levels, from L0 for an idea to L5 for value that has been confirmed.
| Stage | Name | What it means | Typical evidence | Weight in the pipeline |
|---|---|---|---|---|
| L0 | Ideation | Someone has an idea | An owner, a workstream and a rough value range | 0% |
| L1 | Scoped | The idea has a scope and an owner | Problem, objective, scope and timing | 25% |
| L2 | Validated | The numbers have been checked | A business case that finance accepts, risks and at least five milestones | 50% |
| L3 | Plan locked | There is a committed plan | A phased estimate, milestones with owners and dates. The plan is saved | 100% |
| L4 | Implemented | The work is done | All milestones complete, with evidence | 100% |
| L5 | Value realized | The benefit has arrived | Run rate held at plan for three months, confirmed by finance | 100% |
The weights matter. If a program adds all ideas, validated cases and locked plans into one total, the total is mostly hope. Weighting by stage turns it into a risk adjusted pipeline: an idea counts for nothing, a scoped initiative for a quarter of its value, a validated one for half, and a locked plan for all of it. The gap between the risk adjusted pipeline and the target tells leaders how many more ideas they need, and how fast they need to move them.
Who decides at each gate
Gates need named approvers. A common pattern: the workstream lead triages ideas at L0 and confirms scope at L1. The workstream lead and a finance partner validate the business case at L2, with a functional approver such as the chief technology officer when a capital investment crosses a threshold. The workstream sponsor, the finance partner and the chief transformation officer lock the plan at L3. The sponsor and finance confirm realized value at L5.
Each decision needs a deadline. Forty eight hours is common, with a reminder when it passes and an escalation at seventy two or ninety six hours. Without a deadline, a gate becomes a waiting room.
of the maximum financial benefit is what companies with successful transformations say they captured. The rest captured 37%.
Source: McKinsey, Losing from day one: Why even successful transformations fall short, December 2021Stage is not status
These are two different questions, and most trackers mix them up.
| Stage | Status | |
|---|---|---|
| The question | How real is the value? | Is the work on course? |
| The answer | L0 to L5 | Green, Amber or Red |
| It changes when | A gate is passed | A rule is triggered |
An initiative can be at L3, with a locked plan, and Red, because a critical milestone is two weeks late. Another can be at L1 and Green, because it is moving exactly as planned through scoping. Reporting one number for both questions hides exactly the information leaders need.
Count value once
Double counting is the quiet killer of transformation credibility. Two initiatives, one saving: a procurement team renegotiates a freight contract, and the logistics team reroutes the same lanes. Both claim the saving, the total on the board slide is wrong, and the finance team stops trusting every number that follows.
The remedy is simple to state and hard to keep without a system: every benefit has one home. Each benefit line belongs to exactly one initiative, and an initiative that depends on another links to it rather than claiming its value.
How to read a value pipeline
Plot the total value at each gate, L0 to L5, as a bar chart, with the number of initiatives in each bar. A healthy pipeline has a broad base of ideas and scoped initiatives, a steady flow through L2 and L3, and a growing amount at L4 and L5 as the program matures.
Three shapes are warning signs. Everything at L1 means ideas are not being validated. A tall bar at L3 and a short one at L4 means plans are locked but execution is stalling, which is where most value is lost. Nothing at L5 after a year means nobody is confirming that the money arrived.
of the potential financial benefit of a transformation is lost, on average, in the later stages of executing and sustaining it.
Source: McKinsey, How to implement transformations for long term impact, May 2023Five mistakes
- Gates as paperwork. The form is filled in after the decision. Fix: the gate decides, and the form is its evidence.
- No named decider. A committee approves, so nobody is accountable. Fix: one name per approval, with a deadline.
- Vague criteria. "Business case complete" means different things to different people. Fix: list the fields and the evidence each gate requires.
- L1 value reported as money. The board hears a number that is mostly ideas. Fix: report the risk adjusted pipeline, and keep the hopper separate.
- No check after L5. The value is confirmed once and never looked at again. Fix: hold the run rate for an agreed period, such as three months, before confirming.
Where software helps
Centric Governance Central builds these stages into the screens. Every initiative carries its gate, its value by period and its status, gate requests go to named approvers with deadlines, and a benefit is booked once. See stage gates in CGC.
Frequently asked
How many gates should a process have?
Enough to separate an idea, a checked case, a committed plan, finished work and confirmed value. Six, from L0 to L5, is common in transformation programs.
Who signs off a gate?
Named approvers set for each gate, typically the workstream lead, the sponsor, a finance partner and, for large investments, a functional approver.
What is the difference between value realization and benefits realization?
They are used almost interchangeably. Benefits realization often includes non financial benefits, while value realization usually refers to financial impact in a stated profit metric.
What does L3 mean?
L3, often called plan locked, is the gate at which the plan is committed and saved as the reference that later progress is compared with.
Do not take our word for it. Take Microsoft's.
CGC is listed and transactable on Microsoft Marketplace, co-sell ready with Microsoft, and the subject of a Microsoft partner success story. Centric is a Microsoft Solutions Partner for Data & AI (Azure).
Centric's enterprise-grade platform unifies strategic planning, KPI management, program execution, and governance workflows into a single, secure system of record.

- February 2026Listed on Microsoft MarketplaceCGC goes live on Microsoft Marketplace as a transactable offer.
- May 2026Named in the Microsoft Marketplace blogMicrosoft features CGC among new transactable offers on 26 May 2026.
- October 2026Co-sell ready with MicrosoftMicrosoft sellers can work with Centric on customer purchases.
- November 2026Featured in a Microsoft partner success storyMicrosoft publishes how Centric built CGC into a scalable Marketplace offer, on 13 November 2026.
See it on your own sector's data.
A 30 minute walkthrough, built around a program like yours. No slides, the real product.
