Skip to content
Stories & Systems
Back to insights

How to stop being the bottleneck

Updated
Owner DependencyOperationsLeadership

You stop being the bottleneck when the organization can move without every exception, approval, and question routing through you. That is not a motivation problem. It is a design problem: decision rights, coverage, and systems.

The short answer

  1. Find what breaks when you are unavailable.
  2. Separate decisions you must own from decisions a rule can own.
  3. Document coverage for the high-consequence paths.
  4. Automate the repetitive residue.
  5. Protect a cadence so the bottleneck does not quietly rebuild.

Signs you are the system

  • Vacations are not rest; they are remote work with worse Wi-Fi
  • Staff wait on your reply before finishing ordinary work
  • Customers ask for you by name for issues others could solve
  • Priorities reshuffle whenever you change your mind midweek
  • Tribal knowledge lives in your texts, not in a shared place

If that list stings, you are not alone. The useful question is which recurring decisions could move safely without your involvement.

Run an Absence Audit

Before you buy another tool, run an Absence Audit. Pick a realistic window — one or two weeks — and list what only you can do. Rank by frequency and consequence. The top of that list is your redesign backlog, not your badge of honor.

Pay down Decision Debt

Bottlenecks are often piles of unmade or over-concentrated choices. Decision Debt names that drag. Clear the expensive waiting decisions, then write simple decision rights: who decides, with what inputs, by when, and what escalates to you.

Why does every decision come back to me?

A team can receive responsibility without receiving the information or authority to act. Asking someone to “handle operations” leaves several questions unanswered: what can they change, which commitments must they protect, and what happens if you disagree with a reasonable decision?

Start with one recurring decision. Talk through an actual example with the person you want to own it. Agree on the expected result, the information they need, the limits of their authority, and the conditions that require escalation.

For an illustrative scheduling example, your right-hand person might move appointments within an agreed window, inform you when a change affects another crew, and escalate before changing a promised completion date. Those boundaries must come from your operation; they are not universal rules.

Write the agreement somewhere both of you can find. If the team still needs a private text from you to discover the current schedule or customer promise, the handoff is incomplete.

Develop judgment through a small handoff

Choose a bounded responsibility before handing over the whole day-to-day operation. Ask your right-hand person to recommend a decision and explain their reasoning. Discuss the trade-offs, then agree on what they can decide independently next time.

After a decision, review the reasoning as well as the result. A reasonable decision can have a disappointing outcome. If every disappointing outcome results in authority being taken away, people will learn to seek approval again.

Keep genuine safety, employment, financial, and customer commitments within the appropriate approval boundaries. Developing judgment includes knowing when to stop and ask.

Watch whether the owner becomes the fallback again

For a short observation period, log the questions that come back to you. Record the decision, why it returned, and what was missing: information, authority, access, skill, or confidence.

Review that record together. A written procedure may fix an information gap. A permission change may fix an access gap. Practice may fix a skill gap. Another application will not automatically resolve any of those.

Measure recurring interruptions and decisions completed within the agreed boundaries. Use what you observe to choose the next responsibility to hand over. For a practical way to check coverage, read Can my business run while I’m away?.

Automate after the path is clear

Automation multiplies whatever you point it at. Once a path is stable and rule-based, automate it. If you are choosing a first target, use What should I automate first?. If the process is still mushy, fix that first with Is your process ready to automate?.

A practical 30-day sequence

Week 1 — See it. Complete an Absence Audit. Note the top five dependencies.

Week 2 — Decide it. Hold a decision clinic on the stuck approvals and write rights for the recurring ones.

Week 3 — Cover it. Create checklists, shared inboxes, or deputy ownership for the two highest-consequence paths.

Week 4 — Multiply it. Automate one high-frequency, low-judgment task and measure time returned.

Your business should keep moving without you holding it together.

What Stories & Systems does here

David Runnels and Stories & Systems help owner-led organizations redesign the systems behind the work — including San Antonio teams wrestling with growth chaos. The Friction Assessment is the fastest way to see where the operation still leans on you.