In 2015, a mid-size automotive supplier in Bavaria did something
remarkable. Over the course of eighteen months, they implemented Six
Sigma, adopted Agile across every department, purchased a digital twin
platform, rolled out a company-wide 5S program, launched a Kaizen
initiative, hired a Lean consultant, and announced their transformation
into an “Industry 4.0 smart factory.” They did all of this
simultaneously. They held press events. They printed new banners for the
lobby. They sent their leadership team to conferences to present their
transformation story.
By 2017, their defect rate had increased by 22 percent. Their on-time
delivery had dropped to 78 percent. Two of their three largest customers
had issued formal quality warnings. The plant manager was replaced. The
banners came down.
What happened to that Bavarian supplier happens to organizations
everywhere, in every industry, on every continent. It is one of the most
pervasive and destructive forces in quality management, and most
companies do not even have a name for it. Psychologists call it the
Bandwagon Effect — the tendency to adopt behaviors, beliefs, and
practices simply because others are adopting them. In manufacturing, it
manifests as a compulsive hunger for the new, the trendy, the thing that
everyone else is doing. And it is quietly destroying quality in
organizations that believe they are improving it.
The Psychology of the
Bandwagon
The Bandwagon Effect is one of the most well-documented cognitive
biases in social psychology. It takes its name from the
nineteenth-century American political practice of riding on a literal
bandwagon during campaign parades — the idea being that once a candidate
attracted enough supporters, others would climb aboard simply because
the wagon was already full.
The research is unambiguous. Solomon Asch’s conformity experiments in
the 1950s demonstrated that people will give obviously incorrect answers
to simple questions if those around them are giving the same wrong
answer. Later studies showed that the effect intensifies when the domain
is unfamiliar: when people feel uncertain, they look to others for cues
about what to do. And in a world of consultants, conferences, LinkedIn
posts, and vendor marketing, the cues are everywhere.
In quality management, the Bandwagon Effect creates a particular kind
of organizational dysfunction. Leaders do not adopt new tools and
methodologies because they have carefully analyzed their problems and
identified the right solutions. They adopt them because their
competitors adopted them. Because their customers asked about them.
Because a consultant recommended them. Because an article in a trade
journal said they were the future. Because everyone at the last industry
conference was talking about them.
The motivation is not improvement. The motivation is belonging. And
the result is not quality. The result is chaos.
The Anatomy of a Quality
Bandwagon
Quality bandwagons follow a remarkably predictable lifecycle, and
understanding that lifecycle is the first step to resisting it.
Phase One: The Buzz. A new methodology, tool, or
technology emerges. It is usually legitimate in its original context —
Six Sigma was genuinely transformative at Motorola, Lean was genuinely
transformative at Toyota, Agile was genuinely transformative in software
development. But the methodology begins to detach from its context.
Consultants package it. Certification bodies standardize it. Vendor
ecosystems form around it. The buzz builds.
Phase Two: The Leap. A respected company — usually
large, usually successful — publicly adopts the methodology. They
present their results at conferences. They publish case studies. The
results are often real, but they are also specific to that company’s
context, culture, and problems. This detail is lost in the retelling.
The market hears only “Company X did this and improved by Y
percent.”
Phase Three: The Stampede. Organizations across
industries, regardless of their actual problems, begin adopting the
methodology. The motivation shifts from problem-solving to
status-seeking. Companies adopt the methodology because not adopting it
would signal that they are behind. The language of the methodology
enters the corporate vocabulary whether it fits or not. People who do
not understand the methodology start using its terminology in
meetings.
Phase Four: The Plateau. The initial enthusiasm
wanes. The results do not match the promises, because the methodology
was never tailored to the actual problems. Implementation becomes
superficial — the rituals are performed without the underlying
discipline. “We do Lean” means there are 5S markings on the floor, not
that anyone is systematically eliminating waste. “We are Agile” means
there are daily standups, not that teams are genuinely adapting to
changing information.
Phase Five: The Abandonment or the Zombies. One of
two things happens. Either the organization quietly abandons the
methodology and moves on to the next bandwagon, leaving behind a
graveyard of half-implemented tools. Or the methodology becomes a zombie
— it shambles on in a degraded, hollow form, consuming resources without
delivering value, enforced by people who no longer remember why it was
adopted in the first place.
In my 25 years of consulting across manufacturing plants on three
continents, I have seen this cycle repeat dozens of times. Total Quality
Management. Business Process Reengineering. Six Sigma. Lean. Theory of
Constraints. Balanced Scorecard. Agile. Digital Twins. Industry 4.0.
Predictive Maintenance. AI-Powered Quality. Each one, in its place,
valuable. Each one, when pursued as a bandwagon, destructive.
Why the Bandwagon Destroys
Quality
The damage caused by quality bandwagons is not merely wasted money or
wasted time, though both are substantial. The real damage is deeper and
more insidious.
Loss of Depth. When an organization is constantly
chasing the next new thing, it never develops depth in anything. Mastery
requires sustained focus, repetition, and incremental improvement over
years. A plant that implements Six Sigma for two years and then pivots
to Lean for two years and then pivots to Agile for two years has six
years of shallow experience and zero years of mastery. The organizations
with the best quality — the Toyotas, the Millikens, the Danahers — are
not the ones with the most tools. They are the ones that have gone
deepest on the fewest tools.
Tool Proliferation. Bandwagon-hopping organizations
accumulate tools the way a garage accumulates gadgets. Every new
methodology comes with its own forms, its own metrics, its own meetings,
its own terminology. Eventually, the organization is spending more time
managing its quality tools than actually managing quality. I walked
through a plant in Monterrey that had seven different problem-solving
frameworks in active use — 8D, A3, DMAIC, PDCA, 5 Why, Fishbone, and
their own proprietary hybrid. When I asked a line supervisor which one
she used for a specific defect, she looked at me and said, “Whichever
one the auditor asks for.” She was not being glib. She was being
accurate.
Cynicism. Perhaps the most corrosive effect. When
workers and middle managers have lived through three or four bandwagon
cycles, they develop a deep and justified cynicism about management’s
commitment to any improvement initiative. They learn to perform the
rituals without engaging with the substance. They nod in the training
sessions, fill out the forms, attend the ceremonies, and then go back to
doing things the way they always have. This cynicism is not laziness. It
is a rational response to a pattern of shallow, unserious improvement
efforts. And once it takes root, it kills any genuine improvement effort
— even the ones that are well-chosen and well-executed.
Context Collapse. Every quality methodology was
developed in a specific context to solve a specific class of problems.
Six Sigma works best in high-volume, repetitive processes with
measurable outputs. Lean works best in environments where flow and waste
elimination are the primary levers. Agile works best in complex,
uncertain environments where requirements evolve. When you apply a
methodology without understanding its context, you are prescribing
medicine without understanding the disease. The patient may get better
by accident. More likely, they will get worse.
The Bavarian Supplier
Revisited
Let us return to our Bavarian automotive supplier, because their
story illustrates every one of these failure modes.
Their core problem was simple: they had a soldering process on their
PCB assembly line that was producing intermittent cold joints. The
defect was intermittent, temperature-sensitive, and difficult to detect
in final inspection. It was causing field failures at a rate of
approximately 0.3 percent — devastating in the automotive industry.
The solution was equally simple, though not easy: they needed to
tighten their soldering process parameters, implement real-time thermal
profiling on the soldering station, and add an inline X-ray inspection
step. This was a focused, specific, well-understood engineering problem
that required focused, specific, well-understood engineering work.
Instead, they spent 18 months and €2.3 million implementing seven
different improvement methodologies. The soldering problem received
attention in fits and starts, sandwiched between Kaizen events on
unrelated processes, Agile retrospectives about project management, and
digital twin simulations of a production line that had not yet been
instrumented with the sensors the simulations required.
The defect was eventually solved — not by any of the seven
methodologies, but by a process engineer who stayed late one evening and
ran a designed experiment on the soldering parameters. She found the
optimal window in three days. She used basic statistical process
control, a tool the plant had been using for a decade. She was not part
of any formal improvement initiative. She was simply a competent
engineer solving a specific problem with the tools she already had.
That engineer was later laid off in a cost-reduction round. The
consultant who had recommended the digital twin platform was
retained.
How to Resist the Bandwagon
Resisting the bandwagon does not mean rejecting every new idea. It
means developing the discipline to evaluate new ideas against your
specific problems, your specific context, and your specific capacity to
implement them deeply. Here is a framework I have used with
organizations for two decades.
Start with the Problem, Not the Solution. Every
improvement initiative should begin with a clear, specific, measurable
problem statement. Not “we need to become more Lean” or “we need to
embrace digital transformation.” Those are not problems. Those are
aspirations posing as strategy. A problem is: “Our cold solder defect
rate on line three is 0.3 percent and our customer is requiring us to
reduce it to below 0.05 percent within six months.” From that problem,
the right tools become obvious.
Understand Before You Adopt. Before implementing any
methodology, invest the time to understand its principles, not just its
practices. The practices are the visible part — the standups, the
control charts, the value stream maps. The principles are the invisible
part — the underlying logic that makes the practices work. Organizations
that adopt practices without understanding principles are like people
who wear surgical masks because they see doctors wearing them, without
understanding that the mask goes over the nose.
Go Deep Before Going Wide. If you have a tool that
is working — even partially — go deeper with it before adding new ones.
A plant that truly masters SPC will outperform a plant that has
superficially implemented SPC, FMEA, control plans, 8D, and A3. Depth
beats breadth every time. The organizations I have seen achieve
world-class quality are not the ones with the most certifications on the
lobby wall. They are the ones that have taken a small number of tools
and applied them with extraordinary rigor and consistency over many
years.
Beware the Vendor-Consultant Complex. The quality
improvement industry is an industry. Consultants, certification bodies,
software vendors, and conference organizers all have a financial
interest in convincing you that you need the new thing. Some of them are
excellent and genuinely helpful. Many are not. Before hiring a
consultant or purchasing a platform, ask: “What specific problem will
this solve, and how will we measure whether it solved it?” If the answer
involves the word “journey” or “transformation” without specific
measurable outcomes, walk away.
Protect Your Culture. The most valuable asset in any
quality organization is not its tools or its certifications. It is the
culture of disciplined, data-driven problem-solving that develops over
years of consistent practice. A single bandwagon cycle can damage that
culture. Two or three can destroy it. Protect it the way you would
protect any critical asset — by being selective about what you
introduce, rigorous about how you implement, and honest about whether it
is working.
The Uncomfortable Truth
Here is the uncomfortable truth that the quality improvement industry
does not like to talk about. Most organizations do not need a new
methodology. They need to do the things they already know they should be
doing, but more consistently, more rigorously, and with greater
discipline.
I have walked through hundreds of plants. In the vast majority, the
biggest quality opportunities are not found in implementing the latest
tool. They are found in the gap between what the organization says it
does and what it actually does. The control chart that nobody looks at.
The FMEA that was completed for the customer and then filed away. The
work instruction that was updated six months ago but the operator on the
floor has the old version taped to her station. The corrective action
that was closed in the system but never verified on the production
floor.
These gaps are not exciting. They do not make for compelling
conference presentations. They will not generate a glossy case study.
But closing them — systematically, relentlessly, day after day — is what
separates the organizations with genuine quality from the organizations
that are merely performing quality theater.
The bandwagon is seductive because it offers the promise of
transformation without the grind of mastery. It offers the appearance of
improvement without the discipline of actual improvement. It offers the
thrill of the new without the commitment to the real.
The best quality organizations I have worked with share one trait:
they are deeply suspicious of anything that promises quick, dramatic
results. They have learned, through years of hard experience, that
quality is not a revolution. It is a practice. It is built one process
at a time, one parameter at a time, one defect at a time, by people who
show up every day and do the unglamorous work of making things slightly
better than they were yesterday.
That Bavarian supplier? They eventually found their way back. A new
plant manager came in, canceled seven of the nine ongoing improvement
initiatives, and told the team to focus on three things: process control
on the soldering line, incoming material inspection, and operator
training. Within a year, their defect rate dropped below 0.05 percent.
Their on-time delivery recovered to 95 percent. Their customers removed
the quality warnings.
No banners. No conferences. No digital twins. Just a clear problem, a
focused approach, and the discipline to see it through.
Peter Stasko is a Quality Architect with over 25
years of experience helping manufacturing organizations build
sustainable quality systems. He has worked with plants across Europe,
North America, and Asia, specializing in the intersection of human
psychology and operational excellence. He writes about the cognitive
biases and organizational dynamics that undermine quality — and the
practical strategies that overcome them.
