When you certify belts, you get belts — not practitioners

A certification body published a piece this week debunking what it called "persistent myths" about online Six Sigma — apparently we should stop worrying that a self-paced exam produces self-paced thinkers. Hours later, a university press release celebrated its latest cohort of Lean Six Sigma belt graduates. Photographs. Congratulations. A quote about empowerment. What I did not see in either piece was a single solved root cause. No PFMEA. No defect rate. No euros saved. No customer satisfaction metric. Not even a scrap of evidence that anyone in either story had stood near a production line and been personally accountable for what came off it.

This is not a complaint about training. Training matters. The complaint is structural: the certification industry has positioned itself as a proxy for practitioner skill, and two decades of quality outcomes across manufacturing prove — loudly — that it is not.

What a course teaches you and what a production line teaches you

A Six Sigma course will teach you DMAIC. Hypothesis testing, control charts, the anatomy of an FMEA. Useful things — and things you can learn from a textbook in an afternoon, which is precisely why a certificate proves you read the textbook and nothing more.

A production line teaches you something different. A PFMEA is not a document you complete before the audit. It is a living argument between engineering, quality, and operations about what will go wrong next, written in the language of severity, occurrence, and detection — and revised at two in the morning when something does. QRQC is not an acronym on a laminated card. It is a culture where the operator who spots the defect has the authority to stop the line, and the management chain responds in minutes, not days.

At SNOP, I inherited a greenfield plant with 900+ people and no QA/QC department. Bare concrete, a hiring plan, and a customer who expected parts on Monday. The 70% reduction in defect costs we achieved did not come from a DMAIC template handed down by a training provider. It came from PFMEA discipline enforced on the floor, QRQC sessions that were short, brutal, and honest, and a Q-Wall that made problems visible before they escaped. Building that department from nothing taught me more about variation, systems thinking, and human factors than any certification programme ever could. The line does not care about your belt colour. It cares about whether you closed the loop.

If you can pass the exam but cannot answer the operator's question, your belt is holding up your trousers and nothing else.

The certification economy — who profits when everyone is qualified

The certification industry is not a charity. Every belt issued is revenue. Every re-certification cycle is recurring revenue. Every "myth" debunked in a trade publication is marketing dressed as public service. The business model depends on a steady supply of professionals who believe — or are told by their HR departments — that a belt is a career requirement rather than a tool.

The result is an economy where everyone is qualified and nobody is accountable. I have sat across from Green Belts and Black Belts who could recite the definition of special-cause variation but could not tell me the last time they closed an 8D. I have reviewed supplier quality systems where the certification wall was impressive and the outgoing defect rate was not. The certificates are real. The credentials are not.

Sector-level data tells the story nobody wants to read. External audit findings, customer escalations, warranty costs — these numbers do not move because a workforce got belted. They move when leadership enforces discipline, when the floor owns the problem, and when the tools are used as instruments rather than decorations.

The tools that survive the floor

My inventory, built over twenty years and two industries.

PFMEA, QRQC, A3 thinking, 8D with actual containment, control plans that operators can read at a glance, go/no-go gauges that are calibrated and used. SPC when it drives a decision rather than decorating a board. Routing Verification KPIs that catch a deviation before it becomes a discrepancy. These survive because someone owns the risk they describe.

What survives only in slide decks: DMAIC as a linear script. Value stream maps that took six weeks to draw and were never updated. "Lessons learned" databases nobody opens. Capability studies presented in audits and never revisited since launch. These survive because someone needs them for the next quarterly review.

The difference is not complexity. It is accountability.

Fifteen minutes to separate a practitioner from a certificate holder

I have hired, evaluated, and rejected enough quality professionals to have this down to a conversation. Walk me through the last defect you personally contained — the root cause, how you verified it. A practitioner gives you the part, the failure mode, the containment action, and the sound the tool made when it broke. A certificate holder tells you about "applying DMAIC."

Then ask when they last updated a PFMEA, and what triggered the revision. "Before the audit" ends the conversation.

Ask what their last QRQC cost the business — in euros, in hours, in stopped production. A practitioner knows. They were there.

Your hiring process probably cannot do this. Most are designed to verify credentials rather than interrogate experience. The CV lists the belt. The panel checks the box. Nobody asks what the belt actually did.

The certification industry will continue to issue belts. Universities will continue to celebrate graduates. Neither will mention that quality is not a credential — it is a set of behaviours, enforced daily, measured in defects prevented and euros saved, built on the floor by people who own the result. Until we stop confusing the certificate for the work, we will keep certifying belts and wondering why the numbers do not move.