What is shifting the burden?

A pattern in which a quick fix relieves a symptom, weakens the effort to fix the root cause, and leaves the system more dependent on the quick fix.

Shifting the burden diagram example

Public diagram from the Machinations Community. Open it on its own page

Shifting the burden is a system archetype, a recurring pattern of behavior. A problem is handled by a quick fix that works right away, so the harder, lasting fix is never made. Over time the system depends more on the quick fix, and the root problem remains or gets worse.

How it works

Two balancing loops compete. One uses the quick fix and reduces the symptom fast. The other would use the fundamental solution but is slower and costs more effort. Because the symptom disappears, the pressure to apply the fundamental solution fades. A side effect often makes it worse: the quick fix erodes the ability to do the lasting one, such as a team that stops learning skills because an outside contractor always steps in. Breaking the pattern means strengthening the fundamental fix and limiting the quick one.

A warning sign is a quick fix that has become permanent. If a temporary measure is still in place a year later and nobody can say when it will end, the burden has probably already shifted.

Example

Say a company has late deliveries caused by poor forecasting. Each month it pays 20,000 for rush shipping, which hides the lateness. Fixing the forecast would cost 60,000 once and remove the need. Over a year, rush shipping costs 240,000 and the problem remains. Because lateness is hidden, nobody approves the 60,000 project. This is an illustration with round numbers.

How to model it in Machinations

Draw a Pool for the symptom, with a Drain for the quick fix that acts immediately and a Delay before the slower fundamental fix takes effect. Use a state connection so the quick fix reduces the effort sent to the lasting fix. Play the diagram over a long horizon and compare total cost with each Lever setting.

See shifting the burden in a system you can Play

Build the rules in a Machinations diagram, change a value and Play it to watch how the system responds.