C:\> SYSTEM MESSAGE

FREE PLAYBOOK PDF · 14 PAGES

The Founder Bottleneck

4 practical shifts to make your company run without you. For founders who have built a great company and accidentally made themselves indispensable to it.

Get the playbook Run the 3-minute diagnostic

By Bruna Hamori, co-founder of SHIFT

First, a difficult question

What would happen if you disappeared from your company for 30 days?

Not a vacation where you're checking Slack from the beach. Not "I'm technically off, but message me if you need anything." Truly unavailable. No approvals. No answers. No decisions. No rescuing.

Would the company keep moving? Or would things slowly start waiting for you?

It usually starts for a very good reason: the founder cares. You know the business better than anyone, you decide fast, you have the context. At the beginning, that's exactly what makes the company move. As it grows, the same behaviours quietly turn you into its biggest operational bottleneck.

OBJECTION.EXE

"My business is different. My clients expect me."

Your clients expect quality, speed and answers. They don't care whether the answer comes from you, as long as it's right. What they can't tolerate is waiting three days because everything is stuck in your inbox.

The dependency on you personally is something you built. Which is good news, because it means you can unbuild it.

04

The framework

Four shifts. One dependency at a time.

The solution isn't to "let go" overnight. It's to systematically remove the reasons why the company needs you.

01_VISIBILITY.SYS

Make work visible

Replace the daily sync with an async stand-up.

The daily meeting is theatre: everyone performs being busy, the founder collects status. The async version is a signal system for the team. Each person posts a hello, a 1 to 5 capacity score and today's priorities. Coordination leaves your head, and people start reacting to each other before you do.

C:\> START_TODAY

Open one thread for tomorrow morning. Ask everyone to post three things: a quick hello, how their day looks from 1 to 5, and what must move today.

02_KNOWLEDGE.SYS

Make knowledge transferable

Make "done" mean documented.

Don't document the past. That project dies in week one. Document the present: nothing is truly delivered until the relevant knowledge is captured. A recording with timestamps, a checklist, a short page. Six months from now you'll have a living operating system instead of a graveyard of half-finished pages.

C:\> START_TODAY

Take the last important thing your team delivered and ask: could someone who wasn't involved understand what this is and how to use it? If not, document it.

03_AUTOMATION.SYS

Remove repetitive work

Automate what your team hates, after fixing the process.

We don't automate chaos. Automating a broken process creates the same mess faster, at scale, with less visibility. First simplify and assign ownership. Then automate, starting with the task your team hates most, so automation arrives as relief instead of threat.

C:\> START_TODAY

Ask your team: what's the task you do every week that you'd happily never do again? Don't promise anything yet. Just listen.

04_DECISIONS.SYS

Move decisions to the work

Delegate the decision, not just the task.

Set decision boundaries: what the team decides, up to what threshold, and what escalates. One wrong call inside a boundary costs you once. You as the permanent approval layer costs hours every week, forever. Expand the boundary as confidence grows.

C:\> START_TODAY

Pick one recurring decision that waits for you. Define a threshold below which the team decides alone, and tell them today.

One more rule

Don't bring me a question. Bring me the question plus the research.

10 seconds × 20 questions × 5 people × every week

If your team knows you'll always have the answer, there's little incentive to search for it first. Why spend ten minutes in the documentation when the founder answers in ten seconds?

Suddenly the founder has spent hours being the company's search engine. Create a simple expectation instead: before escalating a question, tell me where you looked.

GOOD_ESCALATION.LOG

"I checked the refund policy, looked at the previous three cases and asked Sarah because she handles similar requests. I still couldn't find an answer. What do you recommend?"

That's a completely different question. It says: I've thought about this, here's what I found, I need your judgement. That's the kind of question a founder should be answering.

The playbook

Everything above, in full. Plus the parts that don't fit on a page.

14 pages. Bruna's account of what worked, and what didn't, inside real operations. Tell us where to send it.

  1. 01The 1 to 5 capacity scale your team can start using tomorrow
  2. 02The six-question check to run before you automate anything
  3. 03The decision-boundary template, with the honest maths on mistakes
  4. 04The objections founders raise for each shift, answered
  5. 05The 30-day worksheet: what would break, and what to do with each item

Bruna Hamori built operations inside startups, agencies and Alan, the European health-insurance unicorn known for its async, AI-first operating model. Dismantling founder dependencies is now literally her job.

DOWNLOAD.EXE

C:\> SAVE AS PDF

Send me the playbook

You get the PDF right here, and a copy by e-mail.

By sending, you allow SHIFT to store and process the data above to deliver what you asked for. Privacy Policy.

14 pages · PDF · free

C:\> RUN DIAGNOSTIC

Ready to fix the operation?

Book a 30-minute Diagnostic. We'll look at how your company operates today, identify the biggest bottlenecks and tell you what we'd fix first.

Pick a time

30 minutes. No pitch.