Why Everything Routes Back to You (And What to Actually Do About It)

There’s a pattern that shows up in almost every small team I work with.

The founder is sharp. The team is capable. Everyone is working hard. And yet every caption, every pitch, every newsletter draft, every client proposal ends up back at the top for a final call. Back on the desk of the person who already has the most on it.

This gets diagnosed a lot of different ways. Trust issues. Letting-go problems. Control tendencies. It gets handed to an executive coach, a therapist, a business advisor — sometimes all three, sometimes in the same quarter. And those are all legitimate investments. I’ve made them myself.

But when I sit with this problem longer, something different shows up. Something upstream of the trust conversation.

The real issue is decision architecture. Nobody ever defined what “good” looks like clearly enough for anyone else on the team to make the call.

There’s no measurement. No documented threshold for what can ship without a sign-off versus what genuinely needs one. No shared understanding of the standard. So in the absence of that clarity, every decision defaults upward — and the person at the top ends up carrying a decision load that was never supposed to be theirs in the first place.

That breeds resentment. In small teams, it breeds burnout. The team starts to feel micromanaged. The founder starts to feel like they can’t let go. And both things are true, because neither person has been given the information they need to operate differently.

This is what I call a governance failure — and it’s one of the most common things I find when I sit down with a small organisation and start asking how communications are actually flowing.

What governance actually means in a small team

Governance sounds corporate. In the context of a two-person firm or a nonprofit with a six-person team, it just means three things are answered clearly:

• Who owns creating it?
• Who owns reviewing it?
• Who owns approving it — or does it even need approval at all?

That last question is the most important one. Because in most small organisations, the approval question has never been asked. Nothing has ever been designated as “this can ship without me.” Everything is implicitly flagged for review, even the things that shouldn’t be.

So the team learns, fairly quickly, that the safest move is to ask. Always ask. Ask before shipping, ask after drafting, ask during the process. It protects them. But it also means the founder never gets out of the production line.

The team isn’t being difficult. The founder isn’t failing to delegate. The structure is just missing the thing that would let them operate differently.

The question I always ask

When I work through this with a client, I ask one diagnostic question:

>>> Can your team ship communications without coming back to you for every decision?

Not “could they theoretically?” Not “are they good enough?” The behavioural question: does it currently happen?

For most of the organisations I work with, the answer is no. And when I ask what the holdup is, the answers almost always map back to the same gap. The standard hasn’t been documented. “Good” is still a feeling that lives in the founder’s head, not a reference that lives somewhere the team can access.

When good isn’t written down, it’s not transferable. And an untransferable standard is, functionally, a bottleneck with your name on it.

What changes when governance is clear

A few things shift when a team actually builds this out.

The team gains confidence. Instead of asking “is this okay?” before every send, they start saying “this meets our standard” — and shipping accordingly. That shift in language is not small. It represents a fundamental change in how communications decisions get made inside the organisation.

The founder gains time. The decision load that’s been quietly accumulating — the quick Slack check-ins, the last-minute rewrites, the approvals that should have been non-events — starts to shrink. Not because the founder stopped caring about quality, but because quality now has a definition that lives outside their head.

And the output gets more consistent. Not because the team suddenly got better, but because they finally have a clear picture of what better looks like.

---

This is one of six things I’m covering on April 22nd

Governance is the G in the BRIDGE Framework — the six-pillar communications infrastructure system I’ve built from years of working inside small organisations and watching what actually breaks down when they try to communicate at scale.

The full framework runs Brief, Rhythm, Infrastructure, Distribution, Governance, Escalation. Each pillar depends on the ones before it, and each one addresses a specific structural failure that tends to get misdiagnosed as something else. A people problem. A capacity problem. A messaging problem. Almost always, it’s upstream of all of those.

On April 22nd I’m running a free 60-minute workshop called Communications Chaos to Cadence: A Workshop on the BRIDGE Framework. Live on Zoom. We’ll go through all six pillars, and by the end of the session you’ll know exactly which one is your biggest gap right now — and where to start.

Registration is open at erintrafford.com/workshop-april.

You’re not tired because you’re doing too much. You’re tired because you’re deciding too much. That’s fixable.

---