Quality
and the Tragedy of the Commons: When Your Organization’s Shared
Resources Become Everyone’s Problem and Nobody’s Responsibility — and
the Calibration Equipment Nobody Maintained Became the Measurements
Nobody Trusted
How the most reliable quality systems collapse not from
catastrophic failures, but from shared resources that everyone depends
on and no one protects.
The Parable of the Gage Room
There is a manufacturing plant in the American Midwest — let’s call
it Precision Components Inc. — that invested $2.3 million in a
state-of-the-art metrology lab. Coordinate measuring machines, optical
comparators, surface roughness testers, digital calipers calibrated to
NIST standards. The works. When the lab opened, the quality director
gave a speech about how this investment would transform their inspection
capability and put them on par with aerospace suppliers.
Eighteen months later, the CMM had a sticky probe that nobody had
reported. The optical comparator’s lens had a smudge that had become
permanent. Three of the twelve caliper sets were outside tolerance. The
surface roughness tester hadn’t been calibrated in seven months. And the
temperature-controlled room was being used to store leftover packaging
materials because “it was the only climate-controlled space
available.”
Nobody destroyed the lab on purpose. Nobody even neglected it on
purpose. That’s what makes the Tragedy of the Commons so insidious — and
so devastating to quality systems.
What Is the Tragedy of the
Commons?
The concept was popularized by ecologist Garrett Hardin in 1968,
though the underlying dilemma dates back to Aristotle. The classic
formulation involves a shared pasture — a “commons” — on which multiple
herders graze their cattle. Each herder benefits from adding one more
animal to the pasture, while the cost of that additional animal
(overgrazing) is shared by everyone. The rational choice for each
individual herder is to add more cattle. The inevitable result for all
herders is a destroyed pasture.
The logic is remorseless:
- Individual incentive: Add one more animal → gain
+1 - Shared cost: The pasture degrades slightly → cost
shared by all → individual cost is negligible - Individual rationality: “I should add another
animal” - Collective outcome: The pasture dies
This same logic pervades manufacturing organizations, where shared
resources — equipment, information, time, attention, training budgets,
maintenance schedules — are consumed by individual departments or teams
while the costs of degradation are distributed across the entire
organization.
The Shared Resources of
Quality
In quality management, the “commons” takes many forms, and
recognizing them is the first step toward protecting them.
Calibration and
Measurement Equipment
The most literal commons in any manufacturing plant. CMMs, gages,
fixtures, and test equipment are often shared across shifts,
departments, and product lines. Each user benefits from having access.
No single user bears the full cost of maintenance. The result? Equipment
degrades incrementally — a knock here, a missed calibration there —
until measurements become unreliable and nobody can pinpoint when the
trust was lost.
I once audited a Tier 1 automotive supplier where five production
cells shared a single set of go/no-go gages. Each cell needed them “just
for a quick check.” The gages were never returned to their protective
cases. They were dropped on concrete floors. They were used as makeshift
tools for tasks they were never designed for. When the annual
calibration audit arrived, 40% of the gages failed. The plant had been
shipping parts for months with inspection equipment that couldn’t
reliably tell good from bad.
Shared Data and Information
Systems
SPC data, corrective action databases, process knowledge, customer
feedback — these are the informational commons of quality. When everyone
can enter data but no one is responsible for its integrity, the database
degrades. Entries become incomplete. Categories become inconsistent. The
system that was supposed to be the organization’s collective memory
becomes a digital landfill.
A medical device manufacturer I consulted for had invested heavily in
an electronic quality management system. Within two years, the
corrective action module contained 3,400 entries. Roughly 60% had never
been closed. The root cause field contained variations of “operator
error” in 73% of cases. The system had become a bureaucratic exercise in
documentation rather than a tool for learning. Everyone entered data.
Nobody curated it. The commons was overgrazed.
Training and Knowledge
Experienced operators, quality engineers, and technicians represent a
knowledge commons. When one department pulls an expert to solve an
urgent problem, other departments lose access. When training budgets are
allocated to the loudest voice rather than the greatest need, the
organization’s collective capability erodes unevenly. And when
experienced workers retire without transferring their knowledge, the
commons is depleted irreversibly.
Process Standards and
Procedures
Work instructions, control plans, and standard operating procedures
are shared resources that degrade when modified without coordination.
Each engineering change, each “temporary deviation,” each unofficial
workaround chips away at the standard. Department A updates a procedure
to suit its needs without informing Department B. Shift 1 interprets a
requirement differently from Shift 2. The standard that was supposed to
ensure consistency becomes a document that means different things to
different people.
Time and Attention
Perhaps the most precious commons of all. Quality review meetings,
Gemba walks, root cause investigations — these require time. When
production pressure mounts, quality activities are the first to be
“postponed.” Each postponement is rational for the individual manager
facing a delivery deadline. Collectively, the organization loses the
attention that prevents defects from occurring.
The Mathematics of
Commons Degradation
The Tragedy of the Commons in quality systems follows a predictable
mathematical pattern. If a shared resource has a carrying capacity C,
and n users each consume slightly more than their sustainable share (C/n
+ ε), the resource degrades at a rate proportional to n × ε.
In practical terms:
- A calibration program designed for monthly intervals gets pushed to
quarterly because “we’re too busy.” Each additional month of delay adds
ε risk. - A CMM used by three shifts accumulates three times the wear, but
maintenance is budgeted for single-shift usage. - A quality database serving six departments receives six different
standards of data entry, but curation is assigned to no one.
The degradation is not linear. It accelerates. As the resource
degrades, users compensate by using it more intensively or by creating
workarounds that further degrade it. The gage that’s slightly out of
calibration produces measurements that are slightly wrong, leading to
process adjustments that are slightly inappropriate, generating slightly
more variation, which requires slightly more measurement, which puts
slightly more load on the gage.
This is how commons collapse — not in a single dramatic event, but in
a self-reinforcing spiral of incremental degradation.
Why Traditional Quality
Systems Miss It
Here’s the uncomfortable truth: most quality management systems are
designed around individual process ownership, not shared resource
stewardship. ISO 9001 asks you to identify processes and assign
responsibilities. IATF 16949 requires process owners. Six Sigma defines
project-level accountability.
But who owns the calibration lab that serves eleven production cells?
Who owns the SPC database that feeds three different management reports?
Who owns the collective knowledge of your twenty most experienced
operators?
The answer, too often, is “everyone” — which means no one.
The Audit Blind Spot
External auditors typically assess whether processes are defined,
procedures are followed, and records are maintained. They rarely assess
whether shared resources are being sustained over time. A calibration
lab can pass an audit on Tuesday even if it’s been degrading for eleven
months and will collapse on Wednesday. The audit captures a snapshot,
not the trajectory.
The Metric Blind Spot
Quality dashboards track defect rates, scrap percentages, customer
complaints, and on-time delivery. They rarely track the health of shared
resources: calibration compliance rates, database integrity scores,
knowledge transfer completion, or procedure consistency indices. The
metrics measure the outputs of quality, not the health of the
infrastructure that produces those outputs.
Solutions: Designing for
the Commons
The Tragedy of the Commons is not inevitable. Elinor Ostrom won the
Nobel Prize in Economics in 2009 for demonstrating that communities can
manage shared resources effectively — but only when they design specific
governance structures. Applied to quality systems, this means deliberate
design choices.
1. Assign Stewardship,
Not Just Ownership
Instead of assigning a process owner who “owns” the process on paper,
assign a steward who is explicitly responsible for the health of the
shared resource. The steward’s job is not to use the resource but to
maintain it. A calibration lab steward doesn’t measure parts — they
ensure the equipment can measure parts. A database steward doesn’t enter
corrective actions — they ensure the database remains searchable,
consistent, and trustworthy.
This distinction matters more than it sounds. Ownership implies
control. Stewardship implies care. A quality commons needs caretakers,
not landlords.
2. Make Degradation Visible
One of the reasons commons degrade is that the degradation is
invisible — or at least unmeasured. Make it measured. Create a “Commons
Health Dashboard” that tracks:
- Equipment commons: Calibration status, utilization
vs. capacity, maintenance compliance - Data commons: Database completeness, categorization
consistency, time-to-close for corrective actions - Knowledge commons: Cross-training coverage,
knowledge transfer completion, single-point-of-dependency count - Standards commons: Procedure revision consistency
across shifts, deviation frequency, unofficial workaround count
When degradation becomes visible, it becomes addressable. What gets
measured gets managed — but only if you’re measuring the right
things.
3. Implement
Usage Protocols With Real Consequences
Ostrom’s research identified clear boundaries and rules as essential
for commons governance. In quality systems, this means:
- Checkout systems for shared measurement equipment
(not “borrow and forget”) - Data entry standards with mandatory fields and
validation rules (not “fill in what you feel like”) - Standardized training curricula with documented
competency verification (not “watch Bob for a day”) - Change coordination requirements for shared
procedures (not “update it and hope others notice”)
The key is that these protocols must have real consequences. A
checkout system that nobody enforces is worse than no system at all,
because it creates the illusion of control.
4. Invest Redundancy in
High-Risk Commons
Not all commons are equally critical. Identify the shared resources
whose degradation would cause the most quality damage and invest in
redundancy. This might mean:
- A backup set of critical gages
- A secondary data repository with automated integrity checks
- Cross-training that ensures no single person is the sole source of
critical knowledge - Redundant process documentation stored in multiple accessible
locations
Redundancy is not waste. It is insurance against commons
collapse.
5. Create
Feedback Loops Between Users and Stewards
When a shared resource degrades, the users are often the first to
notice — but the last to report. Create formal channels for users to
report degradation without blame. “The CMM probe feels sticky” should be
a data point, not a complaint. “The database search returned garbage”
should be an improvement trigger, not a frustration.
Establish regular commons review meetings where stewards and users
discuss resource health. These meetings should be short, frequent, and
focused on trajectory rather than snapshot. “Is this resource getting
better or worse?” is the key question.
The Deeper
Lesson: Quality as a Commons Itself
Here is the most profound application of the Tragedy of the Commons
to quality management: quality itself is a commons.
Every department, every shift, every individual in an organization
benefits from the organization’s reputation for quality. That reputation
— that trust, that customer confidence, that market position — is a
shared resource. And every shortcut, every deviation, every “it’s
probably fine” moment is an individual herder adding one more animal to
the pasture.
The production manager who pushes a borderline lot through to meet a
delivery date benefits individually (the delivery is on time). The cost
is shared (the customer’s trust erodes slightly). The purchasing agent
who selects a cheaper, unqualified supplier benefits individually (cost
savings are visible). The cost is shared (incoming quality degrades).
The engineer who signs off on a design without thorough validation
benefits individually (the project timeline is met). The cost is shared
(the field failure rate increases).
Quality is not a department. It is not a metric. It is not a
procedure. It is a commons — a shared resource that every member of the
organization both draws from and contributes to. And like all commons,
it is vulnerable to the tragedy of individual rationality producing
collective catastrophe.
The
Antidote: Collective Responsibility Architecture
The organizations that avoid the Tragedy of the Commons in quality do
not do so through heroics or luck. They do so through architecture —
deliberate design of systems, incentives, and cultures that align
individual behavior with collective health.
This architecture includes:
- Shared visibility: Everyone can see the state of
shared resources - Distributed stewardship: Everyone has some
responsibility for commons health - Aligned incentives: Individual success is tied to
collective resource quality - Regular renewal: Resources are deliberately
refreshed, not just consumed - Cultural norms: Protecting the commons is valued as
highly as using it
The plants I’ve seen that maintain their calibration labs for
decades, that keep their databases clean and useful, that sustain their
institutional knowledge across generations — these are not better people
or smarter engineers. They are organizations that understood quality as
a commons and designed accordingly.
The Question You Need to Ask
Walk through your organization today and ask: What shared
resources does our quality system depend on? Who is responsible for
maintaining them? And how would we know if they were
degrading?
If the answer to the second question is “everyone” and the answer to
the third is “we wouldn’t,” you are living in a Tragedy of the Commons
that hasn’t yet reached its catastrophe. But it will.
The gages are degrading. The database is filling with noise. The
experienced operators are getting older. The procedures are drifting.
And every individual decision to defer maintenance, skip the data entry,
postpone the training, or tolerate the inconsistency is perfectly
rational.
That’s exactly the problem.
About the Author
Peter Stasko is a Quality Architect with over 25 years of experience
in manufacturing quality management. He has worked with organizations
across automotive, aerospace, medical device, and electronics
industries, helping them design quality systems that don’t just comply
with standards but actually work. His approach combines deep technical
knowledge of quality tools with an understanding of the human and
organizational dynamics that determine whether those tools are used
effectively — or just documented.
