The DMAIC Tollgate Review: How to Use It Effectively
One of the most powerful — and most underused — tools in a Lean Six Sigma project is the tollgate review. At the end of each DMAIC phase, the project sponsor sits down with the team to review the work completed, challenge the findings, and formally authorise the next phase. Done well, it is a genuine decision point. Done poorly, it is a rubber stamp that lets weak projects roll forward unchecked.
Understanding what a rigorous tollgate review looks like at each phase is the difference between a DMAIC project that delivers real results and one that collapses at the Improve or Control stage because the foundations were never solid.
What Is a Tollgate Review?
A tollgate review is a structured checkpoint at the boundary of each DMAIC phase. The team presents their work to the sponsor — and sometimes a broader steering committee — who evaluates whether the phase objectives have been met and whether the project is ready to proceed. The sponsor can approve, send the team back to complete additional work, or, in serious cases, cancel the project entirely.
The word "tollgate" is deliberate. Just as a highway toll requires you to stop and pay before passing through, a tollgate review requires the team to stop, demonstrate readiness, and earn permission to continue. It is not a status update. It is a go/no-go decision.
What to Review at Each Phase
Define. The sponsor should see a clear problem statement (what is wrong, where, since when, how much), a project charter with defined scope, a compelling business case expressed in financial or customer-impact terms, and an identified project team. The critical question: Is this problem worth solving, and is the scope manageable?
Measure. The team must present a detailed data collection plan, evidence that the measurement system is reliable (a gauge R&R study or equivalent), and a validated baseline — the current process sigma level or defect rate. If the team cannot demonstrate that the data is trustworthy, no further analysis is valid.
Analyse. This is often the most intellectually demanding tollgate. The team must show confirmed root causes — not suspected, but confirmed through data. Fishbone diagrams, Pareto charts, and regression analyses should point to the same few drivers. The sponsor should push hard here: "How do you know this is a root cause and not a symptom?"
Improve. The team presents the selected solution, pilot results, and evidence that the solution was tested under realistic conditions. Cost-benefit analysis should be included. The sponsor needs confidence that the fix actually works before committing resources to full implementation.
Control. The final tollgate confirms that the gains are locked in. The team should present a control plan, updated standard operating procedures, a monitoring mechanism (typically a control chart), and a response plan for when the process goes out of control. Transition of ownership to the process operator must be explicit.
Common Mistakes That Undermine Tollgates
Rubber-stamp reviews: The sponsor approves without genuinely challenging the work. This is the most common failure — it usually happens when sponsors are too busy, too polite, or too invested in the project to be objective.
Missing or unreliable data: Teams reach the Measure tollgate without a completed gauge R&R, or present baseline data collected inconsistently. The rest of the project is then built on sand.
Root causes not confirmed: Teams arrive at the Analyse tollgate with a list of suspected causes but no statistical evidence distinguishing root causes from noise. Gut feel is not a substitute for data.
No real go/no-go decision: Tollgates become progress reviews rather than decision points. There is no mechanism to pause or stop the project, so it lurches forward regardless of quality.
Scope creep unchecked: Each tollgate is an opportunity to reaffirm scope. Teams that do not revisit the charter at each review often find the project has drifted far from its original boundaries.
Making the Tollgate Work in Practice
The most effective tollgate reviews share a few characteristics. First, they are scheduled in advance and treated as immovable — a postponed tollgate is almost always a sign that the phase work is incomplete. Second, the sponsor prepares questions beforehand rather than reacting in the room. Third, a simple scorecard or checklist is used so there is a shared, objective standard rather than a subjective impression.
It also helps to distinguish between "phase complete" and "project approved." A team can complete the Define phase with a solid charter and still have the project cancelled at Measure if the baseline turns out to be unmeasurable. The tollgate is not about rewarding effort — it is about ensuring the project is viable at every step.
Organisations that treat tollgates seriously see measurably higher project completion rates and stronger financial returns. The discipline of stopping, demonstrating, and earning the right to continue is what separates rigorous Lean Six Sigma programmes from those that produce slide decks rather than results.
XNM Consulting supports organisations in building and sustaining effective Lean Six Sigma programmes, including coaching sponsors and Black Belts through rigorous tollgate processes. Learn more about our .