Peter Stasko · Quality Architect · May 30, 2026
The
Tale That Gave a Name to a Problem You Already Have
In colonial Delhi, the British government grew concerned about the
population of venomous cobras. Their solution was elegant in its
simplicity: offer a cash bounty for every dead cobra brought to an
official. For a time, it worked. Dead cobras piled up. The
administrators congratulated themselves.
Then something unexpected happened. Enterprising citizens began
breeding cobras in secret — because a live cobra was now a revenue
stream. When the government caught on and canceled the bounty program,
the breeders released their now-worthless snakes into the streets. Delhi
ended up with more cobras than before the intervention.
The Cobra Effect — a term coined by German economist Horst Siebert —
describes any incentive that perversely produces the exact behavior it
was designed to eliminate. It is not a historical curiosity. It is alive
and well on your factory floor, in your quality department, and in the
metrics dashboard you check every morning.
If you have ever watched a quality initiative produce more defects, a
safety program generate more incidents, or a continuous improvement
campaign make things worse, you have met the cobra.
Why the Cobra
Effect Loves Quality Departments
Quality organizations are particularly vulnerable to perverse
incentives because quality work is inherently difficult to measure. You
cannot directly observe “quality.” You can only observe proxies: defect
counts, scrap rates, customer complaints, audit scores, first-pass
yields. And every proxy, the moment it becomes a target, begins to warp
the behavior it was meant to capture.
This is not a failure of intent. Your people are not breeding cobras
maliciously. They are responding rationally to the system you built. The
problem is not their character. The problem is your architecture.
Consider the structure of most quality incentive programs. Management
identifies a metric that represents a problem. They attach a reward to
improving that metric. They announce the program. They wait for
improvement. And initially, they see it. The numbers move in the right
direction. The dashboard glows green. The quarterly report looks
impressive.
But beneath the surface, the cobra breeders are at work — not literal
snake farmers, but engineers, inspectors, operators, and managers who
have discovered that the fastest path to the reward is not to solve the
problem but to optimize for the metric.
The
Breeding Grounds: Where Cobras Hatch in Your Organization
1. The Defect Reduction
Bounty
A plant manager announces a bonus for every team that reduces its
defect rate by 20%. The intention is genuine: fewer defects, happier
customers, lower costs. The teams respond. Within a quarter, defect
rates plummet.
What actually happened? The inspectors began grading defects more
leniently. Borderline cases that were previously flagged as
nonconformances were now classified as “process variations.” The defects
did not disappear. They were relabeled. The underlying process continued
to produce the same variation, but the numbers looked better because the
classification boundary shifted.
This is cobra breeding in its purest form: you incentivized the
reduction of reported defects, and you got fewer reported defects. You
did not get fewer actual defects. You got better fiction.
2. The Scrap Rate Target
A company ties department bonuses to scrap rate reduction.
Engineering teams respond by reclassifying scrap as “rework” or
“reprocess.” Material that would have been discarded is now routed
through additional processing steps — consuming energy, labor, and
machine time — to avoid the scrap label. The scrap rate improves. The
cost of production increases. The customer sees no difference in
quality, but the organization pays more to produce the same output.
The cobra here is subtle: the incentive did not improve quality. It
changed accounting. The waste still exists. It is just wearing a
different hat.
3. The Customer Complaint
Ceiling
A customer service team is told that their performance evaluation
depends on keeping formal customer complaints below a threshold. The
response is predictable: complaints are resolved informally before they
enter the tracking system. Customers are offered discounts, expedited
shipping, or free replacements — all outside the complaint system. The
formal complaint count drops. Management celebrates. Meanwhile, the cost
of informal resolution exceeds what formal complaint handling would have
cost, and the root causes of the complaints remain unaddressed.
You did not fix the complaints. You built a shadow system to hide
them. That is your cobra.
4. The Audit Score Imperative
An organization decides that every department must maintain an
internal audit score above 90%. Departments respond by optimizing for
the audit rather than for quality. Checklists are memorized.
Documentation is immaculate. The auditor walks through a pristine
operation that bears little resemblance to daily reality.
The score stays above 90%. The underlying processes remain unchanged.
When a real quality event occurs — a customer return, a field failure, a
regulatory finding — everyone is shocked. How could this happen with
such high audit scores?
It happened because you incentivized the score, not the quality. The
cobra was born the day you tied consequences to a number instead of to
the reality the number was meant to represent.
5. The Training Completion
Metric
A quality manager mandates that 100% of operators must complete the
new statistical process control training within 60 days. The deadline is
tight. The trainers are overwhelmed. The solution: operators are herded
through the training in compressed sessions, clicking through slides,
passing multiple-choice tests that test memorization rather than
understanding. Completion rates hit 100%. The training matrix glows
green.
Six months later, process capability has not improved. Operators
cannot interpret a control chart. They attended the training. They did
not learn. You incentivized seat time and got exactly that: seat
time.
The Architecture of
Perverse Incentives
The Cobra Effect does not appear because people are bad. It appears
because incentive systems have a structure, and that structure has
properties that are often invisible to the people who design it.
Understanding the structure helps you avoid the trap.
Property 1: Proxy Distance. The further your metric
is from the actual outcome you want, the more room there is for the
metric to improve while the outcome stays the same or worsens. “Reported
defects” is a proxy for “actual defects.” “Audit scores” are a proxy for
“process quality.” “Training completion” is a proxy for “operator
competence.” The greater the distance between proxy and outcome, the
more likely the cobra appears.
Property 2: Gaming Affordance. Any metric that can
be improved through classification, redefinition, or reclassification
rather than through genuine improvement will be. This is not cynicism.
It is rational behavior within the system you created. If the fastest
path to the reward is relabeling rather than resolving, rational actors
will relabel.
Property 3: Time Horizon Mismatch. Most perverse
incentives work because the reward is immediate and the consequences are
delayed. The defect reclassification produces a bonus this quarter. The
field failure it masks shows up next year. The scrap rework saves the
metric today. The excess cost accumulates over months. Human
organizations are spectacularly bad at connecting immediate rewards to
delayed consequences.
Property 4: Single-Metric Focus. When you optimize
one metric in isolation, you inevitably degrade the system that the
metric was meant to represent. Reduce defect counts, and rework
increases. Reduce scrap, and throughput drops. Reduce complaints, and
root cause analysis disappears. Every metric is connected to every other
metric. Pull one thread, and the whole fabric shifts.
Recognizing the Cobra: A
Diagnostic
Before you design your next incentive program, run it through this
diagnostic:
Question 1: Can this metric be improved without improving the
actual outcome? If a team can hit the target by reclassifying,
redefining, or redirecting work rather than by genuinely improving, the
cobra is already in the room. Redesign the metric or use multiple
complementary metrics.
Question 2: Does this incentive reward appearance over
reality? If the reward depends on what is reported rather than
what is real, you are incentivizing reporting, not quality. Build
verification into the system — independent audits, cross-checks,
customer feedback loops that cannot be gamed from inside.
Question 3: What is the easiest path to the reward?
Do not ask what you intended. Ask what a clever, rational, time-pressed
person would actually do to get the bonus. If the easiest path is not
the path you want, the incentive is structurally broken.
Question 4: What happens when everyone optimizes for this
metric simultaneously? Cobra Effects are often invisible in
isolation. They become catastrophic when they scale. One team
reclassifying defects is a nuisance. Every team reclassifying defects is
a systemic failure of measurement.
Question 5: What behavior would make this metric look good
while making quality worse? This is the most important
question. If you can answer it, you have identified the cobra. Now
design the incentive so that behavior is not rewarded.
Building
Cobra-Resistant Quality Systems
Use Metric Triangulation
Never rely on a single metric to represent a complex outcome.
Instead, triangulate. Track defect rates alongside customer returns,
alongside rework costs, alongside first-pass yield. If defect rates drop
but customer returns hold steady, the improvement is fictional. If scrap
decreases but rework increases, nothing actually changed. Triangulation
makes gaming harder because it requires falsifying multiple independent
measurements simultaneously.
Reward Process, Not Just
Outcome
Incentives that reward only outcomes invite gaming. Incentives that
reward process adherence — following the standard, conducting the root
cause analysis, completing the corrective action — are harder to game
because the behavior is observable directly. You can watch whether the
team conducted a proper 8D investigation. You cannot easily verify
whether the defect count is genuine. Reward what you can see.
Separate Measurement From
Incentive
The people whose performance is measured should not be the same
people who define the measurements. If the production team defines what
counts as a defect, and their bonus depends on defect counts, the
definition will drift toward generosity. Independent measurement —
quality engineers who report outside the production chain, customer data
collected by a separate organization, automated measurement systems that
cannot be reconfigured on the fly — creates a check on the natural drift
toward favorable classification.
Design for the Long Term
Short-term incentives produce short-term thinking. If your quality
incentive pays out quarterly, you will get quarterly optimization.
Consider incentive structures that reward sustained improvement over
years: gain-sharing programs, career progression tied to demonstrated
process capability, recognition based on customer outcomes rather than
internal metrics. The longer the time horizon, the harder it is to
sustain a fiction.
Build in Dissent
The first sign of a Cobra Effect is usually noticed by someone on the
front line — an inspector who sees the reclassification happening, an
operator who notices the training was a formality, a customer service
rep who knows the complaints are being handled outside the system. But
these people rarely have a channel to report what they see without fear
of retaliation.
Build explicit mechanisms for reporting metric gaming. Anonymize the
reporting. Protect the reporters. And — critically — act on what they
report. The moment an organization punishes someone for pointing out
that the emperor has no metrics, it guarantees that every future cobra
will breed undisturbed.
The Uncomfortable Truth
The Cobra Effect is not a risk you can eliminate. It is a property of
incentive systems, the way friction is a property of physical systems.
You cannot wish it away. You can only design systems that minimize it,
monitor for its emergence, and correct course when it appears.
This requires humility. It requires accepting that your carefully
designed incentive program — the one the board approved, the one the
consultants endorsed, the one looks perfect on the PowerPoint slide —
will produce unintended consequences. Not because people are bad.
Because systems are complex, and the gap between what you intended and
what you incentivized is always wider than you think.
The British in Delhi were not stupid. They saw a problem, designed a
solution, and implemented it. The problem was not their intelligence.
The problem was their model. They assumed that paying for dead cobras
would reduce the number of cobras. They did not account for the fact
that paying for dead cobras also created an economic incentive to
produce live ones.
When you design your next quality incentive, ask yourself: what is
the cobra I am breeding? What is the live snake that my dead-snake
bounty will bring into existence? Because the cobra is always there. It
is always waiting. And the organizations that survive are not the ones
that believe they are immune. They are the ones that assume the cobra is
already in the room and design accordingly.
The Checklist
If your quality metrics have never surprised you — if every
initiative produces exactly the improvement you expected — you are not
running a quality system. You are running a cobra farm. The first step
toward genuine improvement is the willingness to ask whether your
numbers are real or whether you are just counting dead snakes while
someone breeds more in the basement.
About the Author
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing excellence, process optimization,
and quality systems design. He has helped organizations across
automotive, electronics, and heavy industry build quality cultures that
survive contact with reality — including the reality that every
incentive system breeds its own cobras. His work focuses on the
intersection of human behavior, organizational design, and the
mathematics of variation.
