Quality
and the Matthew Effect: When Your Organization’s Best Processes Keep
Getting Better While the Worst Ones Keep Getting Worse — and the
Accumulated Advantage Nobody Designed Becomes the Gap Nobody Can
Close

There is a passage in the Gospel of Matthew that has haunted
organizations for two thousand years without most of them knowing it:
“For unto every one that hath shall be given, and he shall have
abundance: but from him that hath not shall be taken away even that
which he hath.”

The sociologist Robert Merton gave this phenomenon a name in 1968:
the Matthew Effect. He was studying scientific careers when he noticed
something uncomfortable — famous scientists got more credit than unknown
ones for identical work, and that credit then attracted more funding,
more collaborators, more attention, which produced more results, which
attracted even more credit. The rich got richer. The poor got
invisible.

Merton thought he was describing academia. He was actually describing
your factory.

The Quality Accumulator

Walk through any manufacturing plant that has been running a quality
management system for more than five years and you will see two
completely different organizations living inside the same walls.

On Line A — the flagship, the one the customer tours, the one that
gets the investment and the attention — things are pristine. Operators
know their processes inside out. The SPC charts hum along within control
limits. When a deviation occurs, the team has a response plan inside
fifteen minutes. The line supervisor has been to three training courses
this year. The maintenance schedule is followed religiously. The
measurement equipment is calibrated and the gage R&R is under 10%.
Customer complaints from this line are rare, and when they happen, the
8D report is closed in under two weeks.

On Line C — the one at the back, the one running the older product,
the one managed by the supervisor who has been asking for training for
eighteen months — things are different. The SPC charts exist but nobody
looks at them because the last time someone flagged an out-of-control
point, the response was “we don’t have time for that right now.” The
maintenance is reactive. The measurement equipment was calibrated seven
months ago and the gage R&R study is “on the list.” Customer
complaints arrive monthly. Each one triggers a fire drill. The 8D
reports take six weeks because the root cause investigation keeps
getting interrupted by the next fire.

Here is what makes the Matthew Effect so insidious in quality
management: both lines are managed by the same company. Both lines are
covered by the same QMS. Both lines are subject to the same ISO 9001
certificate. And yet, the gap between them is not static. It is
widening. Every single day, it gets a little wider.

Line A’s accumulated advantages — better trained people, better
maintained equipment, stronger process knowledge, faster problem-solving
capability — compound. Each advantage creates the conditions for the
next advantage. The well-maintained equipment produces fewer defects,
which means less rework, which means more time for process improvement,
which means even fewer defects. The well-trained operators catch
deviations earlier, which prevents minor issues from becoming major
ones, which preserves the time and resources that would have been spent
on containment, which can now be invested in prevention.

Line C’s accumulated disadvantages compound in the opposite
direction. The deferred maintenance leads to more breakdowns, which
consumes the time that would have been used for training, which leaves
operators less equipped to detect the early signs of process drift,
which leads to more customer complaints, which triggers more
fire-fighting, which leaves even less time for the systematic
improvement that would have prevented the breakdowns in the first
place.

Nobody designed this divergence. Nobody decided that Line A should
succeed and Line C should fail. The system produced it organically,
through thousands of small decisions that each seemed rational in the
moment but collectively created a self-reinforcing cycle of advantage
and disadvantage.

The Three Engines of
Accumulation

The Matthew Effect operates through three distinct engines in quality
management. Understanding them is the first step toward interrupting the
cycle.

Engine One: Attention Allocation. Management
attention is the scarcest resource in any organization, and it follows a
Matthew distribution. The processes that perform well generate positive
data, which attracts positive attention, which leads to recognition,
which reinforces the behaviors that produced the good data. Meanwhile,
the processes that struggle generate negative data, which initially
attracts attention in the form of corrective actions and improvement
mandates, but over time — as improvement proves difficult and the
problems prove stubborn — that attention converts to frustration, then
avoidance, then neglect. The struggling process doesn’t get more help.
It gets less. Because helping it is hard, unrewarding, and politically
risky.

I watched this play out at a Tier 1 automotive supplier in central
Europe. They had two plants producing the same product family. Plant 1
had a mature quality system, a stable workforce, and a ppm rate that
consistently hovered around 12. Plant 2 had been acquired two years
earlier, had a younger workforce, higher turnover, and a ppm rate of
180. For the first year after acquisition, corporate quality poured
resources into Plant 2 — training programs, process audits, equipment
upgrades. The ppm dropped to 120. Progress. But then the next fiscal
year arrived, the training budget got cut, and corporate attention
shifted to a new product launch at Plant 1. Within six months, Plant 2’s
ppm was back to 175. The improvement hadn’t compounded because the
underlying capability hadn’t been built — only the surface metrics had
moved. And now, with attention withdrawn, even those surface gains
evaporated.

Engine Two: Knowledge Accumulation. Every time a
team solves a quality problem, it builds knowledge. That knowledge lives
in documentation, yes, but more importantly, it lives in the collective
problem-solving muscle of the team. Teams that solve problems frequently
get better at solving problems. They develop heuristics. They build
mental models of cause and effect. They learn to distinguish signal from
noise faster. They accumulate what you might call diagnostic
capital.

Teams that rarely solve problems — because their process is poorly
controlled and they’re always in containment mode, or because problems
get escalated to someone else, or because the culture punishes the
messenger — accumulate diagnostic debt. They don’t develop the
problem-solving muscle. When a significant failure eventually arrives,
they’re starting from zero, which means the investigation takes longer,
costs more, and produces weaker corrective actions.

This is why two plants can have the same failure and produce
dramatically different outcomes. Plant 1’s team has seen similar
failures before. They have a mental library of root causes, a tested set
of verification techniques, and a shared language for describing what
they observe. Plant 2’s team is encountering this failure for the first
time. They’re assembling the investigation from scratch. The gap in
time-to-resolution isn’t a matter of effort. It’s a matter of
accumulated learning.

Engine Three: Trust Currency. Quality management
runs on trust — trust between operators and supervisors, between
production and quality, between supplier and customer. High-trust
relationships enable fast information flow, honest defect reporting, and
collaborative problem-solving. Low-trust relationships produce
information hoarding, blame shifting, and defensive documentation.

Trust, like everything else in the Matthew Effect, compounds. When a
team successfully resolves a customer complaint with a thorough root
cause analysis and effective corrective action, the customer’s trust
increases. Increased trust means the customer is more willing to share
information, provide advance warning of changes, and grant the benefit
of the doubt during future deviations. That information and latitude
makes it easier to prevent and resolve the next issue, which further
builds trust.

When a team handles a complaint poorly — late response, superficial
root cause, ineffective corrective action — trust erodes. The customer
becomes more demanding, more intrusive, less willing to share
information, less patient with deviations. That heightened scrutiny
creates more pressure, which often leads to worse performance, which
further erodes trust. The customer doesn’t just expect more. They demand
more, and the organization — already struggling — must now meet higher
expectations with fewer resources and less goodwill.

The Audit Paradox

The Matthew Effect creates a particularly cruel paradox in the audit
world. Audits are supposed to be the great equalizer — the mechanism
that identifies weaknesses and drives improvement regardless of a
process’s position in the organizational hierarchy. In practice, audits
often reinforce the very inequality they are meant to correct.

Consider what happens during a typical internal audit cycle. The
auditor, usually pressed for time and armed with a standard checklist,
visits the high-performing process first. Everything is in order.
Documentation is current. Records are complete. The team can explain
their process with confidence. The audit goes smoothly, takes less time
than allocated, and produces a clean report with maybe a minor finding
or two. The auditor leaves with a positive impression.

Then the auditor visits the struggling process. Documentation gaps.
Missing records. The team is defensive, partly because they know things
aren’t where they should be and partly because the last auditor’s
findings still haven’t been fully addressed. The audit takes longer than
planned. The findings are more numerous and more serious. The tone is
more adversarial. The auditor leaves with a negative impression that
colors how they describe the process in the closing meeting.

So far, this might seem like the audit is working as designed —
identifying real differences. But here’s the Matthew Effect at work: the
high-performing process, with its clean audit, is now free to continue
improving. The audit was a minor inconvenience that confirmed what
everyone already knew. The struggling process, however, now has a new
set of corrective actions to manage on top of the ones it hasn’t
completed yet. Resources that might have gone toward building capability
are instead channeled toward closing audit findings — addressing
symptoms rather than causes. The audit didn’t help the struggling
process improve. It gave it more work.

External audits amplify this dynamic. Customers who audit their
suppliers follow the same pattern. The supplier with a strong quality
record gets a lighter audit — maybe a desktop review or a shorter
on-site visit. The supplier with quality issues gets a deep dive, more
findings, more requirements, more reporting. The burden of compliance
falls heaviest on the organizations least equipped to bear it.

Breaking the Cycle

Interrupting the Matthew Effect requires deliberate, sustained effort
in the opposite direction. It requires what the economist Mariana
Mazzucato calls “mission-oriented” investment — not spreading resources
evenly across all processes, but deliberately concentrating resources on
the processes that are falling behind.

This is counterintuitive. Most organizations allocate resources based
on expected return, which naturally favors the high-performing processes
that have demonstrated the ability to turn investment into improvement.
Breaking the Matthew Effect means allocating resources based on need,
not return. It means accepting that the investment in the struggling
process will produce a lower short-term return but a higher long-term
payoff in reduced risk and organizational resilience.

Here is a practical framework for doing this:

First, map the divergence. Before you can interrupt
the cycle, you need to see it. Pull your quality data — ppm rates,
customer complaints, audit findings, corrective action closure times,
training hours — and plot it by process, by line, by plant. Look for the
gaps. Not just the absolute numbers, but the trend. Is the gap widening?
Stable? Narrowing? If the gap is widening, the Matthew Effect is active,
and the longer you wait, the harder it will be to reverse.

Second, diagnose the accumulation mechanism. Is the
struggling process suffering from attention starvation, knowledge
deficit, trust erosion, or some combination? Each mechanism requires a
different intervention. Attention starvation requires committed,
sustained management involvement — not a one-time visit, but a recurring
presence. Knowledge deficit requires structured learning — not just
training courses, but deliberate practice through coached
problem-solving. Trust erosion requires behavioral change at the
leadership level — consistent follow-through, honest communication, and
a demonstrated willingness to invest in the process’s success.

Third, protect the improvement time. The single most
common reason the Matthew Effect persists is that struggling processes
never get dedicated improvement time. Every minute is consumed by
containment, rework, and fire-fighting. The solution isn’t to ask the
team to “make time for improvement” — that’s like asking someone
drowning to “make time for swimming lessons.” The solution is to create
protected time by temporarily supplementing capacity, reducing the
workload, or pausing non-essential activities. This requires management
commitment and resources, which brings us back to the attention
allocation problem.

Fourth, build capability, not just compliance. Audit
findings and corrective actions address symptoms. Capability building
addresses causes. The struggling process doesn’t need more findings. It
needs more skill — skill in statistical thinking, skill in root cause
analysis, skill in process management. This takes longer and costs more
than closing a finding, but it produces durable improvement rather than
temporary compliance.

Fifth, measure the gap, not just the average. Most
organizations track average quality performance. A few track worst
performance. Almost none track the gap between best and worst. That gap
is your Matthew Effect meter. If it’s growing, the effect is active. If
it’s shrinking, your interventions are working. If it’s stable, you’ve
reached a new equilibrium — and you should ask whether that equilibrium
is acceptable.

The Leader’s Role

The Matthew Effect cannot be interrupted by policy. It can only be
interrupted by leadership behavior. Specifically, by leaders who are
willing to invest disproportionately in the processes and people that
are falling behind — not because the return is highest, but because the
risk of inaction is unacceptable.

This requires a particular kind of courage: the willingness to spend
time and resources on something that won’t look impressive on next
quarter’s metrics. The struggling process won’t become world-class
overnight. The improvement will be slow, uneven, and sometimes
invisible. The leader who champions this work will spend more time in
the back of the factory than in the boardroom. They will have fewer
success stories to tell and more explanations to provide.

But they will also be building something that the Matthew Effect
would otherwise destroy: an organization where quality capability is
distributed, not concentrated. Where the gap between best and worst is
small enough that a single failure at one site doesn’t become a
catastrophic surprise. Where every process, every line, every plant has
the diagnostic capital to respond effectively when things go wrong.

This is resilience. Not the kind you measure in dashboards, but the
kind you discover when the unexpected happens and every part of your
organization can respond with competence rather than panic.

The Uncomfortable Question

The Matthew Effect asks every quality leader an uncomfortable
question: Are your best processes getting better because of your
quality system, or because of accumulated advantages your quality system
didn’t create?

If your best processes are excellent because they have the best
people, the newest equipment, the most management attention, and the
strongest customer relationships — then your quality system isn’t
producing excellence. It’s certifying it. The excellence was already
there. Your QMS just put a stamp on it.

The real test of a quality system is not how well it supports the
strong. It’s how effectively it lifts the weak. A quality system that
allows the Matthew Effect to operate unchecked — that watches the gap
between processes widen year after year and calls it “normal variation”
— is not a quality system. It’s a ranking system with a certification
logo.

The organizations that understand this — that recognize the Matthew
Effect as the silent architect of their quality landscape and actively
work to counteract it — are the ones that build world-class quality from
the bottom up rather than the top down. They don’t just have excellent
processes. They have excellent organizations, because excellence is not
concentrated in a few places. It is distributed everywhere.

That distribution doesn’t happen by accident. It happens because
someone decided that the struggling process deserved the same commitment
as the flagship. That the struggling team deserved the same investment
as the high performers. That the widening gap was not a fact of life but
a failure of leadership.

That decision — that commitment to lifting the bottom rather than
polishing the top — is where real quality leadership begins.

Peter Stasko is a Quality Architect with 25+ years of experience
transforming organizations across automotive, aerospace, and
pharmaceutical industries. He specializes in making the invisible
patterns that drive quality failure visible — and actionable.