Innovation Pipeline & Stage-Gate Board

Purpose

This stage-gate board is a reusable template to manage many ideas while focusing investment on validated opportunities. Use it to clarify each stage’s objective, the evidence needed to pass a gate, who decides, and roughly how much investment is required. The template is intentionally adaptable — tailor criteria, evidence types, and investment bands to your organization and risk tolerance.

How to use this template

1. Create one row (card) per idea and place it in the column for its current stage.
2. At each gate, the decision owner checks that required evidence meets the gate criteria before approving movement to the next stage.
3. Record a short decision note and key next steps for transparency and learning.
4. Review the board regularly to prevent long-lived stalled projects and to reallocate resources quickly to validated work.

Columns (Suggested)

• Discovery — Explore customer problems, hypothesis generation, early desirability signals.
• Prototype — Build rapid, low-cost prototypes to test critical assumptions.
• Pilot — Test the solution in a limited live environment to measure performance and operations.
• Scale — Ramp up deployment, hand over to operations, and measure long-term outcomes.

Template row / card fields

For each idea, capture these fields so gates are consistent and decisions are evidence-driven.

Example gate criteria by stage (templates)

• Discovery → Prototype: Evidence of problem/market: at least 10 validated customer interviews, documented problem hypothesis, early willingness-to-pay signal.
• Prototype → Pilot: Prototype testing shows viability for core assumption: defined success metric met in user testing (e.g., 60% task success), and a basic cost/benefit sketch exists.
• Pilot → Scale: Pilot KPIs meet acceptance thresholds (e.g., retention, error rate, unit economics), operations can support scale, regulatory/compliance sign-off obtained.
• Scale → Operate: Full handover checklist completed, training and documentation ready, KPIs stable and tracked by business-as-usual owners.

Required evidence examples

• Discovery: interview notes, problem statements, competitor scan, preliminary value hypotheses.
• Prototype: test scripts, user feedback, quantitative usability results, technical feasibility notes.
• Pilot: live metrics, defect logs, operational runbook, customer support feedback, compliance audit results.
• Scale: validated cost model, go-to-market plan, SLA commitments, staffing plan, KPI dashboards.

Handoff checklist (pilot → scale)

• Operational runbook and troubleshooting guide completed.
• Training materials created and at least one training session performed for BAU teams.
• Support and escalation paths documented and tested.
• Performance and reliability thresholds defined and instrumented in dashboards.
• Budget and resource plan approved.

Governance and cadence

Decisions should be time-bound: a gate review should include a short written packet and a 30–60 minute review meeting. If an idea lacks progress or evidence for a defined period (for example, 8–12 weeks in Discovery without new learning), move it to an explicit backlog or archive with a short reason to prevent resource drag.

Common pitfalls and how to avoid them

• Scaling too early — require objective evidence and specific KPIs before approving scale.
• Gate criteria too vague — use measurable thresholds when possible and document qualitative trade-offs.
• Projects lingering unvalidated — add automatic review dates and lightweight kill criteria to reclaim resources.
• No clear decision owner — assign a named role to avoid stalled approvals.

Next steps to adapt this template

1. Customize gate criteria and evidence types to your industry and risk profile (e.g., medical devices need different compliance evidence than a web app).
2. Define investment bands typical for each stage in your organization.
3. Decide a cadence for pipeline reviews and a single source of truth (board tool or document) for decisions and notes.

Use this template as a living artifact: review and refine gate definitions after several cycles so the board reflects real-world learning and organizational standards.