Learn it → Apply it → Save as Skill
The quick fix is quietly taxing the real fix. When a problem's symptom flares up, it's tempting to patch it fast — and that patch often works, in the moment. But lean on the same patch again and again, and it doesn't just fail to touch the root cause: it erodes the resources, skill or motivation you'd need to ever fix things for real. The relief and the relapse come from the same loop.
The Dr. Wallace’s Favorite Mental Models is designed to turn useful ways of thinking into reusable tools. Each model gives you a fast visual overview, deeper interactive learning, practical application exercises and an AI-ready Markdown skill you can save for future use.
Instead of merely reading about mental models, you can gradually build your own AI skills library: a collection of portable reasoning skills that can help ChatGPT, Claude, Grok and other AI assistants apply the mental models you value.
Shifting the Burden is a systems-thinking pattern: a problem symptom can be relieved two ways — a fast symptomatic fix, or a slower fundamental fix that addresses the root cause. The fast fix feels responsible and works immediately. But each time it's used instead of the real fix, it quietly drains the capacity, resources or motivation needed to ever apply the real fix — so the symptom keeps coming back, and the real fix keeps getting harder to reach.
Important: this snapshot is misleading on its own. Run the same comparison a year later, after repeated quick fixes, and the picture flips — relief from the quick fix keeps shrinking while the capacity to even attempt the fundamental fix has quietly eroded too.
The model is most useful wherever a recurring symptom gets patched repeatedly by the same fast fix, and no one has checked whether that fix is eroding the ability to solve it for good.
The pattern tells you a quick fix can quietly disable the real one. It does not by itself tell you whether, in your case, the quick fix is actually doing that.
A symptom keeps returning after being "solved" the same way each time — the fix works, then stops working, then gets reapplied.
Separate the symptomatic fix (fast, addresses the symptom — B1) from the fundamental fix (slower, addresses the root cause — B2). Name both explicitly, even if only one is in use.
Look for a reinforcing loop (R): does using the quick fix repeatedly reduce the resources, skill or motivation available for the fundamental fix? If so, the trap is active.
Choose to invest in the slower fix even though it is less immediately rewarding, using the quick fix only as a deliberate, time-limited bridge.
Open a use case to see what the model changes.
If a system's recurring failure mode is fixed every time by bringing in an outside consultant rather than ever building in-house capability, the team's own debugging skill for that system never develops — and next time, the consultant is needed again, often sooner. This is the "shifting the burden to the intervenor" variant: an outside helper repeatedly solving the problem for a system that never builds the muscle to solve it for itself.
Jumping in to fix a direct report's deliverable is faster than coaching them through it, and it protects the immediate deadline. But each rescue is a missed chance for the report to build the skill — so the manager keeps being needed for the same kind of task, and the report's own problem-solving capacity never gets exercised.
Borrowing or running a credit card balance to cover overspending relieves the immediate cash shortfall, but it does not touch why spending exceeded income. Repeated reliance on credit can also make the harder work of rebuilding a sustainable budget more difficult, since a growing share of income goes to debt service instead.
Heavy discounting reliably moves this quarter's number, which is why it is tempting to reach for again next quarter. But pulling forward demand at a discount can cannibalize future full-price sales, and a sales team that leans on discounting instead of building durable demand can find the discount doing more and more work for less and less result.
Using caffeine to power through tiredness relieves the symptom fast and gets the day done. Used night after night as a substitute for fixing the sleep schedule itself, it treats the same symptom repeatedly while the underlying sleep debt — and the harder work of actually fixing the schedule — never gets addressed.
Some systems-thinking writers use subsidy or welfare programs as an illustration of the structure: support that relieves immediate hardship (the symptom) without ever being paired with investment in root causes like job access or wages could, in principle, reduce pressure to fix those causes. This is a genuinely debated example with credible counter-arguments on multiple sides — it is included here to illustrate the loop structure, not as a policy verdict.
This is an illustrative scenario designed to teach the method. It is not drawn from any real company's data.
Expand for where the pattern comes from, what its loop structure means, its intervenor variant, and how to read its evidentiary status accurately.
Shifting the Burden is one of the systems archetypes catalogued by Peter Senge in Appendix 2 of The Fifth Discipline (1990). Systems archetypes are recurring causal-loop patterns drawn from the system dynamics tradition, used to recognize structures that produce predictable behavior across very different kinds of problems.
A problem symptom can be addressed two ways. A symptomatic solution (a balancing loop, B1) relieves the symptom quickly but leaves the underlying cause untouched, so the symptom tends to return. A fundamental solution (a second balancing loop, B2, with a longer delay) addresses the root cause but takes longer and is less immediately rewarding. The trap is a third loop: a reinforcing side-effect loop (R) in which repeated use of the symptomatic fix erodes the capacity, resources or motivation ever needed to apply the fundamental fix — so leaning on the quick fix makes the real fix progressively harder to reach.
This is a named sub-variant in which an outside helper — a consultant, an expert, a senior person who always steps in — repeatedly solves the problem for the people inside the system. Writers in the systems-thinking tradition, including Daniel Kim writing in The Systems Thinker, describe how each rescue further erodes the system's own problem-solving capacity, deepening dependence on the intervenor rather than building the capability to do without one.
No — and it is worth being precise about that. Shifting the Burden is a qualitative structural pattern from the system dynamics and systems-thinking tradition, used as a diagnostic lens in management and organizational practice. It is not a lab-measured cognitive effect with an experimental literature behind it the way some other mental models on this list are; its value is as a way of naming and recognizing a causal structure, not as a quantified, tested finding.
Not all symptomatic relief erodes the real fix. The failure mode is using the quick fix as a permanent substitute, not using one at all — a short-term bridge paired with a real fix already underway is a different situation entirely.
Watching someone lean harder and harder on the same quick fix can look like laziness or incompetence. The loop structure predicts that outcome in almost anyone placed inside it — the dependency is a property of the system, not a character flaw.
The fundamental fix is slower and less immediately gratifying by definition — that is exactly what makes the quick fix tempting every single time. Waiting for the real fix to feel rewarding before committing to it gets the sequence backwards.
A token effort at the real fix that grows slower than the problem itself will lose the race, and the quick fix will keep looking like the only thing that works. The fundamental solution has to be strong enough to actually outpace the problem.
Cutting off the symptomatic fix abruptly, with no bridge and no fundamental fix yet in place, can make things worse before it makes them better. The goal is changing the ratio and the intent behind the quick fix, not necessarily eliminating it overnight.
Treating a standing arrangement with an outside expert as pure efficiency can hide a "shifting the burden to the intervenor" pattern already in progress — the question to ask is whether reliance on that expert is flat, or rising.
the fundamental fix genuinely is not worth the cost, the symptom is low-stakes, or the quick fix is not actually eroding anyone's capacity to fix the root cause later.
it is explicitly short-term and paired with a fundamental fix that is already underway — a short-term painkiller prescription alongside physical therapy that has already started is not Shifting the Burden, it is a deliberate bridge.
the real issue is that the quick fix creates a new, different problem that makes the original symptom worse later — not that it is eroding the capacity to apply a separate, fundamental fix.
This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.
Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to apply Shifting the Burden, what questions to ask, what evidence to seek, what mistakes to avoid and how to structure its analysis.
Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.
No — the model does not say shortcuts are bad. It says a specific structure exists: the quick fix does not just fail to fix the root cause, it actively erodes the capacity to fix it later. A shortcut that does not touch that capacity at all is not an example of this pattern, even if it is still "just a shortcut."
No. The trap is about repetition and substitution, not a single instance. A quick fix used once, as a deliberate bridge while the fundamental fix is already being built, is explicitly the kind of case this model says is fine. The pattern describes what happens when the quick fix becomes the default response instead.
Plain procrastination delays a fix without necessarily making it any harder to do later. Shifting the Burden describes something stronger: a feedback loop in which the postponement itself actively degrades the resources, skill or motivation the fundamental fix would need — so the delay compounds rather than simply accumulates.