Quality
Coaching: When Your Quality Professional Stops Being the Cop and Starts
Being the Coach — and Your Organization Learns to Police Itself
The Quality Officer
Nobody Invited to Lunch
Let me tell you about Martin.
Martin was a quality manager at a mid-size automotive supplier in
Central Europe. He had the credentials — ASQ CQE, ISO 9001 Lead Auditor
certification, fifteen years of experience. He knew every clause of IATF
16949 by heart. His FMEAs were meticulous. His control plans were
poetry.
Nobody invited Martin to lunch.
When Martin walked onto the shop floor, operators stiffened. When he
entered a production meeting, the room temperature seemed to drop. When
he sent an email, people opened it the way you open a letter from the
tax authority — with dread.
Martin wasn’t a bad person. He wasn’t mean or arrogant. He was
thorough, precise, and absolutely convinced that his job was to catch
what everyone else was doing wrong. And he was very, very good at that
job.
The problem? The more defects Martin caught, the more defects
appeared. The more nonconformances he wrote, the more defensive people
became. The more he audited, the less anyone wanted to talk to him. His
quality system was technically perfect — and culturally bankrupt.
Then something changed.
Martin’s company hired an external consultant named Dr. Helena
Novakova for a leadership development program. She spent two days with
the quality team, and at the end of it, she asked Martin one question
that rearranged his entire professional identity:
“Martin, if you stopped coming to work tomorrow, would quality
get worse — or would nobody notice?”
Martin sat with that question for a long time. Because the honest
answer was: quality would get worse. Quickly. Not because the system was
broken, but because the system depended entirely on him. He was the
quality conscience of the organization — and he was the only one who had
one.
That’s when Martin started becoming a quality coach. And that’s when
everything changed.
The Audit
Trap: When Quality Becomes a One-Man Show
Most quality professionals fall into what I call the Audit
Trap. It works like this:
- You join an organization as a quality engineer or manager
- You discover that processes are messy, documentation is incomplete,
and people don’t follow procedures - You start catching problems — writing NCs, issuing corrective
actions, holding people accountable - You become known as the person who finds what’s wrong
- People start hiding problems from you instead of bringing them to
you - You find fewer problems — not because quality improved, but because
visibility decreased - You double down on auditing, convinced that tighter surveillance is
the answer - The cycle deepens
Sound familiar? It should. This pattern plays out in manufacturing
plants around the world, every single day. And it’s not because quality
professionals are wrong to care about standards. It’s because they’re
using the wrong tool for the wrong job.
Auditing finds problems. Coaching prevents them.
That’s not a semantic difference. That’s the difference between a
quality department that costs money and a quality culture that makes
money.
What Is Quality Coaching,
Really?
Quality coaching is the practice of developing quality capability in
others so that quality becomes embedded in how people think, not just in
what forms they fill out.
It’s built on a fundamental shift in identity:
| The Quality Cop | The Quality Coach |
|---|---|
| Finds defects | Builds defect prevention capability |
| Writes nonconformances | Asks questions that reveal root causes |
| Audits compliance | Develops understanding |
| Owns the quality system | Teaches others to own the quality system |
| People hide problems from them | People bring problems to them |
| Measures what went wrong | Measures what’s being learned |
| Creates dependence | Creates independence |
This isn’t soft. This isn’t about being nice instead of being
rigorous. Quality coaching is, in many ways, harder than traditional
quality management — because it requires you to be rigorous about
people’s development, not just their output.
A quality coach doesn’t say, “You filled out this control chart
wrong.” A quality coach says, “Walk me through why you chart this
parameter. What does it tell you? What would you do if it moved outside
the control limits? How would you know?” And then listens — really
listens — to the answer.
The Five Practices of a
Quality Coach
After studying organizations where quality coaching transformed
performance — and living through that transformation myself — I’ve
identified five practices that separate coaches from cops.
Practice 1: Ask Before Tell
The most powerful quality tool isn’t the control chart or the FMEA.
It’s a well-timed question.
When an operator makes a mistake, the cop says: “You didn’t
follow the procedure. Redo it.”
The coach says: “Help me understand what happened. What did you
see? What were you expecting to see?”
This isn’t coddling. It’s diagnostic. The operator who made the
mistake knows things about the process that no procedure manual can
capture. They know what the machine sounds like when it’s drifting. They
know which raw material batches feel different. They know the
workarounds that everyone uses but nobody documents.
When you ask before you tell, you access that knowledge. When you
tell before you ask, you shut it down.
The rule: Before issuing any corrective action, ask
three questions. If you can’t ask the person closest to the problem,
you’re not solving the problem — you’re solving your version of it.
Practice 2: Teach
the Why, Not Just the What
I once visited a plant where every operator could recite the seven
quality tools from memory. Posters hung on every wall. Control charts
were filled out perfectly.
But when I asked one operator why she measured a critical dimension
at that specific point in the process, she looked at me blankly.
“Because the procedure says so,” she said.
That operator wasn’t doing quality. She was doing compliance. And
compliance breaks the moment the procedure isn’t looking.
A quality coach teaches the why:
- Why does this dimension matter to the customer?
- Why do we measure it at this station instead of the next
one? - Why is the tolerance 0.05mm and not 0.10mm?
- Why does a shift in this parameter predict a defect 47
steps later?
When people understand the why, they don’t follow procedures because
someone told them to. They follow procedures because they understand
what happens when they don’t. And that understanding makes them vigilant
in ways that no audit schedule can replicate.
The rule: Every procedure should have a “why”
section. Not a technical justification for the auditor — a human
explanation for the operator.
Practice 3: Make Learning
Visible
In most organizations, quality lessons are invisible. A defect
happens, a root cause is found, a corrective action is implemented, and
the whole thing disappears into a database that nobody reads.
A quality coach makes learning visible. They create “lesson learned”
boards on the shop floor — not in a database, but on a physical wall
where operators can see what went wrong, why it went wrong, and what
changed as a result. They start shift meetings with a two-minute quality
story. They celebrate near-misses the way most organizations celebrate
zero-defect days, because near-misses mean someone was paying
attention.
When learning is visible, people learn from each other instead of
repeating each other’s mistakes. The operator on Shift A who caught a
subtle drift in a welding parameter becomes a teacher for the operator
on Shift B who’s about to run the same job — not through a memo nobody
reads, but through a conversation that happened because the learning was
made visible.
The rule: If a quality lesson is stored in a
computer and not displayed where people work, it doesn’t exist.
Practice 4: Build Quality
Champions
Martin — the quality manager from our opening story — realized that
he couldn’t be everywhere. His plant had 240 operators across three
shifts, and he was one person. No matter how hard he audited, he could
only see a fraction of what was happening.
So he started building quality champions.
He identified one operator per shift — not the senior person, not the
most educated person, but the person others naturally turned to when
something went wrong. He spent thirty minutes a week with each champion,
teaching them basic quality tools: how to read a control chart, how to
use a simple 5-Why, how to spot the difference between common cause and
special cause variation.
He didn’t give them a title. He didn’t give them extra pay. He gave
them knowledge and confidence.
Within six months, those three champions were solving 60% of quality
issues at the source — before they became formal nonconformances. Within
a year, other operators were coming to the champions for help. Martin
hadn’t just added three people to his quality team. He had started
building a quality culture.
The rule: Your quality department should be measured
not by how many problems it solves, but by how many people outside the
quality department can solve quality problems.
Practice 5: Replace
Judgment With Curiosity
This is the hardest practice, and the most important.
When a defect reaches the customer, the natural human response is to
find out who messed up. The cop asks: “Who didn’t follow the
procedure?” The coach asks: “What about our system made it easy
for this to happen — and hard for someone to catch it?”
This shift from judgment to curiosity is the foundation of a just
culture — not a blame-free culture, because accountability matters, but
a culture where the first question is always about the system, not the
person.
In practice, this means:
- Never blame an operator for a defect that the system should
have caught. If a defect can be produced by one person’s
mistake and nobody downstream can detect it, the system is the problem —
not the person. - Always investigate the conditions that made the error
possible. Was the operator fatigued? Was the instruction
ambiguous? Was the environment noisy, hot, or distracting? Was the
tooling worn? These aren’t excuses — they’re design flaws in your
process. - Celebrate the person who reports the problem. If
someone brings you a defect they found, your first response should be
“thank you” — not “how did this happen?” The defect happened because
your process allowed it. The person who found it just did you a
favor.
The rule: Every quality incident investigation
should start with the system and end with the system. The human is
always part of the system — never outside it.
The Business Case:
Why Coaching Beats Coping
If the cultural argument doesn’t convince you, let me make the
financial one.
A study by the American Society for Quality found that organizations
with embedded quality cultures — where quality is everyone’s
responsibility, not just the quality department’s — have 35-50%
lower cost of poor quality than organizations that rely on
inspection and audit-based quality systems.
Why? Because:
- Prevention is cheaper than detection. Every defect
caught by an operator at the source costs a fraction of one caught by a
quality inspector three steps later — and a tiny fraction of one caught
by the customer. - Coaching scales. Auditing doesn’t. One quality
coach who develops ten quality champions creates a multiplier effect.
One auditor who audits harder just creates more paperwork. - Coaching creates psychological safety. When people
aren’t afraid of the quality department, they report problems faster.
Problems reported faster are problems solved cheaper. - Coaching reduces turnover. Quality professionals
who act as coaches report higher job satisfaction and lower burnout than
those who act as enforcers. And operators who feel supported rather than
policed stay longer and perform better.
A
Practical Framework: The 90-Day Quality Coaching Transformation
If you’re a quality professional reading this and thinking, “I want
to do this, but I don’t know where to start,” here’s a 90-day
roadmap:
Days 1–30: Observe and Listen
- Stop issuing nonconformances for 30 days. (Seriously. Just
stop.) - Instead, spend those 30 minutes per day on the shop floor, asking
questions. - Your only job this month is to understand how people actually
experience quality in your organization. - Keep a journal. Write down what you hear.
Days 31–60: Teach and
Experiment
- Pick one process area and start teaching the “why” behind the
procedures. - Identify your first quality champion candidate.
- Introduce one visible learning tool — a “lesson learned” board, a
quality story at shift start, a defect prevention wall. - Run your first coaching conversation using only questions — no
directives.
Days 61–90: Build and Expand
- Formalize your quality champion program with regular coaching
sessions. - Replace one audit activity with one coaching activity.
- Measure the difference: Are problems being reported earlier? Are
repeat nonconformances decreasing? Are people coming to you with
solutions instead of hiding problems? - Share what you’ve learned with your leadership team.
The Real Measure of
a Quality Professional
There’s a question I ask every quality professional I mentor:
“If you got hit by a bus tomorrow, would your organization’s
quality improve, stay the same, or get worse?”
If the answer is “get worse,” you’ve built dependence. You’re a cop —
maybe a very effective one, but still a cop. The organization depends on
your vigilance because it hasn’t developed its own.
If the answer is “stay the same” — or even “improve” — then you’ve
built a system where quality lives in the people, the processes, and the
culture. You’ve made yourself less necessary. And paradoxically, that’s
when you become most valuable.
Martin — the quality manager nobody invited to lunch? After two years
of quality coaching, he walked into the cafeteria one afternoon and
found three operators waving him over to their table. They wanted to
tell him about a process improvement they’d discovered on their own.
They didn’t need him to find the problem. They needed him to
celebrate the solution.
That’s quality coaching. That’s when quality stops being a department
and starts being a culture.
And that’s when you finally get invited to lunch.
Peter Stasko is a Quality Architect with 25+ years of experience
transforming manufacturing organizations from inspection-dependent to
prevention-driven. He specializes in building quality cultures where
every employee is a quality professional — whether their job title says
so or not.
