The fix works — at first. The painkiller reduces the pain, the overtime push delivers the project on time, the discounted sale moves the inventory, the new hire fills the gap. And then, months or years later, you find yourself facing the same problem, usually worse than before, wondering what went wrong.
What went wrong is often a structural pattern that Peter Senge called Fixes That Fail: one of the most common and insidious systems archetypes. Understanding this pattern — recognizing it when it appears and knowing what to do instead — is one of the most practical things systems thinking can offer to managers, policymakers, and anyone trying to create lasting change in complex systems.
The Structure of Fixes That Fail
The Fixes That Fail archetype has two parts that interact through a time delay:
Part 1 — The symptomatic fix: A problem symptom is creating pressure. A solution is available that will relieve the symptom quickly. The solution is applied, the symptom decreases, the pressure eases. This is a balancing feedback loop that appears to be working exactly as intended.
Part 2 — The delayed side effect: The symptomatic fix has side effects that, after a delay, worsen the underlying condition that gave rise to the symptom. When those side effects eventually manifest, the symptom returns — often worse than before. More of the same fix is applied. The side effects accumulate. The symptom worsens further. A self-reinforcing cycle of fix-and-relapse develops, with the system becoming progressively more dependent on the fix and the underlying problem becoming progressively harder to solve.
Why the Pattern Is So Common
Fixes That Fail is ubiquitous because of a fundamental mismatch between how organizations and individuals perceive problems and how complex systems actually work.
We perceive problems as symptoms: immediate, visible, measurable signals of distress. We evaluate solutions by their effect on the symptom: did it go away? We tend to discount delayed consequences because they feel uncertain and distant. And we find symptomatic fixes readily available — they are faster, cheaper, and less disruptive than addressing underlying causes.
Complex systems, however, have structures that connect today’s actions to tomorrow’s conditions through multiple feedback loops and time delays. A symptomatic fix that relieves pressure today may erode the conditions — capacity, relationships, resources, fundamental solutions — that would allow the underlying problem to be truly resolved. The very relief the fix provides reduces the urgency of investing in the fundamental solution.
Real-World Examples
Organizational overtime
A team is behind schedule. The fix: overtime. The symptom (schedule slippage) is addressed. But overtime has delayed side effects: fatigue reduces productivity, errors increase, team morale declines, talented people leave. The team falls further behind, requiring more overtime. The Fixes That Fail cycle deepens. The fundamental problem — unrealistic project scoping or inadequate team capacity — is never addressed because the overtime always buys enough time to avoid a crisis, until it no longer does.
Discounting and promotions in retail
Sales are below target. The fix: a promotional discount. Sales increase, the symptom resolves. But the discount trains customers to wait for promotions before buying, erodes the brand’s price positioning, and pressures margins. The next time sales are below target, a bigger discount is needed to achieve the same effect. The brand’s pricing power erodes progressively as it becomes dependent on promotional pricing — a textbook Fixes That Fail pattern.
Antibiotic overuse
A patient presents with infection symptoms. Prescribing antibiotics relieves the symptom quickly. But overuse of antibiotics has delayed side effects: development of antibiotic-resistant strains that make future infections much harder to treat. At the population level, widespread antibiotic use solves individual infections while progressively undermining the effectiveness of antibiotics as a treatment modality.
Breaking the Cycle
The standard prescription in systems thinking for breaking a Fixes That Fail pattern is straightforward to state and difficult to implement:
Identify and invest in fundamental solutions. A fundamental solution is an intervention at the level of the underlying problem rather than its symptoms. Fundamental solutions are typically slower, more expensive, and more disruptive than symptomatic fixes — which is why they are consistently underinvested.
Make the side effects visible. The Fixes That Fail cycle persists because the delayed side effects are often invisible or misattributed. Explicit monitoring of the side effects of symptomatic fixes — including leading indicators of developing problems, not just the immediate symptom being fixed — can break the cycle by making visible what the system otherwise conceals.
Resist the short-term pressure to fix. When a symptomatic fix is available and a fundamental solution is not yet ready, the pressure to apply the fix is intense. Sometimes it cannot be resisted. But being explicit about the trade-off — using the fix as a short-term bridge while investing in the fundamental solution, rather than relying on it indefinitely — can prevent the gradual drift into long-term fix dependency.
Frequently Asked Questions
Is Fixes That Fail the same as Shifting the Burden?
They are closely related but distinct. In both archetypes, a symptomatic fix diverts attention and resources from a fundamental solution. The key difference is that Shifting the Burden emphasizes the atrophy of fundamental solution capability — the side effect erodes the system’s ability to implement the fundamental fix. Fixes That Fail emphasizes the aggravation of the underlying problem — the side effect makes the problem worse. Both patterns are common, and they often occur together.
Conclusion
The Fixes That Fail archetype is a reminder that short-term solutions and long-term outcomes are often in tension in complex systems — and that the most accessible solution is not always the most effective one. Recognizing this pattern when it is developing, making visible the side effects that the fix creates, and maintaining investment in fundamental solutions even when the symptom fix is working are the practical disciplines that distinguish systems thinking from reactive problem-solving. The fix may work in the short run. The question is always: what does it cost in the long run?
