A client escalates. The founder apologises for a delay that was never theirs to apologise for. Somewhere in the building, someone knew about the risk weeks ago - and said nothing. The founder finds out last, and only because the client is already angry.
It's a familiar scene, and it's not bad luck. Founders assume their team has things under control, so they stop asking hard questions until a client forces the issue. Sometimes the team really doesn't have it under control - and no amount of assuming fixes that. Accountability never made it past the founder in the first place.
The founder as firefighter
A project runs over. A delivery slips. The founder hears about it late, usually from the client, and jumps in to sort it out personally.
It feels responsible. It's actually the opposite. Every rescue is a consequence quietly rerouted - away from the team head who should have owned it, and onto the founder who shouldn't have to. So the team head never steps up, and the whole thing repeats next quarter.
The founder keeps catching balls that were never theirs to catch.
Where it actually breaks down
Most leadership teams are fine at reporting up. They're much worse at managing down.
A team head often knows exactly who on their team keeps missing deadlines, or who overpromises to clients just to keep the peace. They see it. They just don't say anything - because having that conversation is uncomfortable, and it's easier to pick up the slack, cover for it in the client meeting, or let it slide another month.
Founders have passed the authority down to their team heads. It's the team heads who aren't doing the harder side of leading their own people.
Why this creates blame instead of ownership
When a team head won't hold their own people to account, the problem doesn't shrink. It just changes direction -sideways, onto another team. A bad brief becomes someone else's fault. A missed handover becomes a process problem, not a person problem.
Every version of the story is technically true. None of them touch the real issue. What looks like departments at war is usually one thing: a leadership vacuum at team head level.
Holding the team accountable
It isn't about being harsh. It's a team head naming the standard clearly upfront rather than leaving it implied. “Try to hit the deadline” becomes “this is due Thursday, and here’s what happens if it slips.”
It's noticing when something has happened more than once, not just reacting to the incident in front of you. One late delivery is a bad week. Three is a habit - and the team head's job is to spot the third one before the client does.
It's having the conversation directly with the person responsible, not venting about them to a peer instead. And it's following through if the standard still isn't met, because a conversation with no consequence attached is no prevention.
The other half of accountability
Holding people to a standard isn't only about what happens when something goes wrong. We're all human, and mistakes happen. What matters is whether the team learns from it and puts something in place so it doesn't keep happening.
That's where a team head earns their place: talking someone through what went wrong and agreeing what would catch it earlier next time. Better still, being someone their team actually goes to when a deadline starts to feel shaky or a client relationship feels strained - before it turns into a problem rather than after.
That's a genuine balancing act. A team head needs to be firm enough that the standard means something, and approachable enough that their team would rather flag a risk early than hide it and hope.
What this asks of you as founder
Your job shifts from fixing the problem to backing your team heads when they do the fixing. That means:
- Resisting the urge to step around them and go straight to the person who slipped
- Asking “did you speak to them about it?” before you ask “what happened?”
- Being visibly behind a team head when they make an unpopular call - even if it costs you some short-term comfort with the wider team
That last point is the one founders skip most often, and it's the one that matters most. If a team head senses a hard conversation with their own person might get undermined by you later, they'll stop having them.
What changes
You stop being the last line of defence for every team's standards. Your team heads stop being senior members of their teams and start actually leading them.
None of this happens overnight. Team heads who've never been expected to hold the line will need you to back them the first few times it's uncomfortable. But every time you let one handle it instead of stepping in yourself, you get a little more of your agency back.
Before you ask what happened
There's a simpler way to check whether this is happening in your agency than waiting for the next escalation. Think about the last time you heard about a problem - did it come from your own team, or from the client? If the client got there first more than once this quarter, accountability is skipping a level somewhere between you and the work.
Then there's the harder question: can you actually name which team head is covering for someone right now? Most founders can't answer that straight away, and the silence isn't proof that nothing's wrong. It usually means nobody's told you yet, which is its own kind of answer.
And the one that matters most, because it's about you rather than them: the last time a team head made a call their team didn't like, did you stand behind it in the room, or did you smooth it over once they'd left? Team heads notice which one you did. It's often the whole reason they do, or don't, make the next hard call themselves.
None of this calls for a big process overhaul. It calls for asking these questions before the client asks them for you.
What this comes down to
Rescuing isn't leading - every time you personally fix a client escalation, you quietly remove the incentive for a team head to catch it earlier. Watch for the third occurrence: one late delivery is a bad week, but a pattern is a leadership gap. And the question worth asking first is “did you speak to them about it?” - not “what happened?” Most of all, back your team heads publicly, especially when their call is unpopular. Undermine them once, quietly, and they'll stop making hard calls at all.
