Any phase · Ways of working
Prepare for a stage-gate review
A stage gate is a formal review before moving to the next phase or funding. Prepare evidence, not paperwork, and treat it as a chance to get help.
About 1-3 daysEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Delivery and executionCommunication and influence
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- Hybrid / stage gates
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- Find out what the gate needs to see and who decides.
- Gather the evidence: research, results, plans, risks and costs.
- Tell the story clearly: what you learned, what you will do next and why.
- Meet the decision-makers beforehand to hear concerns.
- Record the decision and any conditions.
Intermediate (1 to 4 years)
- Understand gate criteria and decision-makers.
- Prepare a concise evidence pack.
- Pre-brief decision-makers and record outcomes.
Experienced (5+ years)
- Push for gates based on evidence of value and risk, not documents.
- Use gates to secure resources and remove blockers.
- Help shape governance to support agile delivery.
Who can do this
Owner: Product manager
Can be delegated to
- Delivery Manager: Prepare the plan, risks and costs
- User Researcher: Summarise user evidence
- Business Analyst: Prepare governance documents
Reviewed by: Delivery Manager, Policy / Legal / Compliance
Tool examples
- SharePoint / Word
- Use the governance template and keep it short.
- Confluence
- Link the gate pack to live evidence rather than copying it.
- Power BI
- Show progress and cost charts in the pack.
Definition of done
- Gate criteria understood
- Evidence pack prepared
- Decision and conditions recorded
Common pitfalls
- Producing documents nobody reads
- Hiding problems
- Treating the gate as a test rather than help