The
Promise That Sold a Billion Dollars in Consulting
Six Sigma arrived with an extraordinary claim: by applying
statistical rigor to your processes, you could reduce defects to 3.4 per
million opportunities. Motorola popularized it in the 1980s. General
Electric made it famous in the 1990s. By the 2000s, every Fortune 500
company either had a Six Sigma program or felt embarrassed about not
having one.
The premise is sound. Define, Measure, Analyze, Improve, Control —
five phases, each with specific tools, each grounded in data.
Statistical thinking replaces gut feeling. Variation becomes the enemy.
Control charts, capability studies, and hypothesis tests give you a
language for quality that doesn’t depend on who shouted loudest in the
meeting.
But here is what happened in practice at thousands of companies: Six
Sigma stopped being a problem-solving methodology and became a
certification program. The belts — Yellow, Green, Black, Master Black —
were supposed to signify demonstrated competence. Instead, they became
HR credentials. You attended a two-week course, passed a multiple-choice
exam, completed a project that may or may not have been real, and
received a title that went on your business card and your LinkedIn
profile.
The organization now had hundreds of Green Belts, dozens of Black
Belts, and a handful of Master Black Belts. What it didn’t have was
fewer defects.
How the Belt
System Corrupted the Methodology
The belt hierarchy was borrowed from martial arts, which was either a
brilliant marketing decision or an accidental confession. In martial
arts, a black belt means you have mastered fundamentals through years of
practice under direct supervision. In Six Sigma, a Black Belt often
means you attended four weeks of training over six months and submitted
a project report that someone reviewed for statistical correctness but
not for business impact.
This created a predictable distortion. People pursued belts for
career advancement, not for process improvement. The certification
became the goal. The project was the vehicle for the certification, not
the other way around. And since the certification body — often internal
— had every incentive to pass people (a high failure rate would make the
program look bad and reduce enrollment), the standards drifted.
A Green Belt project was supposed to deliver measurable financial
impact. In practice, the financial impact was often calculated using
creative accounting that would make an auditor weep. A process
improvement that saved $50,000 in theory — based on assumptions about
labor rates, defect costs, and throughput that nobody verified — was
reported as $500,000 in annualized savings on the project charter. The
finance department signed off because that was the process, and the
process had to be followed even when the process was the problem.
Black Belt projects had the same issue at a larger scale. A Master
Black Belt — supposedly a mentor who had delivered millions in savings —
was often someone who had been in the organization long enough to
accumulate project credits, not someone whose projects had actually
survived contact with reality. The promotion criterion was the number of
projects completed, not whether the improvements held twelve months
later.
DMAIC Became Data-Driven
Theater
The five-phase DMAIC framework is genuinely useful when applied
honestly. Define the problem. Measure the current state. Analyze root
causes. Improve the process. Control the new process to hold the
gains.
But in a belt-driven culture, each phase became a deliverable to
check off rather than a discipline to practice.
Define became an exercise in scoping the project so
narrowly that success was guaranteed. Instead of “reduce warranty
returns by 30%,” the problem statement became “reduce Dimension A
variation on Part Number 12345 from 0.15mm to 0.08mm.” This is a real
problem, but it’s a tiny problem, and solving fifty tiny problems while
ignoring the systemic issue causing all of them is not improvement. It’s
whack-a-mole with statistical software.
Measure became a data collection exercise where the
measurement system itself was never validated. People who had completed
Gage R&R studies in training — and passed the exam — proceeded to
collect data with uncalibrated instruments, inconsistent operator
methods, and sampling plans that captured the wrong population. The
DMAIC report included a Gage R&R slide because the template required
it, but the actual data driving decisions came from whatever was easiest
to measure, not what was most relevant.
Analyze became a parade of statistical techniques
applied because the belt curriculum required demonstrating proficiency,
not because the data called for them. ANOVA on a sample of twelve data
points. Regression models with nine predictor variables and twenty-three
observations. Multi-vari charts that looked impressive in a PowerPoint
but showed effects smaller than the measurement error. The statistics
were technically present but substantively meaningless.
Improve became whatever change the team had already
decided on before the project started. The statistical analysis existed
to justify the predetermined solution, not to discover it. If the data
didn’t support the preferred answer, the data was re-collected,
re-grouped, or re-interpreted until it did.
Control became a control plan that was filed in the
same binder as the FMEA and never looked at again. The process reverted
to its old behavior within months, but since the project was already
closed and the savings already booked, nobody measured the
backslide.
The Cost of Six Sigma
That Nobody Counted
Here is the expense report your organization never filed: the fully
loaded cost of every Black Belt pulled off their regular job for six
months of training. The opportunity cost of every engineer who spent
their days preparing DMAIC presentations instead of designing better
products. The consulting fees paid to the firm that certified your
Master Black Belts so they could certify your Black Belts so they could
certify your Green Belts — a pyramid scheme of credentials.
A typical Black Belt program costs between $15,000 and $30,000 per
person in training and certification fees alone. For an organization
with 100 Black Belts — not unusual for a large manufacturer — that’s
$1.5 to $3 million in direct training costs. Add the lost productivity,
the project hours, the internal infrastructure (the Six Sigma office,
the steering committee, the project tracking software, the annual
quality conference where belts present their projects to each other),
and you’re easily at $5 to $10 million per year.
Now ask the uncomfortable question: how many of those Black Belt
projects delivered real, verifiable, sustained financial impact? Not the
inflated numbers on the project charter. The actual, audited,
twelve-months-later, did-the-process-actually-change impact.
In most organizations, the honest answer is 10 to 20 percent. The
same ratio you’d get from almost any improvement initiative that didn’t
involve statistical software or colored belts.
When the Tools Become the
Purpose
The tools of Six Sigma are not the problem. Control charts are
useful. Design of Experiments is powerful. Capability analysis is
informative. Process mapping is valuable. These tools have helped
organizations solve real problems for decades.
The problem is what happens when the tools become the purpose rather
than the means.
When your organization values the number of belts certified more than
the problems solved, you get certified people who can’t solve problems.
When your organization values the statistical sophistication of a
project report more than the operational change it produces, you get
beautiful reports that describe processes that never improved. When your
organization values the Six Sigma brand more than the quality results,
you get a quality program that exists to perpetuate itself.
This is not unique to Six Sigma. It happened to ISO 9001. It happened
to Lean. It happened to every quality methodology that became a
movement, every movement that became an industry, and every industry
that became more invested in selling certifications than in delivering
results. Quality methodologies follow a predictable lifecycle:
innovation, adoption, institutionalization, dilution, and cargo-cult
compliance. Six Sigma is deep in the dilution phase at most
organizations.
The Manufacturing
Reality Nobody Talks About
Walk onto a shop floor at a company that has invested heavily in Six
Sigma. Ask the operators — not the engineers, not the managers, the
operators — whether anything has changed.
In the best case, they’ll tell you about one Black Belt who actually
came to the floor, watched the process, talked to people, and helped fix
something real. That person exists in every organization, usually one or
two individuals who would have been effective regardless of the
methodology because they care about the work and they respect the people
doing it.
In the worst case — and this is more common — they’ll tell you about
the Black Belt who arrived with a laptop and a template, asked questions
whose answers they didn’t understand, collected data they never shared,
ran analyses they couldn’t explain, presented results that didn’t match
reality, and then left to work on the next project. The process didn’t
change. The defects didn’t change. The only thing that changed was the
color of the belt on the person who briefly stood in their work
area.
The operators know where the defects come from. They’ve known for
years. They tried to tell someone once, and nobody listened. Then
someone with a Green Belt showed up and asked them to fill out a
fishbone diagram, and they wrote down what they’d been saying all along,
and the Green Belt put it in a PowerPoint, and the PowerPoint went into
a binder, and the binder went on a shelf next to the ISO 9001
procedures.
Six Sigma didn’t fail because the statistics were wrong. It failed
because the organization didn’t listen before the statistics, and it
didn’t change after the statistics. The belt system created a layer of
intermediaries between the problem and the solution, and those
intermediaries had more invested in their certification than in the
outcome.
What Actually Works
The organizations that have gotten real value from Six Sigma — and
some have — share certain characteristics that have nothing to do with
statistics:
Leadership involvement at the gemba. The CEO who
walks the floor and asks about the process is worth ten Master Black
Belts. The executive who reviews project results by going to see the
actual process change, not by reading the savings number on a slide, is
the executive whose organization actually improves.
Projects selected for business impact, not for belt
certification. When the project portfolio is driven by
strategic priorities — warranty reduction, throughput improvement, cost
of quality — the methodology serves the business. When the project
portfolio is driven by how many people need to complete certification
requirements, the business serves the methodology.
Honest measurement. The organization that audits its
own savings claims with the same rigor it applies to its product
inspections is the organization that learns. Most organizations don’t,
because the inflated numbers look better in the annual report and the
deflated reality feels like failure.
Sustainability tracking. Twelve months after project
closure, is the process still improved? Eighteen months? Twenty-four? If
the answer is no, the control phase failed, which means the project
failed, regardless of what the charter says. Organizations that track
this honestly discover that their real improvement rate is far lower
than their reported improvement rate — and that discovery, uncomfortable
as it is, is the first step toward doing better.
Respect for the people doing the work. The operator
who has run the same machine for fifteen years knows more about that
process than any Black Belt with a statistical toolkit. Six Sigma works
when the belt is a facilitator who brings analytical tools to complement
operational expertise, not an expert who brings templates to override
it.
The Path Back to Meaning
You don’t need to abandon Six Sigma. You need to abandon what Six
Sigma became.
Strip away the belt hierarchy. Keep the tools. Train everyone in
basic statistical thinking — not to certify them, but to equip them.
Select projects based on what matters to the business. Measure results
honestly. Track sustainability. Go to the floor and stay there until you
understand the process better than the report does.
A Green Belt should not be a credential. It should be a skill. A
Black Belt should not be a title. It should be a demonstrated ability to
solve problems using data. A Master Black Belt should not be a rank. It
should be someone who has personally led changes that held, who has
mentored others to do the same, and whose track record can be verified
not by a certificate but by the processes they touched.
The 3.4 defects per million is achievable. Some organizations have
achieved it. But they didn’t achieve it by certifying people. They
achieved it by changing processes — one at a time, thoroughly,
permanently — with people who cared more about the outcome than about
the credential.
Your organization probably has those people already. They’re on the
shop floor. They’ve been telling you what’s wrong for years. Stop giving
them belts and start giving them authority.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality management, process
improvement, and organizational transformation. He has implemented and
evaluated quality systems across automotive, electronics, and heavy
industries, and writes about the gap between what quality methodologies
promise and what they actually deliver on the factory floor.
