Why fixes fail: shifting the burden

Fixes fail because most of them treat the symptom, and every time the symptom is relieved, the pressure to solve the underlying problem drains away while the capacity to solve it quietly atrophies. Systems thinkers call this pattern shifting the burden: the quick fix works, which is exactly what makes it dangerous. Breaking it requires doing something unnatural — keeping investment flowing to the fundamental solution while the symptomatic one is still doing its job.

What does "shifting the burden" actually mean?

It is one of the classic system archetypes — recurring loop structures that Donella Meadows catalogues in Thinking in Systems and that show up in businesses with depressing regularity. The structure has three parts. A problem symptom. A symptomatic fix that relieves it quickly. A fundamental fix that would remove it permanently but works slowly.

The trap is in the interaction. The symptomatic fix acts fast, so it gets used. Each use reduces the symptom, which reduces the urgency behind the fundamental fix. Worse, many symptomatic fixes create a side effect that erodes the very capability the fundamental fix needs — skills, systems, attention. Over time the organisation becomes structurally dependent on the patch. As I put it in the systems-thinking guide for founders, the behaviour is produced by the structure, not by anyone's laziness; competent people run this loop for years.

What is the most common version in a small B2B firm?

The founder as the fix. Pipeline looks thin, so the founder personally works their network and rescues the quarter. A deal wobbles, so the founder joins the call and closes it. It works — that is the problem. The mechanism runs like this: when the founder rescues the quarter, the symptom (thin pipeline) disappears; when the symptom disappears, the project to build a repeatable pipeline slips down the list; when that project keeps slipping, the team never develops the muscle to generate demand; when the team lacks the muscle, the next thin quarter can only be fixed by the founder — and each cycle deepens the dependency. Run that loop for five years and you have a firm that cannot grow past its owner's calendar, a pattern I have written up fully in the Founder-as-Bottleneck report.

Other versions are everywhere once you know the shape. Hiring to paper over a broken process — a £35k+ a year BDR thrown at lead generation with no system underneath, so the process leaves when they do. Discounting to close deals instead of fixing positioning. Reminding people manually instead of automating the follow-up. Answering the same client question weekly instead of writing it down once.

Why doesn't the fundamental fix just happen eventually?

Because of delay, and delay is the villain in most system stories. The fundamental fix — documented process, an outbound system, trained staff, a rebuilt onboarding — pays back over months. The symptomatic fix pays back today. Under quarterly pressure, today wins every time, and the books balance in a way that hides the cost: the patch shows up as revenue saved, while the erosion of capability shows up nowhere at all. No dashboard has a line called "problems we can no longer solve ourselves".

There is also an identity component that founders rarely admit. Being the fix feels good. The rescue is visible, appreciated and immediate; the system that prevents rescues is invisible precisely when it works. People repeat what gets applauded.

How do you break the pattern?

Not by banning the quick fix — sometimes the quarter genuinely needs rescuing. The discipline is to run both loops at once and protect the slow one.

1. Name the burden. Write down, in one sentence, what the recurring rescue is compensating for. "I close deals because nobody else can" names a training and process gap, not a heroism requirement.
2. Price the patch. The founder rescue costs the firm its most expensive hours; the BDR patch costs £35k+ a year plus management. Put the number next to the cost of the fundamental fix and the comparison usually embarrasses the patch.
3. Ring-fence the fundamental fix. Fixed budget, fixed scope, a deadline that does not move when the next fire starts. This is one reason we deliver systems as fixed-price builds with a 30-day clock — an open-ended internal project loses to the urgent symptom every single week.
4. Let the fix carry a tripwire. Each use of the symptomatic fix triggers a small mandatory contribution to the fundamental one: rescued a deal, then document what closed it; answered the question again, then write the page.

The tripwire is the part most firms skip, and it is the part that converts shocks into structure — the same property that makes a pipeline that benefits from shocks possible.

How do you know which fix you are looking at?

One test: if this fix works, will the problem be back? A fundamental fix removes the loop; a symptomatic one guarantees a repeat booking. Shifting the burden is only one of a small family of traps that produce this feeling of running hard and staying still — I cover the rest of the family in the system archetypes founders keep living. Learn the shapes and you stop blaming people, including yourself, for what the structure was always going to do.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.