The burnout trap in a scaling team
Heroics feel like leadership when the workload spikes. They are actually how a team quietly disables the only fix that would have saved it.
When the work suddenly outruns the team, a good manager does something. Usually that something is heroics — longer hours, a weekend push, a few strong people carrying the rest. And it works. The backlog burns down, the deadline holds, and everyone feels like the situation is under control.
That sense of control is the trap. The fix that relieves the pain fastest is also the one that quietly removes the reason to ever fix it properly — and it brings a second, slower loop that eats the team alive.
Two fixes for one symptom (the Shifting the Burden shape)
The symptom is workload — the gap between what is asked and what the team can absorb. There are two ways to close it.
The symptomatic fix is overtime and heroics. When pressure to fix spikes, this is the lever that is already in reach: it needs no budget, no approval, no waiting. It pulls workload down today. Call that balancing loop B1.
The fundamental fix is to hire, automate, or prioritize — add real capacity, remove toil, or stop committing to so much. It also pulls workload down, durably, but on a delay. Call that balancing loop B2.
Two balancing loops chasing the same symptom is the signature of the Shifting the Burden archetype. Notice the starting values in the model: heroics at 60, the fundamental fix at 28. The team already lives on the easy loop.
Why the easy fix sabotages the real one
Look at the edge from heroics to hire / automate / prioritize: it is negative. This is the heart of the archetype. Every time heroics relieve the workload, they also drain the urgency and the slack that the fundamental fix needs to get funded. Nobody approves a hire when last week ended fine. Nobody automates a workflow when there is no time to automate it because everyone is busy doing it by hand.
So B2 atrophies. The fundamental capability — the team's ability to ever solve this structurally — withers from disuse. The system becomes addicted to heroics not because they are good, but because they keep pre-empting the alternative.
The side-effect loop that turns a trap into a spiral
Shifting the Burden gets genuinely dangerous because of a third loop the daily firefight hides. Heroics drive burnout; burnout erodes team capacity; and lower capacity means the same demand lands as a bigger workload gap — which raises pressure, which calls for more heroics. That is a reinforcing loop, R, and it runs the wrong way.
Run the simulation above. The symptomatic loop holds workload down for a while, then the burnout edge (note the delays) catches up: capacity drifts down, the gap reopens wider than before, and the team is now running harder just to stay in the same place. This is why heroic teams do not plateau — they relapse, each cycle worse than the last.
The leverage point
You do not escape Shifting the Burden by working harder, and you do not escape it by banning overtime overnight — pull heroics to zero while the gap is real and delivery simply collapses.
The leverage is to commit to the fundamental fix and use heroics only to buy the time to install it. Concretely: protect a fixed slice of capacity for hiring, automation, and de-scoping even during the crunch; treat every heroic week as a debt that triggers a structural investment, not as a win; and make the burnout → capacity loop visible so the slow erosion stops being invisible. Strengthen B2 deliberately, and the reinforcing trap R loses its fuel.
This system is an instance of Shifting the Burden — read the full pattern.
Hebel is launching soon. Join the early list and lock in 30% off — plus 10% more per friend you bring.