5.10 Project Charter Reviews and Toll-Gate Governance

ASQ Certified Six Sigma Black Belt CSSBB

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CSSBB Exam Strategy

1.1 CSSBB Exam Format, Scoring, and Testing Windows 1.2 Eligibility, Project Affidavits, Application, and Recertification 1.3 Open-Book Strategy, Reference Materials, and a 16-Week Study Plan

2 Chapter 2: Organization-Wide Planning and Deployment

2.1 Fundamentals of Six Sigma and Lean Methodologies 2.2 Selecting the Right Methodology: DMAIC, DFSS, and Lean 2.3 Business Systems, Processes, and Stakeholder Relationships 2.4 Strategic Planning and Deployment of Six Sigma Initiatives 2.5 Six Sigma Roles and Responsibilities 2.6 Organizational Barriers and Common Causes of Six Sigma Failure 2.7 Change Management: Stakeholder Analysis, Readiness, and Communication

3 Chapter 3: Organizational Process Management and Measures

3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders 3.2 Benchmarking Types and Performance Goal Setting 3.3 Performance Measures: Balanced Scorecard, KPIs, KBIs, OKRs, and Line of Sight 3.4 Leading and Lagging Indicators and Performance Dashboards 3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis 3.6 Cost of Poor Quality and Hard versus Soft Savings

4 Chapter 4: Team Management

4.1 Team Types and Constraints 4.2 Team Roles, Responsibilities, and Member Selection 4.3 Team Success Factors and Ground Rules 4.4 Motivational Techniques and Overcoming Demotivators 4.5 Stages of Team Development and Conflict Resolution 4.6 Team Communication Plans 4.7 Team Leadership Models: Direct, Coach, Support, and Delegate 4.8 Group Behaviors, Conflict Resolution, and Meeting Management 4.9 Facilitation Techniques and Team Decision-Making Methods 4.10 Team Training: Needs Assessment, Delivery, and Evaluation

5 Chapter 5: Define Phase

5.1 Customer Identification and Segmentation 5.2 Customer Data Collection: Methods, Validity, and Reliability 5.3 Customer Requirements: CTX, CTQ Trees, and Operational Definitions 5.4 The Kano Model and Quality Function Deployment 5.5 SIPOC and Process Mapping 5.6 Business Case Justification 5.7 The Project Charter and the Problem Statement 5.8 Project Scope and Boundaries 5.9 SMART Goals and Project Performance Measurements 5.10 Project Charter Reviews and Toll-Gate Governance 5.11 Project Management Tools: Gantt Charts, Toll-Gate Reviews, WBS, and RACI 5.12 Analytical Tools Used Throughout the DMAIC Cycle

6 Chapter 6: Measure Phase

6.1 Process Flow Metrics and the Hidden Factory 6.2 Process Analysis Tools and Value Stream Mapping 6.3 Types of Data and Measurement Scales 6.4 Sampling Concepts, Methods, and Sample Size for Estimation 6.5 Data Collection Plans and Common Pitfalls 6.6 Gage R&R for Variable Measurement Systems 6.7 Attribute Agreement Analysis and Audit MSA 6.8 Measurement Systems Across the Organization, and Metrology 6.9 Population Parameters, Sample Statistics, and Valid Statistical Conclusions 6.10 Descriptive Statistics: Central Tendency, Dispersion, and Shape 6.11 Graphical Methods for Exploratory Data Analysis 6.12 Probability Concepts, Common Distributions, and the Central Limit Theorem 6.13 Additional Distributions: Hypergeometric, Exponential, Lognormal, Weibull, and Bivariate 6.14 Process Capability and Performance Indices 6.15 Capability Studies, Attributes Capability, Yield Metrics, and Long-Term Capability

7 Chapter 7: Analyze Phase

7.1 The Correlation Coefficient, Its Confidence Interval, and Causation 7.2 Linear Regression and Residual Analysis 7.3 Multivariate Tools: Factor Analysis, Discriminant Analysis, and MANOVA 7.4 Hypothesis Testing Terminology, Errors, and Single-Sample Tests 7.5 Statistical Versus Practical Significance 7.6 Sample Size for Hypothesis Tests 7.7 Point Estimates, Confidence, Prediction, and Tolerance Intervals 7.8 Tests for Means, Variances, and Proportions 7.9 Analysis of Variance 7.10 Chi-Square Goodness-of-Fit and Tests of Independence 7.11 Types of Risk and Failure Mode and Effects Analysis 7.12 Gap Analysis and Root Cause Analysis 7.13 Waste Analysis: The Seven Classic Wastes and Resource Under-Utilization

8 Chapter 8: Improve Phase

8.1 Design of Experiments: Objectives, Terminology, and Effects 8.2 DOE Design Principles: Randomization, Blocking, Replication, and Resolution 8.3 Planning and Evaluating Designed Experiments 8.4 One-Factor Experiments: Completely Randomized, Randomized Block, and Latin Square Designs 8.5 Full Factorial Experiments and Design Selection 8.6 Two-Level Fractional Factorial Experiments and Confounding 8.7 Response Surface Methodology and Optimization 8.8 Waste Elimination: Pull Systems, Kanban, 5S, and Poka-Yoke 8.9 Cycle-Time Reduction: Continuous Flow, SMED, and Heijunka 8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE 8.11 Implementation Planning, Piloting, and Solution Selection

9 Chapter 9: Control Phase

9.1 SPC Objectives, Variable Selection, and Rational Subgrouping 9.2 Control Charts for Variables Data 9.3 Control Charts for Attributes Data 9.4 Short-Run SPC and Moving Average Charts 9.5 Control Chart Analysis: Common Cause, Special Cause, and Run Rules 9.6 Total Productive Maintenance and Visual Controls 9.7 Measurement System Reanalysis 9.8 Control Plan Development and Process Owner Handoff 9.9 Lessons Learned, Documentation, and Training for Sustainment 9.10 Ongoing Evaluation of the Improved Process

10 Chapter 10: Design for Six Sigma (DFSS)

10.1 DFSS Frameworks: DMADV, DMADOV, and Design Transfer 10.2 Design for X (DFX) 10.3 Robust Design, Parameter Design, and Verification 10.4 Tolerance Design and Statistical Tolerancing

5.10 Project Charter Reviews and Toll-Gate Governance

Key Takeaways Explain This Topic AI

A charter review re-validates the problem, scope, goal, benefit, resources, and risks against what the team has learned since the last gate.

A toll gate is a decision point where the sponsor approves the phase, returns it with named gaps, or cancels the project.

Cancelling a project at a toll gate is a legitimate and valuable outcome, not a failure of the team.

Charter drift is silent scope change that no sponsor approved, and it is what produces disputes at closure.

Benefit estimates should tighten at each gate, moving from an order-of-magnitude Define figure to a finance-validated number at Control.

Last updated: August 2026

• Why charters must be reviewed
• A Define-phase charter is written with the least information the team will ever have. Almost

everything in it is provisional:

• Charter element Why it changes
• Baseline Measure-phase data usually differs from the initial estimate, sometimes materially

Scope Stratification often shows the problem is concentrated in a narrower slice, or the root cause lies upstream

• Goal Entitlement analysis in Analyze reveals what is actually achievable
• Benefit The estimate tightens as the solution becomes concrete
• Resources Requirements shift as the analysis and then the implementation dominate
• Risks New risks appear; assumed risks fail to materialize
• Team Members join or leave as phases change
• A charter never reviewed becomes a historical document that the team quietly stops referring to. That
• is charter drift : the project people are actually doing diverges from the project the sponsor
• approved, and nobody notices until closure, when the sponsor asks about a benefit that stopped being

in scope four months ago.

What a charter review covers

Run it as a short standing item at each toll gate rather than as a separate ceremony.

Is the problem statement still accurate? Has the measured baseline changed the numbers?

Is the scope still right? Anything added, removed, or discovered outside the boundary?

Is the goal still both achievable and worth achieving?

Has the benefit estimate changed, and in which direction?

Are the resources still committed and sufficient?

Have the risks changed?

Is the sponsor still the right sponsor? If the root cause moved into another function, the

answer is often no.

Every answer that is "no" produces either an updated charter signed by the sponsor, or an explicit

decision to continue unchanged. Both are acceptable; silence is not.

• Toll gates
• A toll gate (sometimes called a phase gate or tollgate review) is a decision point , not a status

presentation. The sponsor has exactly three options:

Approve : the phase criteria are met; proceed and release the next phase's resources.

Return : named gaps must be closed; the gate reconvenes on a stated date.

Cancel : the project should stop.

• Cancelling matters. A deployment where no project is ever cancelled is not exercising judgment, and
• Black Belt capacity is the scarcest resource in the system. Legitimate reasons to cancel at a gate: the
• measured baseline shows the problem is far smaller than believed; the root cause is outside any
• feasible scope; the process is being replaced by a capital project; a regulatory or business change has
• removed the need. Cancelling at Measure after six weeks is a good outcome compared with discovering the

same fact at Improve after five months.

Phase-gate criteria

Gate Entry criteria to pass

Define Signed charter; problem statement with baseline; scope with in-frame and out-of-frame; SIPOC; customers identified and VOC translated to CTQs; team and resources committed; benefit estimate agreed with finance

Measure Operational definitions written; measurement system validated (MSA passed); data collection plan executed; baseline performance and capability established; problem statement refined with actual data

Analyze Potential causes identified and screened; root causes confirmed with data or statistical evidence; entitlement understood; goal validated as achievable

Improve Solutions generated and selected against criteria; risk assessed (FMEA); pilot run and results verified statistically; full implementation plan approved

Control Control plan in place and owned; process owner has formally accepted; training completed; documentation updated; benefit validated by finance; lessons learned captured; project closed

• The single most useful discipline is that Measure does not pass without a validated measurement
• system . Every subsequent phase depends on the data, and an MSA failure discovered in Analyze

invalidates everything after it.

• Who attends
• Sponsor : mandatory. If the sponsor cannot attend, reschedule rather than proceeding without a

decider; a gate without the decider is a status meeting.

Process owner : mandatory from Measure onward, because they will inherit the control plan.

Master Black Belt or deployment lead : methodology quality assurance.

Finance representative : at Define to agree the benefit basis and at Control to validate it.

Affected function leads : where the phase's decisions touch them.

• Running the gate
• Circulate a short pack in advance -- typically the updated charter one-pager, the phase evidence, the

decision being requested, and the risks. Then:

Ten minutes on what the data showed, not on what the team did.

The explicit decision request.

Risks and what the team needs from the sponsor.

The decision, recorded in the room with a date.

• A gate that ends without a recorded decision has not happened. The most common failure is a gate that
• runs long on methodology explanation, leaves no time for the decision, and defaults to "carry on",

which is approval without scrutiny.

Benefit tightening across gates

• Gate Benefit basis Typical accuracy
• Define Estimated from the gap and a closure fraction plus or minus 50%
• Measure Recomputed from the validated baseline plus or minus 30%
• Analyze Bounded by entitlement from the root-cause analysis plus or minus 20%
• Improve Based on measured pilot results plus or minus 10%
• Control Validated by finance from actual post-implementation performance Actual
• Showing this progression at each gate keeps the sponsor's expectation calibrated and removes the
• awkward conversation where a $400,000 Define estimate closes at $150,000 with no explanation of when

or why it changed.