Walk into any manufacturing plant running a mature ISO 9001 system and you will find two organizations inside the same walls. Line A, the flagship the customer tours, hums along with calibrated gages, current PFMEA reviews, and SPC charts that operators actually read. Line C, running the legacy product at the back of the plant, has a gage R&R study eighteen months overdue and a corrective-action log that functions as a permanent fire drill.
Both lines sit under the same certificate. Both are subject to the same management reviews. Yet the performance gap between them is not static — it compounds annually. The sociologist Robert Merton named this dynamic the Matthew Effect in 1968, observing that accumulated advantage accelerates while accumulated disadvantage accelerates in the opposite direction. He was studying scientific careers. He was also describing your factory.
I have audited plants where the divergence between a flagship line and a struggling line exceeds 300 percent on every core metric — ppm, OEE, on-time delivery, 8D closure time. Nobody designed this gap. The system produced it through thousands of small resource-allocation decisions, each rational in isolation, that collectively reinforced the strong and starved the weak.
The Quality Accumulator
Well-maintained equipment produces fewer defects, which reduces rework, which frees time for preventive maintenance and process improvement, which further reduces defects. Well-trained operators detect drift earlier, which prevents minor deviations from escalating, which preserves engineering capacity for prevention rather than containment. Each advantage creates the conditions for the next.
The struggling line follows the inverse path. Deferred PM leads to unplanned downtime, which consumes the training budget in lost throughput, which leaves operators less equipped to recognise process drift, which generates more customer complaints, which triggers more fire-fighting and leaves even less time for the systematic improvement that would have prevented the breakdowns.
These cycles are self-reinforcing and they accelerate. Line A's Cpk of 1.67 is not a static achievement — it is the output of a system that generates daily micro-improvements. Line C's Cpk of 0.9 is not a static problem — it is the output of a system that generates daily micro-degradations. The longer the cycles run, the harder they are to reverse, because the capability gap between the two teams widens alongside the metric gap.
Three Engines of Accumulation
The first engine is attention allocation. Management attention follows a Matthew distribution: processes that generate positive data attract recognition, which reinforces the behaviours producing the good data. Struggling processes initially attract attention through corrective-action mandates, but as improvement proves difficult, that attention converts to frustration, then avoidance, then neglect. The struggling line does not get more help over time. It gets less.
I watched this at a Tier 1 automotive supplier with two plants producing the same product family. Plant 1 maintained a stable 12 ppm. Plant 2, acquired two years prior, ran at 180 ppm. Corporate quality poured resources into Plant 2 for twelve months — VDA 6.3 process audits, equipment upgrades, structured training. Ppm dropped to 120. Then the fiscal year turned, budgets tightened, and attention shifted to a new product launch at Plant 1. Within six months, Plant 2 was back at 175 ppm. The surface metrics had moved; the underlying capability had not been built.
The second engine is knowledge accumulation. Every time a team closes an 8D with a verified root cause, it builds diagnostic capital — heuristics, mental models of cause and effect, the ability to distinguish signal from noise. Teams that solve problems frequently get better at solving problems. Teams trapped in containment mode accumulate diagnostic debt. When a significant failure arrives, they start from zero.
The third engine is trust currency. A team that resolves a customer complaint with thorough root cause analysis and effective corrective action earns trust. That trust buys information sharing, advance warning of changes, and latitude during future deviations — all of which make the next problem easier to prevent. A team that delivers late responses and superficial 8Ds faces heightened scrutiny, more demanding reporting requirements, and less patience. The burden of compliance falls heaviest on the organisations least equipped to bear it.
The Audit Paradox
Internal audits are designed to be the great equaliser — the mechanism that identifies weakness and drives improvement regardless of a process's organisational standing. In practice, audits frequently reinforce the inequality they are meant to correct. The auditor visits the high-performing line: documentation is current, records are complete, the team explains its process with confidence. The audit closes quickly with a minor observation or two.
Then the auditor visits the struggling line. Documentation gaps everywhere. Missing calibration records. The team is defensive because the previous audit's corrective actions remain open. The findings pile up. The audit takes longer than planned, the tone turns adversarial, and the closing meeting produces a list of nonconformities that lands on a team already drowning in containment work.
The high-performing line treats the audit as a minor inconvenience and returns to improvement. The struggling line treats the audit as additional workload — more findings to close, more evidence to compile, more reports to submit. Resources that might have gone toward building process capability are diverted toward closing audit findings. The audit did not help the struggling line improve. It gave it more work.
The audit's divergent impact
High-performing line
- Records current, evidence ready, team confident
- One or two minor observations
- Returns to improvement work next day
- Audit confirms existing discipline
Struggling line
- Documentation gaps, open CARs from prior cycle
- Multiple major nonconformities
- Diverts resources from prevention to evidence compilation
- Audit adds workload, not capability
Breaking the Accumulation Cycle
Interrupting the Matthew Effect requires deliberate, sustained effort in the opposite direction. Most organisations allocate resources based on expected return, which naturally favours the processes that have demonstrated the ability to turn investment into improvement. Breaking the cycle means allocating resources based on need, not return — accepting lower short-term yield for higher long-term risk reduction.
The first step is to map the divergence. Pull your quality data — ppm, customer complaints, audit findings, 8D closure time, training hours per operator — and plot it by line, by process, by plant. Do not look at averages alone. Track the gap between best and worst. If the gap is widening, the Matthew Effect is active and the cost of reversal grows every month you wait.
The second step is to diagnose which engine drives the divergence. Attention starvation requires committed, recurring management presence — not a single plant visit. Knowledge deficit requires structured coaching through real problem-solving, not classroom training in isolation. Trust erosion requires behavioural change at the leadership level: consistent follow-through, honest communication about what went wrong, and visible investment in the team's success.
The third step is the hardest: protect improvement time. Struggling processes never get dedicated improvement time because every minute is consumed by containment and rework. Asking the team to make time for improvement is asking a drowning team to schedule swimming lessons. You create protected time by temporarily supplementing capacity, reducing the production schedule, or pausing non-essential output. This requires leadership commitment and resources — which returns you to the attention-allocation problem.
Reversing the Matthew Effect in a struggling process
- 01Map the divergencePlot ppm, 8D closure time, complaint rate and training hours by line; track the gap trend, not just the average.
- 02Diagnose the engineIdentify whether attention, knowledge or trust is the binding constraint driving the divergence.
- 03Protect improvement timeSupplement capacity or reduce output targets so the team has dedicated hours for prevention, not containment.
- 04Build capabilityCoach structured problem-solving on real failures — not classroom theory, not checklist compliance.
- 05Measure the gapTrack the best-to-worst delta monthly. A shrinking gap confirms the intervention; a stable gap means a new equilibrium.
Capability Over Compliance
Audit findings and corrective actions address symptoms. Capability building addresses causes. The struggling process does not need more findings — it needs statistical thinking, root cause discipline, and process management skill. This takes longer, costs more, and produces fewer visible deliverables in the first quarter than a stack of closed nonconformities. But it generates durable improvement rather than temporary compliance.
A quality system that watches the process gap widen and calls it normal variation is a ranking system with a certification logo.
Most organisations track average quality performance across all lines. A few track the worst performer. Almost none track the delta between best and worst as a standing metric. That delta is your Matthew Effect indicator. If it is growing, the effect is active. If it is shrinking, your intervention is working. If it is stable, you have reached an equilibrium — and you should ask hard questions about whether that equilibrium is acceptable.
At SNOP, I built a greenfield QA department for a 900-person plant where the starting condition was essentially zero diagnostic capital. The investment in structured problem-solving training — not ISO documentation, not checklist audits — produced the durable capability improvement. The certification followed the capability. It did not create it.
The Leader's Decision
The Matthew Effect cannot be interrupted by policy revision or a new procedure. It can only be interrupted by leaders willing to invest disproportionately in the processes and people falling behind — not because the short-term return justifies it, but because the risk of inaction compounds at the same rate as every other accumulation dynamic in the system.
This requires spending time and resources on work that will not look impressive on next quarter's management review. The struggling line will not reach world-class Cpk in one quarter. Improvement will be incremental, uneven, and sometimes invisible to anyone not standing on the shop floor. The leader who champions this work will spend more time at the back of the plant than in the boardroom, and will have more explanations to provide than success stories to tell.
But the result is something the Matthew Effect would otherwise destroy: an organisation where quality capability is distributed, not concentrated at one flagship line. Where the gap between best and worst is narrow enough that a failure at any single site is managed with competence rather than panic. That distribution does not happen by accident. It happens because a leader decided the struggling process deserved the same investment as the high performer — and treated the widening gap not as normal variation but as a failure of management.
The real test of a quality system is not how well it supports the strong. It is how effectively it lifts the weak. If your best processes are excellent because they have the best people, the newest equipment, and the most management attention, then your QMS is not producing excellence. It is certifying what was already there.