A sponsor's job during a tollgate review is not to celebrate progress. It is to make a disciplined decision about whether the team has earned the right to move forward. The DMAIC tollgate checklist exists precisely for this reason: to give sponsors a structured, evidence-based framework for evaluating each phase before granting approval.
This article walks through 25 targeted DMAIC tollgate questions, organized by phase, so sponsors can challenge assumptions, confirm deliverables, and protect the integrity of every project gate review. You will also find a three-tier approval framework and phase-specific warning signs that should immediately delay any DMAIC phase approval.
Key Takeaways
- Sponsors should approve phases only when evidence is complete.
- Each DMAIC phase requires specific proof and deliverables.
- Weak data or unproven causes should trigger a hold.
- Tested solutions and clear ownership support lasting results.
- Strong tollgates protect project quality and business value.
A Sponsor Should Approve a Phase Only When the Evidence Is Complete
Before diving into the 25 questions, every sponsor needs a clear decision framework. Approving too early undermines the entire Six Sigma tollgate review process. Waiting too long without cause stalls momentum and frustrates teams.
Use this three-tier framework at every project gate review:
- Approve: All phase deliverables are complete, evidence is reliable, and the team is ready to proceed without conditions.
- Conditionally Approve: Most deliverables are complete, but one or two items need resolution within a defined timeframe before the next phase begins.
- Hold: Critical deliverables are missing, data is unreliable, root causes are unproven, or risks are unresolved. The team must return for a second tollgate review.
This framework applies across all five phases. The questions below tell you exactly what to look for at each gate.
The Define Phase Checklist: 5 DMAIC Tollgate Questions for Sponsors
The Define phase sets the foundation for everything that follows. A weak project charter or vague problem statement will cost the team weeks of rework later. Sponsors must confirm that the project is worth pursuing before any resources are committed.
Here are the five Define phase checklist questions every sponsor should ask:
1. Is the Problem Statement Specific and Measurable?
The problem statement should describe what is wrong, where it occurs, and how large the gap is. Vague statements like "improve customer satisfaction" are a warning sign that the team has not yet defined the real problem.
- Evidence expected: A written problem statement with quantified impact and a defined scope boundary.
- Warning sign: The team cannot explain the problem without using solution language.
2. Does the Project Charter Reflect Sponsor Alignment?
The charter is a contract between the team and the organization. If the sponsor has not reviewed and signed off on the charter, the project lacks formal authorization and accountability.
- Evidence expected: A signed, dated project charter with agreed scope, goals, and timeline.
- Warning sign: The charter has not been updated since the project kickoff meeting.
3. Has the Voice of the Customer Been Captured?
A Lean Six Sigma project without VOC data is solving a problem the organization assumes exists. Sponsors should confirm that customers were actually consulted, not just assumed.
- Evidence expected: VOC data translated into critical-to-quality characteristics (CTQs) with measurable thresholds.
- Warning sign: CTQs were defined internally without any customer input or validation.
4. Is the SIPOC Map Complete and Agreed Upon?
The SIPOC provides a high-level view of the process in scope. Without it, the team risks measuring and analyzing the wrong process entirely.
- Evidence expected: A completed SIPOC diagram reviewed by key stakeholders and process owners.
- Warning sign: The process boundaries in the SIPOC do not match the scope in the charter.
5. Are Team Roles and Tollgate Dates Confirmed?
Lean Six Sigma project governance requires clear accountability from day one. If team roles are undefined or tollgate dates have not been scheduled, the project lacks basic structure.
- Evidence expected: A RACI chart or equivalent, with scheduled tollgate review dates on the project timeline.
- Warning sign: The team cannot name who is responsible for each deliverable.
Sponsors who invest in structured governance training gain a significant advantage here. Air Academy Associates offers a dedicated Lean Six Sigma Champions Online Training program designed specifically to help leaders run effective tollgate reviews, remove barriers, and drive project accountability from the Define phase forward.
Measure Phase Tollgate: 5 Questions to Confirm Data Integrity
The Measure phase is where projects either gain credibility or lose it. Sponsors must confirm that the team is measuring the right things, measuring them correctly, and establishing a reliable baseline. Without this, the Analyze phase will produce conclusions built on flawed data.
1. Have the Key Performance Indicators Been Agreed Upon?
KPIs should connect directly to the CTQs defined in the Define phase. If the metrics have shifted without explanation, the project may be drifting from its original scope.
- Evidence expected: Documented KPIs with operational definitions and measurement units.
- Warning sign: The team is tracking metrics that do not directly link to the problem statement.
2. Is There a Documented Data Collection Plan?
A data collection plan defines what data will be collected, by whom, when, and how. Without it, data quality is unpredictable and the baseline becomes unreliable.
- Evidence expected: A written data collection plan reviewed before data gathering began.
- Warning sign: Data was collected informally, without a defined plan or sampling strategy.
3. Has Measurement System Analysis Been Completed?
Every project should assess whether its measurement or data system is fit for purpose. Depending on the type of data, this may involve Gage R&R, agreement analysis, calibration review, data audits, or another appropriate validation method.
- Evidence expected: A documented assessment showing that the measurement or data system is sufficiently accurate, consistent, and reliable for the project's decisions.
- Warning sign: The team skipped MSA because the measurement "seemed obvious."
4. Is the Baseline Performance Documented?
The baseline is the starting point against which all improvement will be measured. Without a documented baseline, there is no way to prove that any change made a difference.
- Evidence expected: Baseline performance summarized with measures appropriate to the outcome and data type. Include process capability only when the process is stable and valid specification limits are available.
- Warning sign: The baseline was estimated rather than measured from actual process data.
5. Does the Data Reveal Any Unexpected Patterns or Risks?
Sponsors should ask whether the data revealed anything that changes the project scope, timeline, or business case. Early surprises are far easier to address than late ones.
- Evidence expected: A brief data summary with any notable patterns, outliers, or risks flagged for discussion.
- Warning sign: The team presents only clean, favorable data without acknowledging variation or anomalies.
Analyze Phase DMAIC Tollgate Questions: Proving Root Causes With Data
The Analyze phase is where assumptions get tested. Sponsors must push teams to prove root causes with data, not just confirm what everyone already believed. This is the phase most likely to be rushed, and rushing it leads directly to solutions that do not work.
1. Are Root Causes Proven With Statistical Evidence?
A list of suspected causes is not the same as proven root causes. Sponsors should ask the team to show the analysis that confirms each root cause, not just the conclusion.
- Evidence expected: Root-cause hypotheses identified through tools such as process maps, fishbone diagrams, or the Five Whys, followed by observational, experimental, or statistical evidence that tests the most important suspected causes.
- Warning sign: Root causes were selected based on team opinion rather than data analysis.
2. Have the Vital Few Drivers Been Separated From the Trivial Many?
The team should identify and prioritize the factors with the strongest evidence of practical and statistical impact. The number of material drivers will depend on the process, data, and interactions among causes.
- Evidence expected: A prioritized list of root causes with supporting data showing relative impact.
- Warning sign: The team presents a long, unprioritized list of possible causes without estimating their relative impact or strength of evidence.
3. Has the Team Validated Findings With the Process Owner?
Root cause findings that have not been reviewed with the process owner risk being disconnected from operational reality. The process owner should review the findings, provide operational context, and identify implementation constraints. Any disagreement with the analysis should be documented and resolved through additional evidence where necessary.
- Evidence expected: Documentation of the process owner's review, comments, unresolved concerns, and agreed actions.
- Warning sign: The process owner was not involved in the Analyze phase at all.
4. Are There Any Assumptions That Have Not Been Tested?
Sponsors should specifically ask whether any assumptions from the Define or Measure phase were carried forward untested. Unchallenged assumptions are a common source of project failure.
- Evidence expected: A list of assumptions with confirmation of which were tested and how.
- Warning sign: The team cannot identify any assumptions they made during the analysis.
5. Does the Analysis Support the Original Business Case?
If the root causes identified do not connect back to the business case in the charter, the project may need to be rescoped. Sponsors must make this call before the team moves to solutions.
- Evidence expected: A clear link between proven root causes and the financial or operational impact described in the charter.
- Warning sign: The team's findings suggest the original problem was misdiagnosed.
For teams that need to strengthen their analytical skills before or after the Analyze phase, the Project Study Definition course focuses on clarifying a project's purpose, scope, structure, boundaries, and charter elements before full project work begins.
| DMAIC Phase | Primary Evidence Required | Top Warning Sign | Approval Risk Level |
|---|---|---|---|
| Define | Signed charter, VOC, SIPOC, CTQs | Vague problem statement | High if charter is unsigned |
| Measure | MSA results, baseline data, data collection plan | No measurement system validation | High if baseline is estimated |
| Analyze | Statistical root cause proof, prioritized drivers | Opinion-based root causes | Critical if no data supports findings |
| Improve | Pilot results, cost-benefit analysis, implementation plan | No pilot conducted | High if solutions are untested |
| Control | Control plan, response plan, ownership transfer | No process owner handoff | Critical if monitoring is not in place |
Improve Phase Project Gate Review: 5 Questions Before Approving Solutions
Reaching the Improve phase feels like progress, but sponsors must resist the urge to approve quickly. Solutions that were not piloted, cost-justified, or risk-assessed have a poor track record of sustaining results. This is the phase where sponsor discipline matters most.
1. Were Solutions Piloted Before Full Implementation?
A pilot test confirms whether a proposed solution actually works under real conditions. Proposed solutions should be tested under controlled or limited conditions before broad implementation whenever practical. The test may take the form of a pilot, prototype, simulation, phased release, or small-scale improvement cycle.
- Evidence expected: Results from an appropriately scaled test showing whether the solution improved the target measure and created any unintended effects.
- Warning sign: The team plans to implement the solution at full scale without any prior testing.
2. Has a Cost-Benefit Analysis Been Completed?
Every solution has a cost. Sponsors need to confirm that the expected benefit justifies the investment before approving implementation resources.
- Evidence expected: A documented cost-benefit analysis reviewed by finance or the project sponsor.
- Warning sign: The team cannot quantify the expected return on the proposed solution.
3. Have Risks Been Identified and Mitigated?
The team should complete a risk assessment proportionate to the scale and consequences of the proposed change. FMEA is appropriate for complex or high-risk implementations, while simpler changes may use a structured risk register or preimplementation review.
- Evidence expected: A completed FMEA or risk register with mitigation actions assigned to specific owners.
- Warning sign: The implementation plan does not include any contingency actions.
4. Is There a Detailed Implementation Plan?
An implementation plan defines who does what, by when, and with what resources. Without it, even a well-tested solution can fail during rollout.
- Evidence expected: A project plan with milestones, owners, resource requirements, and a communication strategy.
- Warning sign: The team presents a solution without a corresponding implementation roadmap.
5. Has Stakeholder Buy-In Been Secured?
Solutions that affect other teams or departments require stakeholder alignment before implementation begins. Sponsors should confirm this before approving the Improve phase.
- Evidence expected: Documentation of stakeholder reviews, approvals, or sign-offs from affected departments.
- Warning sign: Affected stakeholders were informed but not consulted during solution development.
Control Phase DMAIC Phase Checklist: 5 Questions to Ensure Lasting Results
The Control phase is the most frequently underestimated in the entire DMAIC phase checklist. Teams often rush to close projects without confirming that the gains will hold. Sponsors must be particularly rigorous here, because once a project is closed, organizational attention moves on.
1. Is There a Documented Control Plan?
The control plan defines how the process will be monitored going forward. Without defined monitoring, ownership, and response responsibilities, the process is more likely to drift after the project team disengages.
- Evidence expected: A written control plan with monitoring frequency, responsible parties, and acceptable performance thresholds.
- Warning sign: The team plans to monitor performance informally without a structured plan.
2. Is an Appropriate Ongoing Monitoring System in Place?
The monitoring method should match the process, data frequency, and risks involved. Depending on the project, this may include control charts, run charts, automated alerts, audits, dashboards, or periodic compliance checks.
- Evidence expected: A run chart, control chart, or other monitoring method suited to the process, supported by defined decision rules and a documented response plan.
- Warning sign: The monitoring method does not match the data type, lacks defined interpretation rules, or cannot reliably distinguish meaningful change from routine variation.
3. Does the Response Plan Define What to Do When Performance Drops?
A response plan tells the process owner exactly what to do if the process drifts back toward the old baseline. Without this, teams default to firefighting rather than structured correction.
- Evidence expected: A written response plan with escalation steps and defined triggers for action.
- Warning sign: The response plan says "notify the manager" without any specific corrective steps.
4. Has Ownership Been Formally Transferred to the Process Owner?
Project closure without a formal ownership transfer is one of the most common reasons improvements do not sustain. The process owner must accept responsibility before the Belt moves on.
- Evidence expected: A signed ownership transfer document or equivalent formal handoff record.
- Warning sign: The Belt is still the primary contact for process performance after project closure.
5. Have Financial Benefits Been Validated by Finance?
Self-reported savings are not the same as validated financial results. When a project claims hard savings, cost avoidance, revenue impact, or other financial benefits, the calculation method and reported amount should be reviewed by finance or another designated benefits owner before the results are reported.
- Evidence expected: For projects reporting financial benefits, a documented benefits calculation reviewed by finance or the organization's designated validation authority.
- Warning sign: The team's reported savings have not been reviewed outside the project team.
Strengthen Your Sponsor and Belt Capability With These Resources
Running a disciplined tollgate review requires more than a checklist. Sponsors and project leaders need structured training that builds the judgment to ask the right questions at the right time. The following programs from Air Academy Associates are directly relevant to the skills covered in this DMAIC tollgate checklist.
Whether you are a sponsor looking to lead more effective project gate reviews or a Belt preparing to present at each phase, these resources provide the foundation you need to govern projects with confidence.
Lean Six Sigma Champions Online Training
The Lean Six Sigma Champion Training Course introduces Lean Six Sigma, the DMAIC roadmap, project-selection principles, and the roles and responsibilities of a Champion. It is suited to leaders who sponsor improvement work and need a practical foundation for overseeing DMAIC projects.
Key focus areas include:
- Understanding the DMAIC phase checklist from a leadership perspective
- Running structured Six Sigma tollgate reviews with confidence
- Coaching Belt teams without micromanaging
- Aligning project selection with organizational priorities
Learn more: Lean Six Sigma Champions Online Training
Project Study Definition
Before a project reaches its first tollgate review, the problem must be properly scoped and defined. This resource guides teams through the critical work of defining a project study with enough rigor to survive sponsor scrutiny. It directly supports the Define phase checklist and helps teams avoid the most common early-stage mistakes that lead to holds at the gate. It covers problem framing, scope boundaries, and baseline identification to set every project up for a clean first tollgate approval.
Learn more: Project Study Definition
Lean Six Sigma Green Belt
Green Belts are often the practitioners presenting at tollgate reviews and defending their phase deliverables to sponsors. This certification program trains them to produce the evidence that sponsors expect at every gate. It covers VOC analysis, measurement system validation, root cause analysis, solution development, and control planning, giving Green Belts the tools to pass every phase of the DMAIC phase approval process with confidence.
Learn more: Lean Six Sigma Green Belt
Lean Six Sigma Black Belt
Black Belts lead complex, high-impact projects and often mentor Green Belts through their own tollgate reviews. This advanced certification builds deep competency across all five DMAIC phases, including advanced statistical analysis for the Analyze phase, Design of Experiments for the Improve phase, and robust control planning for the Control phase. Black Belts trained through this program are equipped to lead projects that deliver measurable, finance-validated results.
Learn more: Lean Six Sigma Black Belt
Final Thoughts on Running a Disciplined DMAIC Tollgate Review
A sponsor who asks hard questions at every tollgate review protects the project, the team, and the organization's investment in Lean Six Sigma. The 25 questions in this DMAIC tollgate checklist give you a practical, phase-specific framework to evaluate evidence, identify warning signs, and make confident approval decisions. When every phase gate review is treated as a real decision point rather than a formality, projects deliver results that last well beyond project closure.
Air Academy Associates offers expert Master Black Belt-led DMAIC coaching to sharpen every tollgate review. Our certified instructors help sponsors ask the right questions at every phase. Get started with us today.
FAQs
What Is a DMAIC Tollgate Checklist?
A DMAIC tollgate checklist is a set of standard questions used by sponsors and project leaders to confirm each phase deliverable is complete, accurate, and ready to proceed. It helps ensure the team is solving the right problem, using data correctly, managing risk, and staying aligned to business goals—an approach we've reinforced across decades of Lean Six Sigma training and consulting.
What Are the Tollgates in DMAIC?
The DMAIC tollgates align to the five phases: Define, Measure, Analyze, Improve, and Control. Each tollgate is a formal review point where the sponsor verifies that required outputs (such as a validated problem statement, reliable measurement system, proven root causes, tested solutions, and a control plan) are in place before approving the next phase.
What Should Be Included in Each DMAIC Tollgate Review?
Each review should include: phase deliverables and evidence (data, analyses, and documentation), progress versus the charter and timeline, risks/issues and mitigation plans, stakeholder and change-management updates, and a clear decision (go/hold/redirect) with agreed next steps. Strong tollgates focus on real-world proof—not just completed templates—consistent with how we teach teams to drive measurable results.
Who Participates in a DMAIC Tollgate Review and What Are Their Roles?
Typical participants include the Sponsor (approves scope, resources, and phase exit), Project Leader/Green or Black Belt (presents work and next steps), Process Owner (commits to sustaining changes), Subject Matter Experts (provide technical/process input), Finance (validates benefits when applicable), and the Master Black Belt/Coach (ensures methodological rigor and helps remove barriers).
Where Can I Find a DMAIC Tollgate Checklist Template?
You can find DMAIC tollgate checklist templates through reputable Lean Six Sigma training providers, professional associations, or course toolkits. Air Academy Associates provides practical, field-tested tollgate checklists and sponsor questions as part of our Lean Six Sigma training and coaching, tailored to your industry and project governance needs.
Related Articles:
