Set out as a systems archetype by Peter M. Senge (The Fifth Discipline, 1990) and restated by John D. Sterman (Business Dynamics, 2000).
Describes how a fix relieves a symptom now but triggers a delayed side effect that brings the problem back worse, the delay hiding the link.
Overtime clears a support backlog for a month, then tired work reopens it
Set the overtime and how fast tiredness fades, then Play. The fix (B1) clears tickets at once; the side effect (R1) reopens them weeks later, and the backlog ends above where it began. With no overtime it sits at 300. Illustrative.
Open tickets
Tickets reopened a week
Week 16 of 16
- Open tickets
- 406
- Tickets reopened a week
- 82
- B1, The fix
- More open tickets bring more overtime, and overtime closes tickets: the queue falls within days. One negative (−) link: an odd count, so the loop balances.
- R1, The side effect
- Overtime builds tiredness, tiredness reopens tickets weeks later, and the larger queue calls for still more overtime. No negative (−) links: an even count, so the loop reinforces.
- Open tickets
- The symptom: 300 open tickets after a confusing release, against a normal 100. New tickets arrive as fast as the regular shifts close them, so the queue does not shrink on its own.
- Overtime hours
- The fix: extra hours asked of each of ten agents while the queue stays above normal. Each hour clears five tickets across the team.
- Tired hours carried
- Overtime not yet recovered from. It builds week by week and fades only by the share set on the slider.
- Tickets reopened
- The side effect: tired agents close tickets with partial answers, and customers reopen them. Each carried tired hour reopens one and a half tickets a week.
An example
A payroll software company shipped a January release with a confusing new screen, and its support queue jumped to 300 open tickets against a normal 100. The support manager asked each of the ten agents for eight hours of overtime a week. Within five weeks the queue was under 200, and the overtime was praised at the leadership meeting.
By week seven it was climbing again. Tired agents were closing tickets with partial answers, customers were reopening them, and two agents were out sick. In week thirteen the queue passed 300, and the manager asked for more overtime. The head of operations drew it as two loops on one page: overtime clearing the queue within days, and overtime building tiredness that reopened tickets about a month later. The team capped overtime at four weeks per agent, added a second check before any ticket could close, and put the confusing screen at the top of the product backlog, since it was still sending in a hundred tickets a week.
Why it works
The pattern is hard to see because both halves of it are true. The fix does ease the symptom, and the side effect does bring it back, but they run on different clocks. The balancing loop answers within days. The loop of consequences builds slowly and shows up weeks or months later, by which time the fix has been credited and the relapse is blamed on something else. The relapse then makes the fix look more necessary, so more of it gets applied, and the side effect grows with it.
Drawing the two loops side by side puts both clocks on one page. Once the delay is marked, the question changes from whether the fix works to how long it works and what it costs afterward, and a team can put rough numbers on both.
The thinking behind it
Peter M. Senge Peter M. Senge, a senior lecturer at MIT Sloan, named fixes that fail among the system archetypes in the appendix of The Fifth Discipline (1990), the book that brought system dynamics to managers and set systems thinking among five disciplines of a learning organization. An archetype is a feedback structure that recurs across very different businesses. This one pairs a balancing loop, the fix easing the symptom, with a reinforcing loop of unintended consequences that arrives late, so a team that knows the shape can spot it before the second loop shows up.
John D. Sterman John D. Sterman, director of the MIT System Dynamics Group, restated the archetype in Business Dynamics (2000), the standard textbook of the field, among the structures built from stocks, flows, feedback loops, and delays. His beer distribution game experiments, reported in Modeling Managerial Behavior (Management Science, 1989), showed that managers misread feedback and delays and order in ways that create wild swings in inventory. That finding explains why capable people fall into this archetype: the delay hides the link between the fix and the problem's return.
How to run it
- Name the symptom and the fix. Write the symptom as a number that can rise or fall, and the fix as the action taken when it rises.
- Draw the fix loop. Link the symptom to the fix and the fix back to the symptom with a minus sign; this balancing loop is why the fix looks good.
- Trace the fix past its first result. Ask what else it changes in people, equipment, customers, or money over the next three to six months.
- Find the delayed path back. Look for a chain from those changes to the symptom, and mark the delay on it.
- Put rough numbers on both loops. Even guessed figures show roughly which week the side effect overtakes the relief.
- Cap, redesign, or replace the fix. Limit how long it runs, weaken the side effect, or work on what is feeding the symptom.
- Watch the side effect from day one. Its leading number moves weeks before the symptom does, so put it in the same weekly review.
Where it goes wrong
The usual failure is stopping the trace at the first result. The fix works, the meeting moves on, and the side effect arrives months later in someone else's report, where nobody ties it to the decision. Spot it when every review of the fix quotes only the symptom's number, and recover by adding the side effect's number to the same review.
A second failure is calling every relapse a fix that fails. Some problems come back because their cause was never touched, which is shifting the burden and asks for a different remedy; check whether the fix itself drives the return. A third is throwing out a sound fix. Two weeks of overtime may be fine. Four months of it is the trap.
When to use something else
- Shifting the Burden. When the symptom keeps returning because the quick fix stands in for the real remedy, and the ability to deliver that remedy is fading.
- Second-Order Thinking. When the decision is still open and a quick pass over the consequences of consequences is enough, before any loop is drawn.
- Causal Loop Diagram. When the situation matches no known archetype and the loops have to be drawn from scratch.
Where it sits in SOLVE eX
Go to the source
- The Fifth Discipline, 1990
- Business Dynamics, 2000