Field note: A stage gate should improve resource decisions, not reward teams for producing optimistic documents. Early stages should test desirability, feasibility, and critical assumptions cheaply; later stages demand stronger evidence about integration, operations, risk, and value.
Operational question
What uncertainty should be reduced before the next investment, and what evidence is sufficient for this stage—not an imagined final product?
A workable method
- Define stage-specific questions. Early gates may examine problem importance and plausible concepts. Later gates address technical performance, user workflow, safety, manufacturability, maintainability, adoption, and total cost.
- Separate evidence from advocacy. Use standard evidence tables, disclose failed tests and assumptions, and include reviewers who are not rewarded for continuation.
- Offer more than go or no-go. Allow continue, continue with conditions, redirect, run a targeted test, pause, transfer, or stop. Record the reason and required evidence.
- Carry learning forward. Maintain a decision log, evidence register, unresolved-risk list, and reusable artifacts so the next stage does not restart the argument.
What this looks like in practice
A prototype learning sensor may pass an early feasibility gate after bench tests, but a later gate requires evidence on privacy, calibration drift, instructor workflow, maintenance, accessibility, and performance in the intended environment.
Evidence to collect
Choose a small set of measures before implementation. Record the baseline, the source of each measure, the review cadence, and who is authorized to act on the result.
- uncertainties retired per unit of investment
- quality and independence of gate evidence
- reuse of lessons across projects and stages
Field checklist
- Write the decision, accountable owner, and decision date.
- Describe the current workflow and the conditions that shape performance.
- Confirm the source hierarchy, permissions, and local requirements.
- Test the method under representative—not merely convenient—conditions.
- Review both intended outcomes and burden on the people doing the work.
- Record a change, escalation, and stop rule before results arrive.
Watch-out
A gate can become theater when dates are fixed and stopping is punished. Leadership must make redirection and evidence-based termination legitimate outcomes.