Burnout is the bill for the design work nobody did
The smooshed middle: burnout and the layer problem
If you're a middle manager leading a high-performing team, you've probably noticed something the wellbeing literature completely skips over: you're being held accountable for outcomes that don't flex, in conditions you don't control.
You're absorbing pressure from above and below, and often sideways from customers or other stakeholders. You're watching people pay the cost of decisions you didn't make, but when someone takes unplanned leave, or quits, or just goes quiet, you're the one who's supposed to fix it.
You've read the articles, taken the courses, been told your team needs to be more resilient, or that you need to develop your soft skills. You've probably been taught that high performance and wellbeing are in tension, and it's your job to find the balance between them. None of it has quite lined up with your actual experience as a leader.
This post is for you.
The false choice
Right now, we're hearing two stories about burnout.
The first: burnout is a personal weakness. People aren't resilient enough. They need better boundaries, more mindfulness, more sleep. The fix is individual.
The second: burnout is a leadership gap. Managers push too hard, miss the signs, don't model recovery. The fix is managerial: better one-on-ones, more emotional intelligence, psychological safety training.
Both stories are wrong in the same way. They locate the problem at a single layer of the organisation. When your team is burning out despite individual resilience and despite your care, neither of you is failing at your part. There's a piece missing, one that neither of you can replace alone. Until that piece falls into place, the wellbeing conversation will keep missing the point.
What burnout actually is
Workplace burnout becomes inevitable when an organisation fails to do its actual job of building systems that can deliver sustained performance, and externalises the missing design work onto the humans inside it.
Every organisation's actual job is to translate inputs (capital, talent, time, attention) into outputs (products, services, revenue) efficiently. Doing that job well requires design work: deciding what to build, how to sequence it, who will do what, what to defer, how to coordinate, what to commit to externally given internal capacity.
This design work is genuinely hard. It requires senior people to accept that fast-cheap-good is a trade-off with real consequences. It requires honesty about what the organisation can actually deliver.
When that design work doesn't happen, there's a gap. Something has to absorb it. That something is always, eventually, an overachieving human.
Burnout is the bill for the design work nobody did.
Why the standard arguments don't hold
"But sometimes you genuinely have to sprint." Yes. But notice the move here: from "the organisation needs sprint-level output" to "individuals need to sprint all the time." That's an unsustainable solution to a recurring problem. Sprint-level output is a systems-design problem: rotation, load-sharing, removing coordination friction, investing in tooling. Constant sprint-level exertion is what happens when the organisation skips the design work and asks individuals to absorb the gap instead.
"But high-performing organisations have always operated this way." Stable patterns aren't evidence of good design. They're evidence of cultural reinforcement, sunk cost, and absence of legitimate alternatives. Stability is not the same as performance.
"But our org is successful, so the model must work." Some organisations succeed despite their operating model. Momentum, brand inertia, and tough employment markets can all obscure real externalised costs. When those protections weaken, those costs tend to be exposed quickly.
Organisations that punish wellbeing-conscious management are usually not high-performance organisations. They're organisations whose performance measurement is broken.
Where you actually sit
Three layers are at play.
The individual owns their response. No one else can notice their signals for them, pace their work for them, or recover for them. That is non-transferable.
The manager is accountable for local conditions: workload conversations, recovery legitimacy, decision transparency, the psychological safety to discuss real capacity. The things that make individual ownership achievable in this team, on this work, this quarter.
The organisation is accountable for the upstream conditions that make local accountability dischargeable: headcount, deadlines, comp, promotion criteria, cultural defaults. "The organisation" is not a single person; the accountability runs to specific decision-makers, up to the board.
The squeeze you're feeling — the sense of being asked to absorb something that isn't yours — is the chain breaking at some layer above you.
What's actually yours to do
Not all of this is yours to fix; not even most of it. But there may be more than you're currently doing, and those parts are powerful.
Grok the system you're shaping. Your team experiences your local design, not the org chart. The pace you set, the tradeoffs you name, the work you defer, the rest you legitimise are all conditions you can set, regardless of what's broken above you.
Run workload conversations honestly. Especially when the upstream constraint is bad. Ask your reports what they have capacity for. Believe them when they answer. Make tradeoffs explicit when something has to give. Most teams burn out not because they're working hard but because they don't understand why the work is shaped the way it is, and have no idea what they're allowed to push back on.
Discuss stress and recovery openly at the team level. If they remain private matters absorbed silently by those in hero-mode, burnout becomes much more likely. When they're coordinated information the team holds together, they become manageable. Who needs some breathing room? Who's getting smashed this week? What can move? Who can help? It costs almost nothing and it changes recovery from an individual problem into a team practice.
Refuse to silently absorb the gap. When you're being asked to deliver outcomes under unreasonable conditions, say so, in language that engages rather than blames: "I can deliver X under these conditions. I can't deliver X without them. How should we handle this?" This is not insubordination. It's accountability running in the right direction. If you don't do it, you become the shock absorber that hides the org's design failure from itself, and you pay the bill personally.
The hard limit
Some organisations are not survivable for managers who care about their people. That isn't because wellbeing and performance are in tension — they actually compound — but because the chain is broken at a layer you can't reach, the org has chosen a target you don't share, or the pattern is so ingrained that naming it makes you the problem rather than the messenger. In those organisations, you can do everything right, and the gap will still push you and your team towards burnout.
If that's your situation, leaving isn't failure. It's the rational move.
What we're for
This is the work we help with at TANK.
We help you build the local conditions where individual and team ownership of wellbeing is actually achievable. We make the gap between what's yours and what isn't visible, so you can stop filling the design gap, and stop paying the bill.
You can read more about the evidence base for our work here, take a look at how we work here, or join the beta for our new Teams product here.