Founders don't burn out from working too hard. They burn out from holding too much.
by Chloe Field
If you spend any time with early-stage founders like we do, you’ll hear something like this:
"I have to be across everything or it all falls apart" "I don't trust anyone to do the work" "No one just handles things"
And beneath it all, if I sit with someone long enough, I usually end up hearing:
"I'm working during my days off" "I'm just so exhausted"
I understand this because I've worked closely with founders at a senior level for nearly ten years. I'm also a founder myself at re/Work alongside Kristen Gallagher and this is the work we're most proud of.
Here's what I notice in our founder coaching sessions: it rarely starts as a control issue. It begins as a caring issue.
Founders care deeply. So deeply that sometimes it becomes their downside. They hired good people, built something amazing from scratch, and are genuinely trying to hold it all together. The problem? The way they held it together at the start - across every decision, big and small - never got updated as their team grew.
So now you've got a team that technically owns things... but still looks to you before they make a move.
What this really looks like in practice
There's usually a beloved Google Sheet, Notion doc, or project tool that everyone works from. And yet, everyone's still waiting for the founder to have their say.
Because they've realised that decisions don't always stay final. Someone makes a call, and it gets changed a day later. A direction is set, but then reworked. Again.
After that happens a few times, people stop backing themselves. Even your best people start to feel undervalued. And when people don't feel trusted, they stop showing up as the capable humans you hired them to be.
You see it in small moments too. A client Slack message lands, the founder jumps in "wait, what's going on here?" and suddenly the whole team is back in a thread, re-explaining, re-deciding, resetting.
It doesn't seem like a big issue at first, but over time, the cracks start to show and soon enough it's affecting the whole team, turning into a pattern (or a rollercoaster 🙃🎢).
Where burnout actually comes from
At the start, this was the founder’s baby. They were involved in every decision. They made every move. They loved the "build" phase. Problems start creeping in when they begin hiring and scaling, yet they're still operating as if it's a 1-2-person show. The founder never fully stepped back or simply couldn't let go. Even though they’ve employed clever people to help carry the load.
It's not about the volume of work. It's about the absence of real delegation and clean handovers. When everything still flows through one person, that person never genuinely gets a break. Every day becomes relentless context-switching: team problems, sales, client questions, product decisions, hiring, operations - all landing on the same brain, ALL DAY 🤪
That's not sustainable. And the founders we work with know this. They're not oblivious, they're just stuck in a pattern that made complete sense when they started and nobody's helped them find the way out yet or given them space to step back for a moment to zoom the heck out to breathe!
What shifts when you actually fix it
The fix isn't complicated, but it does require the founder to genuinely let go. Which honestly is the hardest part... Once you start working on it, the change is noticeable. Meetings get sharper. Decisions get made and stay made. Your team starts bringing perspectives you weren't even looking for and those perspectives make everything better.
There's more trust on both sides.
Founders can actually take a day off and come back to a team that handled it.
That sounds small. It's not. It's everything and doable!
The goal isn't to remove founders from the picture. It's to build a team structure that doesn't require them to be the single point of contact for every decision. One where people are genuinely trusted to do their best work and the founder gets to actually lead instead of just firefight.
The thing I had to unlearn
The shift from firefighting to leading doesn't just change the team, it changes you.
Early in my career, I think I confused calm leaders with detached ones. Maybe even misunderstood calm for weakness?
Now I understand: Calm is a form of power.
It's the ability to pause before reacting. To lead with questions rather than opinions. To create space for better thinking and choices. And here's what's ironic: sometimes detaching is a good move. Not as a weakness, but as a deliberate act of leadership. There is so much flying at founders every single day that being calm actually requires you to step away, mentally and emotionally.
The most effective founders don't lack drive. They just learn to make decisions from steadier ground and surround themselves with good people.
If you're reading this and thinking "this is me" - you're not failing, you're just due for a reset.
This is exactly the kind of work we love to do at re/Work. Helping founders move from everything 'runs through me' to something the team can do together.
Decision fatigue is real and burnout is inevitable when everything still depends on one person to keep moving. It's a heavy thing to carry alone. Once that weight gets lifted, things start to feel more manageable. Not just for you, but for everyone around you.
What's one thing on your plate right now that should genuinely be someone else's call?
Sit with that for a moment. That's usually a good place to start.