.png)
Burnout gets blamed on workload. But decades of research point to a more dangerous combination: heavy demands, and little say over how the work gets done.
When a team burns out, the first explanation is always workload.
Too many projects. Too many meetings. Not enough people.
Sometimes that's true. But it misses the more dangerous half of the problem.

In 1979, the researcher Robert Karasek proposed a model of job stress that still shapes the field. His core idea: high demands aren't harmful on their own. The damage comes when demands are high and control is low.
Studies since have consistently linked that combination, heavy workloads with little say over how the work gets done, to job strain and burnout.
Workload still matters. Heavy demands wear people down on their own. But give people real control over the work, and the same load becomes far more survivable, sometimes even energising.
Take control away, and even a manageable load starts to crush.

You launch campaigns, but decisions change overnight.
You offer strategic input, and it's brushed aside.
You're told you "own it," but approvals, rewrites and shifting priorities say otherwise.
You're responsible for outcomes, but have no influence over the inputs.
None of this shows up in a workload survey. It shows up in what people stop bringing to work.

Explain the why behind every change, especially the messy ones. People can live with a reversal. They struggle with one that arrives without a reason.
Delegate outcomes, not tasks. Let people own the how.
Keep your hands off decisions you've delegated. If you take them back every time you'd have chosen differently, you haven't delegated anything.
Protect time to think. A calendar with no space for thinking is a team with no room for control.
Connect the work to results people can see. Control over the inputs means little if nobody ever sees the output.

I worked with a marketing manager who was one of the strongest people on her team. She knew the customers, understood the work and was usually the person others went to when something needed solving. Her workload was heavy, but she'd never complained about working hard.
What changed was how little control she had over the work.
She would build a campaign strategy, only for the direction to change after she'd started. She'd make recommendations, then wait days for approval before being asked why the work was behind. Priorities changed without warning, but she was still held responsible for the original deadline. Each time she tried to take more ownership, another decision was pulled back to someone above her.
Eventually, she stopped.
In a one-to-one, she said something that stuck with me: "I used to bring ideas. Now I just bring updates."
That was the warning sign. She hadn't become less capable or less committed. She had learned that taking initiative created more work and more opportunities for someone else to override her. The safest way to work was to wait, execute and report.
The leadership team eventually realised what was happening, but by then it was too late. She left. The workload hadn't been what pushed her out. She'd been willing to work hard. What she couldn't sustain was being held responsible for outcomes she no longer had the authority to influence.
The team lost more than a good employee. It lost the judgement, initiative and problem-solving capacity she'd been bringing to the work: the very things leadership had gradually trained her to stop using.
Her replacement could take over the tasks.
They couldn't immediately replace the ownership they'd lost.
No noise. Only honest strategy, occasional reflection, and the kind of insights you actually want in your inbox.