There is a pattern that destroys quality departments from the inside,
and most organizations never recognize it until the damage is
irreversible. It does not arrive as a dramatic failure or a catastrophic
defect. It arrives as a slow, quiet depletion — the gradual exhaustion
of shared quality resources that everyone uses and no one maintains.
Calibration schedules slip because “someone else” will handle them.
Shared inspection tools degrade because “it’s not my department.”
Quality documentation becomes outdated because updating it is
“everyone’s responsibility,” which means it becomes no one’s. By the
time the organization notices, the commons are barren, and the quality
system that once protected production has become a hollow shell.
This is the Tragedy of the Commons applied to quality management, and
understanding it is essential for any manufacturing organization that
depends on shared resources, shared standards, and shared
accountability.
The Original Insight
The concept originates with ecologist Garrett Hardin, who in 1968
described a scenario in which multiple herders share a common pasture.
Each herder benefits from adding one more animal to their flock, but the
cost of overgrazing is distributed among all herders equally. The
rational choice for each individual herder is to add more animals — more
profit for them, shared cost for everyone. But when every herder follows
this logic, the pasture is destroyed, and all herders suffer.
The tragedy is not that people are malicious. The tragedy is that
individually rational decisions produce collectively catastrophic
outcomes. Each person acts in their immediate self-interest, and the
system collapses because no one has sufficient incentive to preserve
what everyone depends on.
In manufacturing quality, this dynamic plays out every single
day.
The Quality Commons in
Manufacturing
Every manufacturing organization has a quality commons — shared
resources, systems, and standards that no single person or department
owns exclusively but that everyone depends upon. These commons take many
forms.
Shared measurement systems are perhaps the most
visible quality commons. Calibration standards, reference materials,
master gauges, and shared inspection equipment exist in a liminal space
between departments. The quality lab maintains them, but production uses
them. Engineering specifies them, but purchasing procures them. When
calibration drifts or reference materials degrade, the cost is borne by
whoever suffers the bad measurement — which could be any department, on
any shift, at any time. The incentive to maintain the commons is
diffuse. The incentive to use them and move on is immediate and
personal.
Quality documentation represents another critical
commons. Work instructions, control plans, FMEAs, inspection standards,
and process specifications are living documents that require continuous
updating. But updating them is invisible work. It does not produce
parts. It does not ship orders. It does not generate revenue. So the
documentation commons is steadily depleted — instructions become
outdated, control plans no longer reflect actual processes, and FMEAs
reference equipment that was replaced years ago. Everyone assumes
someone else is keeping the documents current. No one is.
Shared quality knowledge is perhaps the most
insidious commons. The collective understanding of why processes work
the way they do, what failure modes have been encountered, what lessons
were learned from past defects — this knowledge lives in the
organization’s collective memory. But when experienced inspectors
retire, when engineers transfer, when operators move to new lines, the
knowledge commons is depleted. And because it was never formally owned
or curated, the organization cannot even measure what it has lost.
Cross-functional quality processes are another
commons that degrades predictably. Material review boards, corrective
action teams, process change reviews, and supplier quality meetings all
require participation from multiple functions. Each participant faces a
choice: invest time and attention in the shared process, or focus on
their own department’s immediate priorities. The rational individual
choice is often to send a subordinate, prepare minimally, or skip the
meeting entirely. Over time, the cross-functional quality process
becomes performative rather than substantive — people attend, but the
quality of participation has been depleted from the commons.
The Mechanics of Depletion
Understanding why the quality commons depletes requires understanding
the incentive structure that drives individual behavior.
Consider a shared calibration laboratory. Three production
departments use the lab’s measurement instruments daily. The quality
department is responsible for maintaining calibration, but their budget
is tight and their headcount is limited. When a calibration deadline
approaches, the quality engineer must choose: pull someone off a
pressing audit finding to perform the calibration, or defer it to next
week. Deferring costs nothing immediately — the instrument still reads
something, and production can still use it. But the measurement
uncertainty grows with each passing day.
Now multiply this decision across every shared resource in the
organization. Every calibration deferral, every outdated document, every
skipped review meeting, every unwritten lesson learned — each is a small
withdrawal from the quality commons. No single withdrawal is
catastrophic. But the cumulative effect is devastating.
The mathematics are unforgiving. If ten departments each make one
small withdrawal from the quality commons per week, that is five hundred
withdrawals per year. Each withdrawal is individually rational — the
department got what it needed, saved time, met its own targets. But the
commons has been depleted by five hundred increments, and no one made a
single deposit.
This is why quality systems that work beautifully during initial
implementation gradually degrade over time. The implementation was a
focused investment — a concentrated deposit into the commons. But
ongoing maintenance is distributed across all users, and the withdrawal
rate far exceeds the deposit rate.
Real-World Manifestations
The Tragedy of the Commons appears across every manufacturing sector,
in organizations ranging from small job shops to multinational
corporations.
In automotive manufacturing, the APQP process — Advanced Product
Quality Planning — is designed to be a comprehensive shared framework
for launching new products. Every function contributes: engineering
designs the product, manufacturing plans the process, quality develops
the control plan, purchasing qualifies suppliers. But APQP is a commons.
When timelines compress, individual functions begin cutting corners on
their APQP deliverables. Engineering skips the design FMEA review.
Manufacturing defers the process capability study. Quality accepts a
preliminary control plan. Each cut is individually rational — the
function meets its deadline. But the APQP commons has been depleted, and
the result is a product launch plagued with issues that a complete APQP
process would have prevented.
In pharmaceutical manufacturing, validated processes represent a
quality commons. The validation was performed collectively — engineering
installed the equipment, quality wrote the protocols, operations
executed the runs. But maintaining the validated state requires ongoing
discipline: change control, revalidation assessments, periodic reviews.
When a small process change is made without going through change control
because “it’s just a minor adjustment,” the validation commons has been
depleted. Over time, the cumulative effect of dozens of uncontrolled
changes is that no one actually knows what the validated state of the
process is anymore.
In aerospace manufacturing, first article inspection records are a
quality commons. They document that the first production part from every
process meets all requirements. But maintaining the FAI system —
updating it when processes change, training new inspectors on FAI
requirements, keeping the records accessible and current — is shared
work that often gets neglected. The result is an FAI system that exists
on paper but has not accurately reflected the manufacturing process for
years.
In electronics manufacturing, the bill of materials and its
associated quality requirements represent a commons that is constantly
under pressure. When engineering changes a component substitution
without updating the incoming inspection requirements, when purchasing
changes a supplier without triggering a requalification, when quality
accepts a deviation without documenting the rationale — each action
withdraws from the BOM integrity commons. Eventually, the BOM no longer
accurately describes what is being built or how it should be
inspected.
The Ownership Vacuum
The core problem is not that people are careless or indifferent. The
core problem is that the quality commons has no clear owner.
In most organizations, quality resources that are shared across
departments exist in an ownership vacuum. The quality department is
responsible for the quality system, but they do not own the production
equipment, the engineering specifications, or the purchasing decisions
that affect quality. Production owns their equipment and their output,
but they do not own the calibration system or the quality documentation.
Engineering owns the design, but they do not own the inspection
processes that verify it.
This ownership vacuum creates a gap where maintenance of the commons
falls. Everyone agrees the commons should be maintained. No one has the
authority, the budget, or the incentive to do it.
The problem is compounded by the way organizations measure
performance. Department-level metrics reward department-level outcomes.
Production is measured on throughput. Engineering is measured on
time-to-market. Purchasing is measured on cost reduction. Quality is
measured on defect rates. None of these metrics rewards investment in
the shared commons. All of them reward withdrawing from it.
Solutions: Enclosing the
Commons
Elinor Ostrom won the Nobel Prize in Economics for her work
demonstrating that the Tragedy of the Commons is not inevitable — that
communities can and do manage shared resources effectively through
institutional design. Her principles translate directly to quality
management.
Define clear boundaries. Every quality commons needs
explicit boundaries that define who has access, under what conditions,
and with what responsibilities. A shared calibration system should have
documented rules about who can use instruments, how they must be
handled, and what happens when a problem is identified. Vague shared
access is an invitation to depletion.
Establish rules that match local conditions. Generic
quality procedures imposed from corporate headquarters often fail
because they do not account for local conditions. The rules governing a
shared quality resource should be developed by the people who actually
use it, with deep understanding of the specific constraints and
requirements of that environment.
Ensure those affected by the rules can modify them.
When quality rules are imposed from above and cannot be adapted by the
people who must follow them, the rules themselves become a source of
commons depletion. People work around rigid rules rather than through
them, and the workaround culture erodes the commons faster than honest
engagement would.
Provide monitoring and accountability. The quality
commons needs active monitoring — not as surveillance, but as
stewardship. Someone needs to be watching the calibration status of
shared instruments, tracking the currency of shared documentation, and
monitoring the health of cross-functional quality processes. This
monitoring should be performed by people who are accountable to the
users of the commons, not to a distant authority.
Apply graduated sanctions. When someone depletes the
quality commons — skips a calibration, fails to update a document,
bypasses a review process — there should be consequences. But the
sanctions should be graduated, starting with reminders and escalating
only for repeated or willful violations. The goal is to maintain the
commons, not to punish people.
Provide accessible conflict resolution mechanisms.
When disagreements arise about the use or maintenance of shared quality
resources, there needs to be a quick, accessible way to resolve them. If
the only path is a formal escalation through management layers, the
conflict will fester, and the commons will continue to degrade while
people argue.
Recognize the right to self-organize. The most
effective quality commons management happens when the users of the
commons are empowered to organize their own governance. A
cross-functional team that manages a shared measurement system, with
representation from every department that uses it, will produce better
outcomes than a top-down mandate from quality management.
Practical Implementation
Implementing these principles in a manufacturing quality context
requires specific, concrete actions.
First, conduct a quality commons audit. Identify every shared quality
resource in the organization — measurement systems, documentation,
knowledge bases, cross-functional processes, training systems — and
assess the health of each. Ask three questions: Who uses this? Who
maintains it? What happens when it breaks? If the answer to the second
question is vague or involves multiple parties with no clear
accountability, you have found a commons at risk.
Second, assign explicit ownership for every quality commons. This
does not mean transferring the resource to a single department. It means
designating a steward — an individual or a small team — who is
explicitly responsible for monitoring the health of that commons and
escalating when depletion is detected. The steward does not need
authority over all users. They need visibility into the state of the
commons and a clear escalation path.
Third, create commons maintenance metrics. If you do not measure the
health of the quality commons, you cannot manage it. Track calibration
currency rates, documentation update frequencies, cross-functional
meeting participation rates, knowledge transfer completion rates. Make
these metrics visible to the organization. What gets measured and
displayed gets maintained.
Fourth, build commons maintenance into regular workflows rather than
treating it as a separate activity. Documentation updates should be
triggered by process changes, not by calendar reminders. Calibration
checks should be integrated into production changeovers, not scheduled
as separate events. Knowledge capture should happen during
problem-solving, not as a separate documentation exercise after the
fact.
Fifth, recognize and reward commons stewardship. If the only metrics
that matter are individual department metrics, no one will invest in the
shared commons. Create recognition for teams and individuals who
contribute to maintaining shared quality resources. Make commons
stewardship a visible, valued part of performance evaluation.
The Cost of Ignoring the
Commons
Organizations that ignore the Tragedy of the Commons in their quality
systems pay a price that compounds over time.
The immediate cost is inconsistency. When shared measurement systems
are not maintained, different departments produce different results from
the same measurements. When documentation is outdated, different
operators follow different procedures. When knowledge is lost, the same
problems are solved repeatedly by different people who do not benefit
from past experience.
The intermediate cost is inefficiency. Every depletion of the quality
commons forces someone, somewhere, to compensate. Inspectors add extra
checks because they do not trust the calibration. Engineers over-specify
because they do not trust the process capability data. Quality managers
add layers of approval because they do not trust the cross-functional
review process. The compensation is invisible — it shows up as longer
cycle times, higher inspection costs, and slower response to changes —
but it is real and it is expensive.
The long-term cost is catastrophic failure. When the quality commons
has been sufficiently depleted, the organization loses its ability to
detect, prevent, and respond to quality problems. The shared measurement
system no longer provides reliable data. The documentation no longer
reflects reality. The knowledge base no longer contains the lessons of
past failures. The cross-functional processes no longer provide
meaningful oversight. The organization is flying blind, and it does not
even know it.
This is how organizations that once had excellent quality systems
experience sudden, inexplicable quality crises. The crisis is not
inexplicable. It is the predictable outcome of years of incremental
depletion of the quality commons.
The Stewardship Mindset
Ultimately, preventing the Tragedy of the Commons in quality
management requires a fundamental shift in mindset — from consumption to
stewardship.
The consumption mindset asks: What can I get from the quality system?
How can I use it to meet my department’s targets? What can I safely
defer or delegate?
The stewardship mindset asks: What is the state of the quality system
I am inheriting? What am I doing to maintain it for those who come after
me? What deposits am I making, not just withdrawals?
This mindset cannot be mandated. It must be cultivated through
leadership, through example, and through organizational structures that
reward stewardship as much as they reward individual performance. The
organizations that maintain excellent quality systems over decades are
not those with the most sophisticated tools or the largest quality
departments. They are the organizations that have solved the Tragedy of
the Commons by creating a culture where shared quality resources are
valued, maintained, and protected — not because someone is forcing it,
but because everyone understands that the commons is the foundation upon
which their individual success depends.
The tragedy is not inevitable. But preventing it requires intention,
structure, and the recognition that the quality system is not just a
tool to be used — it is a commons to be preserved.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality management, process
optimization, and continuous improvement across automotive, aerospace,
electronics, and industrial sectors. He writes about the intersection of
organizational psychology, systems thinking, and quality engineering —
because the hardest quality problems are never just technical.
