The Saturday Morning Text

A founder texted on a Saturday morning: "I give up. I'm just going to do it all myself."


She'd been gone for two weeks. Phone off, out of the country, the kind of disappearance every founder fantasizes about. When she came back, everything was exactly where she left it.

Client questions sitting in inboxes. Handoffs that hadn't happened. Fires nobody touched — not because they didn't care, but because they didn't know if they were allowed to.

Her first words: "I think I'm a bad leader."

She's not a bad leader. She's leading in a room with no walls.


This is the pattern we see over and over. A founder hires good people, tells them to "own it," and watches the same loop play out. Decisions stall. Things escalate. Nobody moves unless the founder moves first.

The standard diagnosis sounds like a people problem. "They don't care enough. They can't think for themselves. I need better hires."

It's not a people problem. It's an architecture problem.

When she's in the room, every decision finds her — because there's nowhere else for it to go. When she's gone, decisions don't get made. The team isn't free. They're exposed.

Brian Chesky said something in a Fortune interview late in 2024 that landed like a brick: "I don't believe in autonomy. I don't think employees want autonomy. I think that is a giant misnomer."

What he said next was the part that mattered: "What people don't want is a lack of empowerment. They want to be integrated, not disintegrated."

That word — disintegrated — is exactly right. Most founder-led teams aren't suffering from too much control. They're suffering from too little structure.

The founder removed themselves and called it empowerment. What they actually created was a room where every move could be wrong, so nobody moves at all.

Your team isn't asking for autonomy. They're asking for walls.


The fix isn't a reorg. It's not a new hire. It's not a leadership book.

It's three artifacts that answer the three questions every person on your team is silently asking but will never say out loud.

Where do I stand?

A weekly shared document. Three columns: Done, Stuck, Up Next. Every person fills it out before a standing meeting. Takes ten minutes.

This isn't a status report for the founder's benefit. It's a mirror for the team. When someone writes down what they finished, what's blocking them, and what's next, they stop guessing whether they're on track. The founder stops being the only person who knows what's happening.

One document. Updated weekly. Visible to everyone.

What do I own?

A single number per role. Not a job description — a scoreboard. One metric that tells each person whether they're winning or losing without asking anyone.

The ops person knows their number. The sales person knows theirs. When a client question comes in and two people look at each other wondering whose it is, the number answers before anyone has to.

This is the difference between "I think I'm responsible" and "I know I'm responsible." The first creates hesitation. The second creates movement.

Who decides?

A one-page decision rights document. It doesn't need to cover every scenario. It needs to cover the five to ten recurring decisions that currently bounce up to the founder by default.

Who approves refunds under a certain amount. Who calls the timeline on a deliverable. Who responds to a client escalation when the founder isn't available.

Most teams never write this down. So every decision becomes a question. Every question becomes an interruption. Every interruption reinforces the pattern: nothing moves unless the founder says so.

One page kills the escalation reflex.


Three walls. That's it.

A rhythm document so people know where they stand. A number so people know what they own. A decision page so people know when to act without asking.

This founder didn't need to fire anyone. She didn't need a COO. She needed to stop building freedom and start building rooms.

When she put the walls up, the same team that looked paralyzed started making calls on their own. Not because they suddenly cared more. Because they finally knew where the edges were.

The room didn't get smaller. It got usable.

Three months later, she left for ten days. When she came back, things had moved. Not perfectly. But they'd moved.

Decisions had been made. Clients had been answered. The team didn't need her presence to function. They needed her architecture.

Your team isn't free. They're exposed. Build the walls.

Keep Reading