Stage-Gate Process: Phases, Gates & Examples for Project Teams

By Tara Minh · Updated Oct 8, 2026

The Stage-Gate process is a project governance model that divides work into stages and puts a decision point, called a gate, before each one. At every gate, senior reviewers check the evidence and decide to go, kill, hold or recycle the project. Robert G. Cooper created it for new product development, and teams now use it for many project types.

If you've ever watched a doomed project limp along for another six months because nobody wanted to be the one to stop it, you already understand the problem Stage-Gate was built to solve. It forces a hard, scheduled conversation about whether a project deserves the next slice of money and people.

What is the Stage-Gate process?

Stage-Gate is a trademarked framework from Dr. Robert G. Cooper. According to Stage-Gate International's overview, Cooper coined the term and it first appeared in print in 1988. Cooper's early academic description is the 1990 paper "Stage-Gate Systems: A New Tool for Managing New Products," published in Business Horizons (Vol. 33, No. 3, pp. 44-54).

The model has two building blocks:

• Stages are where the work happens. Cross-functional teams gather information, build things, test them and reduce risk. Each stage costs more than the one before it.
• Gates are the decision points between stages. A fixed group of senior managers, the gatekeepers, reviews the deliverables and decides whether the project earns the resources for the next stage.

The classic version has a Discovery phase followed by five stages, with a gate in front of each stage. Stage-Gate International's own overview labels this the "5-Stage, 5-Gate" model and describes Discovery as the upstream work of finding opportunities and generating ideas. A common way to name the stages looks like this:

1. Discovery: generate and capture ideas from customers, R&D, partners and strategy.
2. Scoping: a quick, cheap look at market and technical merit.
3. Build the business case: define the product or deliverable, the plan and the economics.
4. Development: design and build, with testing plans.
5. Testing and validation: prove the deliverable and the plan with trials, pilots or reviews.
6. Launch: go to market or hand over to operations, then review the results.

Stage names vary by company. The pattern doesn't: do a defined chunk of work, bring evidence to a gate, get a decision.

How gates work: go, kill, hold, recycle

The overview from Stage-Gate International says the typical gate outcomes are Go, Kill, Hold or Recycle. Here's what each means in practice:

On a Go, the overview notes, the gate also confirms the resources, timeline and deliverables, and sets the date of the next gate. That detail matters. A gate that ends without a named owner, budget and next date isn't really a gate.

Gatekeepers

Gatekeepers are the senior managers who control the resources the next stage needs. For smaller projects the group is usually a few functional leaders. For bigger bets, the overview says, the business's leadership team joins the later gates. The group should stay stable across the life of a project, otherwise teams end up re-arguing settled points every time a reviewer rotates in.

Gate criteria

Stage-Gate International describes two kinds of criteria: readiness (is the project mature enough for the next stage?) and business value, which it assesses with a risk-adjusted financial model and a scoring model it calls a Value-Based Scorecard.

Many organizations also split criteria into two buckets. Must-meet criteria are yes/no knock-outs, such as legal compliance or strategic fit. Should-meet criteria are scored and weighted, such as market attractiveness or team capability. This split is common practice in gate design rather than something you have to adopt exactly. The idea is simple: knock-outs weed out obvious misfits fast, and scoring helps you rank the rest.

Key Facts

Stage-Gate was created by Robert G. Cooper, first appeared in print in 1988 and was described academically in a 1990 Business Horizons paper. The classic model has a Discovery phase plus five stages, each preceded by a gate that ends in Go, Kill, Hold or Recycle.

• Gates are staffed by gatekeepers who control the resources for the next stage.
• Stage-Gate International describes gate criteria as readiness plus business value, with a risk-adjusted financial model and a scorecard.
• A hybrid that blends Agile sprints with Stage-Gate was studied by Cooper and Sommer in a 2016 Journal of Product Innovation Management paper, which reports faster and more adaptive responses to changing customer needs.
• Stage-Gate is a registered trademark. "Phase-gate" is the generic term most project teams use for the broader idea.

Stage-Gate vs other frameworks

Stage-Gate sits in a family of staged approaches. They overlap, but they're not the same thing.

The practical difference: generic phase-gates mostly ask "is this phase finished?" while Stage-Gate asks "should we still be doing this project at all?" That second question is why it pairs well with project portfolio management, where gates are how you free up capacity for better bets.

Later variants: scaled and agile versions

Cooper's original model was built for large, risky product projects, and applying the full process to a small enhancement can bury a team in paperwork. Teams commonly run scaled-down versions for lower-risk work, with fewer stages, combined gates and lighter documentation. Check Stage-Gate International for its current official variants before you name yours after one.

The bigger shift was agility. Stage-Gate International's overview says later generations of the model integrate software-world methods such as build-and-test cycles and in-stage sprints. Cooper and Sommer's 2016 paper, The Agile-Stage-Gate Hybrid Model, examines combining Agile with Stage-Gate for physical products. They report benefits including a faster and more adaptive response to changing customer needs and better team communication, and they note manufacturers have to modify Agile to make it work. The gates stay as governance. The stages become a series of short sprints.

If you're weighing these approaches, our comparison of agile vs waterfall is a good companion read.

How to set up a stage-gate process

You don't need a software tool to start. You need clarity about decisions. Here's a practical sequence.

1. Define what you're governing. Pick one project type first, such as new products or major IT builds. Mixing everything into one process is how gates turn into rubber stamps.
2. Name the stages. Four to six stages is enough for most teams. Write a one-line purpose for each.
3. Place the gates. Put a gate before each stage that needs a meaningful jump in spending. Early gates should be quick and cheap. Later gates deserve more scrutiny.
4. Write the deliverables per stage. A gate can only judge what it can see. List the documents or evidence the team must bring, starting with a project charter at the front.
5. Set criteria. Pick a short list of must-meet knock-outs and a scored list of should-meet factors. Keep it to what reviewers will actually read.
6. Choose gatekeepers. Name people who control budget and people. Agree on quorum and who decides when they disagree.
7. Agree on the decision rules. Define what Go, Kill, Hold and Recycle trigger. Make sure a Kill actually frees the team.
8. Build in risk and change handling. Link each gate to your risk register so that new risks show up in the review.
9. Pilot on one or two projects. Collect feedback from teams and gatekeepers, then trim anything that slowed decisions without improving them.
10. Review the process itself. After a few cycles, look at how many projects were killed, held or recycled, and where decisions stalled.

Stage-gate template you can copy

Adapt the table below to your organization. Treat the criteria as starting points, not a standard.

Examples by function

These are illustrative setups, not case studies. Your thresholds and names will differ.

Product development

A software company exploring a new feature uses a light Discovery gate where product and engineering leads read a one-page idea brief. Scoping asks for a few customer conversations. The business-case gate is where finance and the CEO step in, because Development is expensive. Testing might be a beta with a few accounts before the final launch gate.

IT and software projects

An internal IT team replacing a core system can use stages for requirements, design, build, pilot and rollout. Gates focus on integration readiness, data migration risk and training. A hybrid approach works well here: run sprints inside the build stage, and hold formal gates only at the points where spending or risk jumps.

Marketing campaign

A marketing team planning a large campaign can use three or four stages: concept, audience and message testing, production, and launch. The early gate checks the concept against the strategy and budget. The pre-production gate checks that message tests supported the creative direction. A Hold might mean waiting for a product release date to settle.

Construction and capital projects

Capital teams already think in phases: feasibility, design, procurement, construction and commissioning. Gates add clear funding decisions, such as approving design spend only after a feasibility study clears must-meet items like permitting and site conditions. A Recycle often means redesigning to fit a budget, and Kill is a legitimate result when costs outrun the case.

Process or operations change

An operations team rolling out a new workflow can use gates for a pilot team, a second pilot team, then wider rollout. Each gate checks adoption and error rates, so a problem at one site doesn't get copied to ten more.

Do's and don'ts

Do:

• Keep gate packs short. If reviewers need an hour to read the pack, they'll skim it.
• Decide criteria before the project starts, so the rules don't change when the project looks shaky.
• Make Kill a respected outcome. Celebrate the money and people redeployed.
• Give every Go a date for the next gate, a budget and an owner.
• Scale the process to the risk. Small, low-risk work shouldn't carry the same paperwork as a major bet.
• Track gate outcomes across projects, which makes the process itself improvable.

Don't:

• Don't turn gates into status meetings. A status update isn't a decision.
• Don't let a project skip a gate because it's "almost done." Late gates exist to protect the biggest spend.
• Don't staff gates with people who can't commit resources.
• Don't accept a Recycle as a default for "we don't want to say no."
• Don't use the model for work with truly unknowable scope without adding iteration inside stages.
• Don't confuse this with sales pipeline exit criteria. The stage-gate criteria used in sales pipeline management govern when a deal moves between sales stages, which is a different job from approving funding for a project.

Where to go next

Stage-Gate works best when it's treated as a decision system, not a document factory. Start with one project type, write down your gate criteria, and run a pilot. If you also manage a portfolio, look at how gates feed your PMO's reporting so leadership sees the same pipeline you do.