The Founder Bottleneck Audit: A 30-Minute Exercise

If work stops whenever the founder is away, the problem rarely starts with a missing software tool. It starts with decisions and knowledge that have never been made visible. This short audit shows where to begin.

Map the interruptions

For one week, capture every request that needs your approval, explanation, or intervention. Note who asked, what decision was needed, how long it waited, and the consequence of waiting. Do not judge the team or solve the problem yet. The goal is to see the pattern.

Sort by decision type

Group requests into three categories: routine decisions with a known rule, judgment calls within a safe range, and high-consequence decisions that genuinely require you. Most founders discover that routine questions consume a surprising share of their attention.

Write one decision rule

Choose the most frequent routine request. Document the trigger, the information needed, the person who decides, the acceptable range, and when to escalate. Keep the rule to one page. A useful process should help someone act without interpreting a long manual.

Test it for two weeks

Let the team use the rule, then review exceptions in a scheduled meeting. Track how many requests still reached you and whether quality changed. If exceptions are frequent, improve the rule or the training. If the decisions are sound, move to the next bottleneck.

Protect the owner’s time

The purpose is not to disappear from the business. It is to spend your attention where it changes the outcome: strategy, people, capital, and relationships. A founder who approves every small step has less time for those responsibilities.

Run this audit each quarter as the company grows. The work that depends on you will change, and your decision rules should change with it. Explore the Built to Run guide for more on documentation and delegation.