Nobody owns your workload

I coach managers who are working 50+ hours a week and weekends just to keep up, not because they manage their time poorly but because there is more work than time, no matter how well they sequence it. The stress, anxiety, and frustration aren't time-management failures; they are the inevitable consequence of a workload that quietly burns people out.

What doesn't work

The common advice is to raise the workload problem with their boss. Ask for some tasks to be removed, or for another person to share the load. Almost every manager who tries this gets the same response: genuine sympathy, an admission that the boss is stretched just as thin, some minor task reshuffling or no change.

It's tempting to read that response as evasion — a boss protecting themselves by declining to advocate upward. Usually that's the wrong read. The boss's admission that they're in the same position is usually accurate, and it's telling you something important: they don't control the total volume of work landing on their team any more than the manager below them does.

Nobody approved "this much work." What arrived instead was a series of separate, reasonable decisions — a new initiative here, an urgent client ask there, a metric that needed attention — each approved on its own terms, by someone with the authority to approve exactly that piece. None of those approvals required anyone to look at the sum. The workload burying a manager isn't the output of a decision. It's the output of many decisions that were never added together.

This is why telling a manager to "push back" rarely produces the outcome they're hoping for, even when they do it well. Pushing back changes one conversation. It doesn't change the structure producing the volume, because that structure was never built to receive the signal in a form it can act on.

When a manager says “I can't sustain this”, it lands privately with their boss, receives a sympathetic hearing, and stops there. It never travels sideways to peers suffering the exact same issue, nor does it travel upward as a systemic pattern. Instead, leadership sees a single data point — and misinterprets an organizational resourcing crisis as one person's individual capacity issue. A manager weighing whether to raise it is also weighing a real cost: doing it alone risks reading as an inability to handle the pressure, with no guarantee the aggregate picture changes at all. The rational response, for almost anyone in that position, is to absorb it quietly. That isn't a failure of individual courage. It's what happens when a system has no channel for turning private signals into shared data.

What works

The version of this that eventually gets attention is the one that shows up somewhere leadership is already watching — turnover climbs, a delivery date slips, error rates rise. That's not because leaders were indifferent to the earlier signals and only started caring once the cost got large. It's because overload doesn't register on the ledger they're managing against until it converts into something that does.

A manager's exhaustion doesn't appear on a dashboard. Attrition does, eventually, but by then it's expensive, hard to trace back to its source, and often misread as a hiring-market problem or one person's fit rather than a structural one. The organization doesn't correct because someone finally notices the human cost. It corrects because the cost finally arrives in a form the organization was built to notice.

This means a manager caught in the middle isn't powerless, but the moves that actually work are the ones that engage this structure rather than try to out-manage it. Here are three things you can change:

Change what you ask for

Shift from "Can you take something off my plate?" (which asks for authority over total headcount or scope that a boss rarely has) to "Given everything on my plate, which of these should I deprioritize?" (which asks for something they can decide: relative priority).

Change what you bring to the conversation

An impression of being busy is easy to sympathize with and just as easy to set aside. A documented account of the actual work — especially one shared across two or three peers in the same position — is much harder to dismiss as one person's individual strain.

Change the language carrying the signal

"I’m burning out" registers as a personal problem, even to a sympathetic listener. "If this continues, the deadline slips" or "quality on this account will start to show it" registers as a business risk, framed directly in terms the organization already tracks.

These moves by themselves will not fix the underlying structure because it wasn’t built to process these kinds of demands. But at least they give a manager the best available leverage to influence how that structure responds.

There's also a stakeholder above the organization that is harder to influence but plays an important role. Investors, boards, and competitive pressure to hold or cut costs reward exactly the kind of headcount discipline that produces this pattern in the first place, and that pressure doesn't disappear once the tradeoff becomes visible. A leadership team can see clearly that its people are working past capacity and still decide the more urgent number to protect is margin. That's not a failure to notice the cost. It's a case where the visible cost is weighed against another cost that is treated as more important.

So the actual fix requires two things:

• A structural mechanism to aggregate workload data before it causes damage on the ledger that leaders actually pay attention to.
• A leadership choice to treat human capacity as a hard constraint rather than a negotiable line item.

Without the first, the tradeoff never becomes visible. Without the second, visibility isn't enough. Without both, an organization’s only reliable feedback loop runs through failure — missed deadlines, quality drops, and attrition. Those register on the dashboard, but the human overload underneath them doesn't until it breaks something expensive.

Alexander Spradling, PhD, is an organizational consultant and executive coach based in Austin, Texas. He writes Why Organizations Misbehave.