Fixes that Fail Archetype
Core Idea
Fixes that Fail is a system archetype where a quick fix initially solves a problem symptom, but unintended consequences eventually worsen the original problem, often prompting even more of the same ineffective solution.
What the Pattern Is
A problem symptom appears, prompting a solution that works in the short term. The symptom improves, validating the fix. However, after a delay, unintended consequences emerge that make the original problem worse. This creates pressure to apply even more of the same “proven” fix, deepening the cycle.
Pattern structure:
- Initial balancing loop: Fix applied to reduce problem symptom
- Short-term success: Fix works, symptom improves
- Hidden delay: Time lag obscures the connection between fix and consequences
- Unintended consequences worsen the original problem
- Escalating spiral: More pressure to apply the fix that’s causing the problem
Why It Matters
The delay between fix and consequences prevents learning. Short-term success creates confidence in the fix. When the problem returns, it seems like “we need more of what worked before.” The true cause-effect relationship remains invisible without systems thinking.
Common examples:
- Cost-cutting: Reduces headcount improving short-term financials, but degrades quality, leading to lost customers and worse cost pressure
- Technical debt: Quick-and-dirty code solutions speed delivery but accumulate maintenance burden that slows all future development
- Deadline pressure: Forcing overtime meets near-term schedules but causes burnout, quality problems, and rework — creating worse delays later
Leverage Points
- Don’t apply more of the same when the problem returns — this is a signal the fix itself is failing
- Identify and address root causes, not just symptoms
- Map potential unintended consequences before implementing solutions
- Look for patterns of repeated fixes — if you’ve solved this problem before, it may be a fix that fails
Related Concepts
- Systems-Thinking - Fixes that Fail is a fundamental system archetype
- Balancing-Feedback-Loops - The initial fix operates as a balancing loop
- Reinforcing-Feedback-Loops - Unintended consequences create a vicious cycle
- System-Delays - Delay between fix and consequences obscures the pattern
- Shifting-the-Burden-Archetype - Related pattern: symptomatic vs. fundamental solutions
- Leverage-Points - Leverage exists in addressing root causes rather than symptoms
Sources
- Senge, Peter M. (1990). The Fifth Discipline: The Art & Practice of The Learning Organization. Doubleday/Currency. ISBN: 978-0-385-26094-7.
- Chapter 6: Nature’s Templates (pp. 93-113); Archetype: Fixes that Fail
- Available: https://www.penguinrandomhouse.com/books/366/the-fifth-discipline-by-peter-m-senge/
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.