You remember the launch. The CEO stood in front of the company. There
were banners. There were coffee mugs printed with “Quality Is Everyone’s
Job.” There was a consultant — expensive, articulate, gone in six weeks.
The word “TQM” was everywhere: in the employee handbook, in the
quarterly report, in the all-hands presentation that nobody questioned
because nobody understood what it actually meant.
That was three years ago.
Today, the coffee mugs are in a breakroom cabinet nobody opens. The
banners came down when the walls were repainted. The consultant’s slides
are in a shared drive folder that hasn’t been accessed since the quarter
they were uploaded. And the quality problems you had before TQM? You
still have them. The difference is that now you have a word for the gap
between what you claim and what you do, and that word is “TQM,” and
nobody flinches when they say it because nobody remembers it was
supposed to mean something.
This is the story of Total Quality Management in most organizations.
Not the textbook story — the real one. The one where a philosophy that
transformed Japanese manufacturing gets reduced to a poster campaign in
an American factory, where a methodology that requires years of cultural
change gets launched in a kickoff meeting and abandoned in a quarterly
review, and where the most powerful quality framework ever conceived
becomes the most empty buzzword on the mission statement.
What TQM Actually Is
Before we talk about what goes wrong, let’s be clear about what TQM
is when it’s done right.
Total Quality Management is not a tool. It’s not a program. It’s not
an initiative with a start date and an end date. It is a management
philosophy — a fundamentally different way of running an organization —
built on a simple premise: quality is not a department, quality is not
an inspection step, quality is not a metric you track. Quality is the
organizing principle of the entire enterprise.
The “Total” means what it says. Everyone. Every function, every
level, every process, every decision. Not just the quality team. Not
just the production floor. Finance, HR, engineering, maintenance,
logistics, sales — all of them responsible for quality. All of them
measured on it. All of them expected to improve it continuously.
The “Quality” means more than conformance. It means meeting customer
expectations — stated and unstated, present and future. It means
designing quality into products and processes rather than inspecting it
in. It means reducing variation, eliminating waste, solving problems at
their root, and preventing defects rather than catching them.
The “Management” means leadership. Not slogans, not exhortation, not
“quality campaigns.” Active, daily, visible leadership that prioritizes
quality over short-term output, that invests in people’s capability to
improve their own work, that creates systems where doing the right thing
is easier than doing the wrong thing.
TQM was synthesized from the work of W. Edwards Deming, Joseph Juran,
and Kaoru Ishikawa, among others. It was the engine of Japan’s post-war
industrial transformation. It was the foundation of the Malcolm Baldrige
National Quality Award in the United States. And it was the
philosophical ancestor of Lean, Six Sigma, and every quality framework
that followed.
Done right, TQM transforms organizations. Done the way most
organizations do it, TQM is a poster on a wall.
How TQM Dies: The
Launch Without Foundation
The most common pattern is the grand launch. An executive reads a
book, attends a conference, or visits a company that does TQM well. They
return inspired. They hire a consultant. They schedule an all-hands
meeting. They announce that the company is “becoming a quality
organization.”
And then nothing happens.
Nothing happens because TQM cannot be launched. It can only be built
— slowly, deliberately, from the foundation up. The foundation is trust:
trust that leadership means what it says, trust that speaking up about
problems won’t get you punished, trust that quality will actually be
prioritized over output when the two conflict. That trust doesn’t exist
in most organizations, and it cannot be created by a speech or a
banner.
So the launch happens, and people listen politely, and they go back
to their workstations, and they wait. They wait to see if the words mean
anything. They wait to see if the quality team actually gets authority
or just gets responsibility. They wait to see if the production schedule
slows down when a quality issue is found. They wait to see if the
executive who launched TQM is still talking about it in six months.
In most cases, the answer to every question is no. The quality team
gets more meetings but not more authority. The production schedule
doesn’t change. The executive moves on to the next initiative. And the
workforce learns, once again, that this too shall pass.
The Seven Sins of Failed TQM
Organizations that fail at TQM tend to fail in predictable ways. Here
are the seven patterns that kill it every time.
1. Delegation to the
Quality Department
The most lethal mistake. The CEO says, “Quality is everyone’s
responsibility,” and then assigns TQM implementation to the Quality
Manager. This is the equivalent of saying, “Safety is everyone’s
responsibility,” and then making the Safety Manager responsible for
whether people get hurt. The words are nice. The structure tells the
truth.
When TQM is owned by the quality department, it becomes a quality
department initiative. And a quality department initiative is, by
definition, not Total. It’s Partial. It’s Departmental. It’s the
opposite of what the word means.
Real TQM is owned by the CEO. Not sponsored by the CEO, not
championed by the CEO — owned. Driven daily. Measured personally. If the
CEO doesn’t lead it, it doesn’t happen.
2. Training Without
Empowerment
The second most common pattern: train everyone in quality tools, but
don’t change the organizational structure that prevents them from using
those tools. You send people to a two-day workshop on problem-solving.
They learn about fishbone diagrams and 5 Whys and Pareto charts. They
come back excited. They identify a problem in their area. They propose a
solution.
And then nothing happens. Because their supervisor wasn’t trained. Or
the solution requires a budget approval that takes six months. Or the
engineering team doesn’t have time to help. Or the problem crosses
departmental boundaries and nobody has the authority to convene a
cross-functional team.
Training without empowerment is worse than no training at all. It
creates awareness of problems without the ability to solve them. It
breeds cynicism. And it guarantees that the next time you offer
training, people will attend with their arms crossed.
3. Measurement Without
Meaning
You know what most TQM scorecards look like. They have dozens of
metrics. They track everything: defect rates, rework rates, customer
complaints, on-time delivery, audit scores, training hours, corrective
actions open, corrective actions closed.
And nobody looks at them.
Nobody looks at them because the scorecard is a reporting exercise,
not a management tool. It’s generated monthly by the quality team,
distributed by email, filed in a folder, and never discussed in any
meeting where a decision is actually made. The numbers go up and down,
and the reaction is always the same: “That’s interesting. Let’s keep an
eye on that.”
Real TQM measurement is different. It’s selective — a few critical
metrics that directly reflect the organization’s quality priorities.
It’s visible — posted where people work, updated in real time,
understood by everyone. And it’s actionable — reviewed in daily and
weekly meetings where decisions are made, not in monthly reviews where
reports are presented.
4. Customer Focus
Without Customer Contact
TQM demands that organizations be customer-focused. Most
organizations interpret this as: track customer complaints, monitor
customer satisfaction scores, send surveys.
But here’s the thing: tracking complaints is not customer focus.
Monitoring satisfaction scores is not customer focus. Sending surveys is
not customer focus. These are measurement activities, and while they’re
useful, they don’t create the understanding that TQM requires.
Customer focus means knowing your customers. Visiting their
facilities. Watching them use your product. Listening to their
operators, their quality teams, their engineers. Understanding not just
what they specify but what they actually need. Understanding the
difference between their stated requirements and their real
expectations, and designing your processes to meet the latter, not just
the former.
In failed TQM implementations, nobody in the organization has direct
customer contact except the sales team. And the sales team’s incentives
are structured around volume, not quality, not understanding, not
long-term partnership. So the “customer focus” becomes a number on a
dashboard, and the gap between what customers need and what the
organization delivers grows wider every quarter.
5. Continuous
Improvement Without Continuity
Continuous improvement requires continuity. It requires that the
people who solve problems today are still around to benefit from the
solutions tomorrow. It requires that improvements build on each other —
that this month’s gains become next month’s baseline.
In most organizations, there is no continuity. The kaizen team that
solved the problem last quarter has been disbanded. The engineer who led
the improvement effort has been transferred. The operator who suggested
the fix has quit. And the process change that was implemented has
quietly drifted back to the old way because nobody owns the
standard.
True continuous improvement requires a culture where learning is
captured, standards are maintained, and knowledge is transferred. Where
a problem solved stays solved. Where an improvement made stays made.
This is unglamorous, repetitive work — standardization, documentation,
training, auditing — and it’s the work that most organizations skip
because it doesn’t feel like progress.
6. Process Focus
Without Process Discipline
TQM teaches that quality comes from improving processes, not from
inspecting outputs. This is correct. But most organizations interpret
“process focus” as “documenting processes” rather than “improving
processes.”
They spend months creating process flowcharts. They fill binders with
procedures. They get ISO certified. And the processes — the actual work,
as performed on the floor — don’t change. The documentation describes an
ideal process that nobody follows. The actual process is a set of
workarounds, shortcuts, and “we’ve always done it this way” habits that
bear no resemblance to the documented flow.
This is process focus without process discipline. The documentation
exists for the auditor, not for the operator. The process is something
you point to when someone asks, not something you follow when you work.
And the gap between documented and actual becomes the source of every
quality problem the organization can’t solve.
7.
Leadership Commitment Without Leadership Behavior
The seventh sin is the most fundamental. Leaders say they’re
committed to quality. They allocate budget. They attend the steering
committee. They approve the training plan. They sign the quality
policy.
But they don’t change their own behavior.
When the production target is behind, they push for output, not
quality. When a supplier quality issue requires rejecting a shipment,
they ask about the cost of the delay, not the cost of the defect. When a
quality problem requires stopping a line, they ask how long the stop
will last, not how long the problem has existed.
Leadership commitment without leadership behavior is worse than no
commitment at all. It teaches the organization that the words don’t
matter. It teaches people that quality is a priority only when it’s
convenient. And it makes every subsequent quality initiative harder
because people have been trained to wait for the real signal — which is
not what leaders say, but what they do when the pressure is on.
What Real TQM Looks Like
It’s easy to criticize. It’s harder to describe what success looks
like. So let me be specific.
In a real TQM organization, the CEO can tell you the top three
quality issues facing the company, what’s being done about them, and who
owns each one. Not because they memorized it for a presentation —
because they review it weekly and they personally involved in removing
obstacles.
In a real TQM organization, operators stop the line when they see a
problem. Not because they have authority delegated through a formal
policy — because the culture makes it unthinkable to pass a defect
downstream, and because every time they’ve stopped the line, the
response has been support, not punishment.
In a real TQM organization, cross-functional teams solve problems
together. Not in scheduled meetings with formal agendas — in spontaneous
conversations at the gemba, where people from engineering, quality,
production, and maintenance stand around a machine and figure out why
it’s producing parts out of tolerance.
In a real TQM organization, suppliers are partners. Not because they
have long-term contracts — because they’re involved in design reviews,
invited to improvement events, and treated as extensions of the
company’s own capability. Their problems are your problems, and your
investment in their improvement is seen as an investment in your own
quality.
In a real TQM organization, data drives decisions at every level. Not
in the sense that everyone has a dashboard — in the sense that when
someone proposes a change, the first question is “what does the data
show?” And if there’s no data, the response is “let’s collect some
before we decide.”
And in a real TQM organization, quality is not a function. It’s not a
department. It’s not even a priority. It’s the water the organization
swims in. It’s so deeply embedded in how people think, how they work,
how they make decisions, that nobody mentions it anymore because it
would be like mentioning that they breathe air.
The Uncomfortable Truth
Here’s the uncomfortable truth about TQM: it’s not complicated. The
concepts are straightforward. The tools are accessible. The methodology
is well-documented and freely available.
What’s hard about TQM is that it requires something most
organizations aren’t willing to give: time. Time to build trust. Time to
develop people. Time to solve problems at their root instead of patching
them for the next shipment. Time to let a culture of quality grow from a
few committed individuals to a few teams to a whole organization.
Most organizations want results in a quarter. TQM delivers results in
years. Most organizations want a tool they can implement. TQM is a
philosophy they must become. Most organizations want a consultant to
install. TQM is a culture they must build, person by person, day by day,
from the inside out.
The companies that succeeded with TQM — Toyota, Milliken, Motorola in
its prime, the Baldrige winners who sustained their performance — didn’t
succeed because they had better tools or smarter people. They succeeded
because their leaders made a multi-year, multi-decade commitment to a
way of operating that didn’t bend to quarterly pressures, didn’t waver
with leadership changes, and didn’t stop when the consultant left.
The companies that failed with TQM didn’t fail because TQM doesn’t
work. They failed because they wanted the outcomes without the
commitment. They wanted the results without the culture change. They
wanted the quality without doing the work that quality requires.
And so they got posters. And mugs. And a shared drive full of slides.
And the same quality problems they always had, now with a three-letter
acronym attached to them.
The Path Forward (If You’re
Serious)
If you’re reading this and recognizing your organization, here’s what
I’d suggest.
First, stop calling it TQM. The term is burned. Your workforce has
been through “TQM,” “Six Sigma,” “Lean,” and whatever else you launched
and abandoned. A new name won’t help, but the old name carries baggage.
Focus on what needs to change, not what to call it.
Second, pick one thing. Not seven pillars of quality excellence — one
thing. One process that produces defects. One supplier that causes
problems. One metric that reflects a real quality issue. Focus your best
people on that one thing. Solve it. Document what you learned. Then pick
the next thing.
Third, change one leadership behavior. Not seven behaviors across a
competency model — one. If you stop lines for quality issues, mean it.
If you prioritize root cause analysis over quick fixes, fund it. If you
invest in supplier development, staff it. Pick the behavior that sends
the clearest signal and change it visibly.
Fourth, measure whether you’ve changed. Not with a satisfaction
survey — with operational data. Are defects going down? Is rework
decreasing? Are problems being caught earlier? Are the same problems
recurring? If the numbers aren’t moving, the culture isn’t changing,
regardless of how the initiative feels.
And fifth — the hardest one — commit to years, not months. If you
can’t do that, don’t start. Another failed initiative is worse than no
initiative at all. It deepens the cynicism. It erodes the trust. It
makes the next attempt harder.
Quality is not a campaign. It’s not an initiative. It’s not a slogan
on a coffee mug. It’s the daily, relentless, unglamorous work of doing
things right, solving problems at their root, and refusing to accept
defects as normal — even when the schedule is tight, even when the
budget is lean, even when nobody’s watching.
That’s what Total Quality Management was always supposed to mean. The
fact that most organizations turned it into a poster doesn’t mean the
philosophy was wrong. It means the implementation was.
About the Author
Peter Stasko is a Quality Architect with over 25 years of experience
transforming manufacturing operations across automotive, electronics,
and industrial sectors. He has led quality management system
implementations, supplier development programs, and continuous
improvement initiatives on three continents. He writes about the gap
between quality theory and manufacturing reality — because he’s spent a
quarter-century living in it.
