Quality
and the Shirky Principle: When Your Quality Department Unconsciously
Preserves the Problems It Was Created to Solve
The Institution That
Needs the Disease
In 2009, the writer and technology theorist Clay Shirky formulated a
principle so uncomfortable that most organizations refuse to acknowledge
it exists: “Institutions will try to preserve the problem to
which they are the solution.” It was a observation about how
bureaucracies behave, but it might be the most important thing anyone
has ever said about quality departments.
Because here’s the thing — your quality department was created to
solve a problem. And if you’re not paying attention, it will quietly,
inadvertently, and with the best intentions in the world, make sure that
problem never fully goes away.
This isn’t a conspiracy. It’s not malicious. Nobody sits in a
conference room and says, “Let’s keep defects alive so we keep our
jobs.” That’s cartoon villain thinking, and real organizations don’t
work like that. What happens is far more subtle, far more common, and
far more dangerous. It happens through incentive structures, through
identity, through the slow gravitational pull of institutional
self-preservation.
And if you’ve ever wondered why your quality metrics improve for
three quarters and then plateau just before they would make the
department redundant, you’ve seen the Shirky Principle in action.
How It
Starts: The Noble Birth of a Quality Department
Every quality department begins with a crisis. A customer returns a
shipment. A defect escapes to the field. An audit finds a systemic
failure. Someone in leadership says, “We need to get serious about
quality,” and a department is born.
In the beginning, it’s pure. The quality engineers are firefighters,
heroes. They find the defects, they trace the root causes, they put
countermeasures in place. The metrics improve. The customer stops
complaining. Leadership pats itself on the back for making the
investment.
But then something shifts.
The acute crisis becomes a chronic condition. The quality department
doesn’t dissolve — it institutionalizes. It builds systems, procedures,
checklists, and approval gates. It hires more people. It creates
dashboards and reports. It establishes weekly meetings, monthly reviews,
and annual audits. All of this is necessary. All of this is good. And
all of this creates something that didn’t exist before: a
department whose identity, budget, and organizational power depend on
the continued existence of quality problems.
Not big problems. Not crises. Just enough problems to justify the
next budget cycle, the next headcount request, the next software
upgrade.
The Five Mechanisms
of Problem Preservation
The Shirky Principle doesn’t operate through conscious choice. It
operates through structural dynamics that reward the department for
managing problems rather than eliminating them. Here are the five
mechanisms I’ve watched play out across dozens of organizations:
1. The Metric That Becomes
the Mission
A quality department creates a dashboard tracking defect rates. The
dashboard is useful — it shows where problems are, it measures
improvement, it gives leadership visibility. But over time, the
dashboard becomes the point. The department starts optimizing for the
metrics themselves rather than the outcomes the metrics were supposed to
represent.
Defect rates drop, so the department redefines what counts as a
defect. Or it shifts focus to a different metric that still has room for
improvement. Or it adds complexity to the measurement system so that the
numbers tell a story that still requires intervention. The metrics
become self-justifying.
I visited a medical device manufacturer where the quality department
tracked 347 distinct metrics. Three hundred and forty-seven. When I
asked the VP of Quality which five actually mattered, she couldn’t
answer. But she could tell me exactly what would happen to her budget if
any of those 347 metrics showed sustained improvement — the board would
ask why they needed a 42-person quality department if everything was
running so well.
2. The Approval Gate
That Creates Bottlenecks
Quality departments often establish themselves as gatekeepers.
Engineering changes must be approved by Quality. New suppliers must be
qualified by Quality. Process modifications must be validated by
Quality. This is standard practice and, in regulated industries, it’s
required.
But the gatekeeping role creates a subtle incentive: the more
gates, the more necessary the gatekeeper. The quality
department unconsciously expands the scope of what requires its
approval. What starts as a review of critical process changes becomes a
review of all process changes. What starts as an assessment of new
suppliers becomes an assessment of any supplier modification. Each
expansion is justified. Each expansion also increases the department’s
centrality.
I worked with an automotive supplier where the quality department
held 23 distinct approval gates between a design concept and production
launch. Twenty-three. The average time from concept to launch was 14
months. When we reduced the gates to the 8 that were genuinely
necessary, the timeline dropped to 7 months. Quality metrics didn’t get
worse — they improved, because the engineers could actually implement
improvements instead of waiting for approvals.
3. The Expertise That
Becomes Dependency
Quality departments develop deep expertise — in statistical methods,
in regulatory requirements, in problem-solving methodologies. This
expertise is valuable. But it also creates dependency. When quality
knowledge is concentrated in the quality department, the production
floor stops developing its own quality capabilities.
Operators stop thinking about quality because that’s “Quality’s job.”
Engineers stop considering process capability because Quality will check
it. Supervisors stop investigating deviations because Quality will do
the root cause analysis. The quality department becomes the only part of
the organization that thinks about quality, which means quality problems
always require quality department involvement.
This is the cruelest mechanism of the Shirky Principle: the
quality department becomes so good at solving quality problems that
nobody else learns how to prevent them. The department’s
expertise, which should be teaching the organization to fish, instead
ensures the organization never learns to fish at all.
4. The Initiative That
Replaces the Outcome
Quality departments, like all departments, need to show progress.
They launch initiatives — Lean Six Sigma programs, zero-defect
campaigns, quality culture transformations. These initiatives generate
activity: training sessions, project charters, presentation decks, belt
certifications. Activity feels like progress.
But initiatives have a lifecycle. They start strong, generate early
wins, and then encounter the hard work of sustaining improvement. At
that point, the quality department faces a choice: do the unglamorous
work of embedding changes into daily operations, or launch a new
initiative that generates fresh excitement and fresh metrics?
Most choose the new initiative. The old one gets folded into
“business as usual” — which means it slowly degrades. The quality
department’s portfolio becomes a graveyard of partially completed
initiatives, each replaced by the next shiny program before it had time
to produce lasting change.
A pharmaceutical company I consulted with had launched 11 major
quality initiatives in 6 years. None had been fully completed. All were
still “ongoing.” The quality department had grown from 18 people to 63
people during that period. Defect rates had improved by 12%. You don’t
need a calculator to see the problem.
5. The Language That Excludes
Quality professionals develop their own language — Cpk, Ppk, FMEA,
PPAP, GR&R, control plans, process flows. This language is precise
and useful within the discipline. But it also creates a barrier between
the quality department and everyone else.
When the quality manager presents findings in a language that
production supervisors don’t speak, two things happen. First, the
findings don’t get implemented — because the people who would implement
them don’t understand them. Second, the quality department’s role as
translator and interpreter becomes indispensable. The jargon that should
be a tool for precision instead becomes a wall that keeps the quality
department necessary.
The
Self-Test: Is Your Quality Department Preserving Problems?
Ask yourself these questions. Be honest:
-
Has your quality department’s headcount grown faster than
your quality metrics have improved? If you’re adding people
faster than you’re reducing defects, you may be managing problems rather
than solving them. -
Do your production operators refer to quality as “their
job, not ours”? If quality is a department instead of a shared
responsibility, the Shirky Principle is already at work. -
Has your quality department launched more than two major
initiatives in the past three years without fully completing any of
them? Initiative proliferation is a sign of problem management,
not problem elimination. -
Does your quality department hold approval gates that
have never been challenged or reviewed? Gates that were created
five years ago and never questioned are gates that serve the gatekeeper
more than the process. -
Does your quality reporting require a quality
professional to interpret? If your CEO can’t read your quality
dashboard without a translation session, your reporting is serving the
department, not the organization. -
Has your quality department ever proposed eliminating one
of its own functions? A healthy quality department is
constantly asking, “What can we stop doing because the organization has
learned to do it without us?” A Shirky-affected department never asks
this question.
The
Antidote: Building a Quality Department That Makes Itself
Unnecessary
The most effective quality departments I’ve worked with share a
single, radical characteristic: they measure their success by
their own irrelevance. They don’t want to be the heroes who
catch defects. They want to build systems where defects don’t happen,
where operators think in statistical terms, where engineering designs
for manufacturability, where the culture of quality is so embedded that
the department becomes unnecessary.
Here’s what that looks like in practice:
Redefine the Mission
Stop measuring the quality department by how many defects it catches
or how many problems it solves. Measure it by how few problems require
its intervention. Track the percentage of quality activities performed
by non-quality personnel. Set targets for transferring expertise out of
the department. Make teaching, not doing, the primary performance
metric.
The best quality engineers I know spend 70% of their time teaching
others and 30% doing the work themselves. The worst spend 100% doing the
work and complain that nobody else understands quality.
Sunset Every Process
Every quality procedure, every approval gate, every inspection point
should have a review date and a sunset criterion. Ask: “Under what
conditions would we eliminate this step?” If the answer is “never,”
you’ve found a Shirky process. Build elimination criteria into the
process design itself.
Distribute Expertise
Every statistical method, every problem-solving tool, every quality
framework that lives only in the quality department is a vulnerability.
Train operators in SPC. Teach engineers about process capability. Coach
supervisors in root cause analysis. Make quality knowledge a
organizational capability, not a departmental asset.
Audit the Auditors
Quality departments audit everyone else. Who audits the quality
department? Regular external reviews — not of compliance, but of value —
should assess whether the quality department is eliminating problems or
managing them. Ask the production floor: “Does the quality department
help you do your job better, or does it add work without adding value?”
The answer will tell you everything.
Celebrate Irrelevance
When a quality engineer successfully transfers a process to the
production team and can stop monitoring it, celebrate that. When a
control plan becomes so routine that it no longer requires quality
oversight, celebrate that. When an operator catches a deviation before
the quality system does, celebrate that. Make the goal visible, public,
and rewarding: build quality so deeply into the organization
that the department becomes optional.
The Paradox of
the Healthy Quality Department
Here’s the paradox: the organizations with the best quality don’t
have the biggest quality departments. They have the most distributed
quality capabilities. The quality department in a world-class
organization looks nothing like the quality department in an average
one. It’s smaller. It’s more strategic. It’s more focused on building
systems than on catching defects. And it’s constantly, almost
obsessively, working to make itself unnecessary.
Clay Shirky wasn’t talking about quality when he formulated his
principle. He was talking about institutions in general. But the
principle applies to quality with a special force, because quality
departments face a uniquely dangerous temptation: the problems they
solve are the problems that justify their existence.
The question isn’t whether your quality department will feel this
temptation. It will. The question is whether you’ve built the
structures, incentives, and culture to resist it.
Because the ultimate measure of a quality department’s success isn’t
how many problems it solves. It’s how few problems require solving.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has helped dozens of companies
recognize when their quality systems were preserving the very problems
they were designed to eliminate — and rebuild them around the radical
idea that the best quality department is the one that makes itself
unnecessary.
