An Improvement Tollgate Review is a structured decision point used to determine whether an improvement project is ready to move into its next phase.
The review is not a presentation ceremony.
It is a governance mechanism for testing whether the team has enough evidence, clarity, and control to continue.
Define what each gate must prove
A useful tollgate has explicit exit criteria.
For example, an early gate may require:
- clear problem statement;
- baseline measure;
- defined scope;
- identified process owner;
- agreed target.
A later gate may require:
- verified causes;
- tested countermeasures;
- implementation plan;
- control plan;
- benefit evidence.
Improvement Project Charter provides many of the inputs needed for early project governance.
Review evidence, not slide quality
A polished deck does not prove project readiness.
The reviewer should ask:
- What evidence supports the problem?
- What was directly observed?
- Which assumptions remain open?
- How was the cause verified?
- What risk remains?
The purpose is to challenge the logic constructively.
For structured Six Sigma work, DMAIC provides natural phase boundaries for tollgate reviews.
Make the decision explicit
A tollgate should end with a clear decision.
Typical outcomes are:
- proceed;
- proceed with conditions;
- hold for missing evidence;
- change scope;
- stop the project.
A vague response such as “looks good, keep going” weakens governance.
The team should know exactly what is required next.
Use the right reviewers
Reviewers should be selected because they can improve the decision.
Depending on the project, that may include:
- sponsor;
- process owner;
- finance;
- quality;
- engineering;
- operations;
- safety.
Too many reviewers can slow the project.
Too few can leave important risk unchallenged.
Protect project ownership
The review should not become a meeting where senior leaders redesign the solution.
The project team owns the analysis and proposal.
The reviewers test:
- completeness;
- logic;
- risk;
- alignment;
- readiness.
Process Ownership helps clarify who ultimately owns the operating result after the project work is complete.
Review risk as the project evolves
Risk can change between phases.
For example:
- a proposed countermeasure may create a new failure mode;
- implementation may require a temporary deviation;
- a new supplier may be involved;
- a change may affect another process.
The tollgate should confirm that major risk is understood before commitment increases.
Confirm benefits and sustainment at closure
A final tollgate should not close the project only because actions are finished.
It should confirm:
- expected result achieved;
- standard updated;
- ownership transferred;
- controls active;
- benefit measurement defined.
Benefits Realization helps verify whether the improvement actually created the intended value.
Match rigor to project size
A small local PDCA does not need the same governance as a major cross-functional transformation.
The review effort should match:
- risk;
- investment;
- complexity;
- customer impact;
- strategic importance.
The objective is disciplined decision-making, not bureaucracy.
Common mistakes
Treating tollgates as slide reviews, advancing projects with unresolved evidence gaps, allowing reviewers to take over the solution, using the same gate requirements for every project, failing to record conditions for approval, and closing projects before results are demonstrated are common mistakes.
Practical sequence
- define gate criteria before the project begins.
- prepare evidence against the criteria.
- identify unresolved assumptions.
- review risk and scope.
- test the team’s logic.
- make the decision explicit.
- record conditions or required actions.
- confirm ownership for the next phase.
- verify results at final closure.
- improve the gate criteria based on experience.
The practical lesson
A tollgate should increase decision quality.
The best review does not ask whether the team completed the paperwork. It asks whether the evidence is strong enough to justify the next commitment.