Study guide

2.6 Organizational Barriers and Common Causes of Six Sigma Failure

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

2.6 Organizational Barriers and Common Causes of Six Sigma Failure

Key Takeaways Explain This Topic AI

Lack of management support and lack of resources are the two causes of Six Sigma failure ASQ names explicitly in the Body of Knowledge.

Functional silos block cross-functional DMAIC projects because authority over the process is split across managers with conflicting metrics.

Part-time Black Belts assigned less than full-time to projects are a resource failure disguised as a staffing decision.

Reward systems that pay for output volume or utilization actively oppose variation reduction and waste elimination.

ASQ tags this topic at the Apply level, so the exam presents a failing deployment and asks which barrier is operating and what to do about it.

Last updated: August 2026

  • Why deployments fail with good tools in the room
  • Six Sigma failures are rarely statistical. The methodology is mature, the tools are validated, and
  • the training is standardized. Deployments fail because the organization around the project makes
  • success structurally difficult. ASQ tags this topic at the Apply level, which means the exam will

hand you a symptom and expect the diagnosis.

  • Structural barriers
  • Functional silos. Most DMAIC projects cross departmental boundaries; most organizational charts
  • do not. When a value stream runs through purchasing, production, quality, and logistics, no single
  • manager owns the process, and each owns a metric that can be improved at the others' expense. The
  • countermeasure is structural, not motivational: a named executive sponsor with authority over the
  • whole value stream , a charter signed by every affected function, and a system-level project metric

that no single department can move alone.

Hierarchy and decision latency. In steep hierarchies, a Black Belt's recommendation queues behind

several approval levels, and the project's improve phase stretches past the sponsor's attention span.

The countermeasure is a pre-agreed decision-rights matrix in the charter: what the team may decide

alone, what the sponsor decides, and what escalates.

  • Geographic and shift dispersion. A process running across three shifts and two sites has three or
  • six versions of standard work. Data collected without stratifying by shift and site hides the largest

source of variation in the study.

Resource barriers

ASQ names lack of resources as a core cause of failure. In practice it takes four forms:

Form Symptom Countermeasure

Part-time Black Belts Project timeline slips repeatedly; belt is pulled to firefight Formal full-time assignment, backfilled day job

No measurement capability Team cannot get data on the CTQ; MSA fails Fund gauges and data systems in the charter

No implementation capital Solution identified but unfunded Pre-approve a capital band at charter approval

No subject-matter expert time Team relies on assumptions about the process Named SMEs with allocated hours in the charter

  • A Black Belt assigned "50% to projects" is, in effect, assigned 0% during any operational crisis --
  • which is exactly when the process data is most interesting. The full-time Black Belt model exists

because part-time assignment is the most common quiet cause of project failure.

  • Cultural barriers
  • Lack of management support is the failure ASQ names first, and it is usually visible in behaviour
  • rather than statements. Executives who publicly endorse Six Sigma but never attend a toll gate, never
  • ask about a control plan, and never fund an implementation have withdrawn support in the only

currency that matters.

  • Fear and blame. If the data will identify whose area causes the defects, people will manage the
  • data. Under-reporting, redefining defects, and "cleaning" records before the study are all rational

responses to a blame culture and all fatal to a Measure phase.

  • Not-invented-here and change fatigue. Organizations that have run several improvement programs
  • carry scar tissue. Frontline staff who watched the last initiative disappear will comply visibly and
  • revert quietly. This is a sustainment failure that shows up months after the project closes,

which is why VIII.D exists in the Body of Knowledge.

  • Reward system misalignment. This is the most under-appreciated barrier because it is invisible on
  • an org chart. If operators are paid for units produced, they will run through a marginal condition
  • rather than stop and adjust. If a plant is measured on machine utilization, it will overproduce and
  • build inventory. Improvement dies wherever the reward system pays for the behaviour the project is

trying to eliminate.

A diagnostic sequence

When a project stalls, work down the list in order; the first "no" is usually the real problem.

Is there a named sponsor with authority over the entire process in scope?

Is the project metric one that no single department can move alone?

Is the Black Belt's time formally protected, and the SME time allocated?

Can the team obtain trustworthy data without exposing an individual to blame?

Does any existing reward or target contradict the improvement?

Is there an approved funding path for the eventual solution?

Does the process owner accept accountability for the control plan after handover?

  • Worked example
  • A hospital charters a project to cut emergency-department boarding time. Six weeks in, the team
  • cannot get inpatient discharge timestamps, the sponsor is the ED director, and nursing unit managers

are measured on bed occupancy. The technical work is competent and the project is doomed.

  • The diagnosis is not "resistance to change". It is three specific, nameable barriers: the sponsor's
  • authority stops at the ED door (silo), the data lives in a system owned by another function (resource
  • and information), and the inpatient reward system pays for high occupancy, which is precisely the
  • condition that creates boarding (reward misalignment). The correct action is to re-sponsor the
  • project at the chief operating officer level, add inpatient nursing to the charter, and put a
  • system-level measure -- total time from decision-to-admit to bed occupancy -- in place of the ED-only

metric.