A sustainable business should not need you to be its emergency system.

What to know

Consider a hypothetical two-person repair shop where every refund needs the owner’s approval. On a busy afternoon, the owner is away from the phone, so a routine customer question waits, an employee interrupts later, and the owner inherits both the decision and the follow-up. This is an invented example, not a report about a real business. Its useful question is not whether the owner should approve every refund; it is which cases genuinely need that judgment. The owner could write a simple rule for low-value refunds, name the records staff should check, and set a clear limit beyond which they must ask. Then test the rule for two weeks, note exceptions and customer outcomes, and revise it before widening authority. This makes delegation a reversible trial, not an all-or-nothing handoff.

Put it into practice

Find the recurring rescue

For one week, note each time someone needs you to unblock ordinary work. Record what was missing, who was waiting, and whether the delay affected a customer or deadline. Resist fixing every problem as it appears; first look for repeats.

At week’s end, group similar interruptions. Questions about the latest customer quote may point to scattered information; repeated requests for approval may point to an unclear decision limit. Choose the pattern that creates the most avoidable waiting, not simply the one that feels most urgent.

Treat the pattern as a clue, not a verdict on your team. If a process or answer is hard to find, people may be waiting because it is unclear what to do—not because they lack judgment. Some unusual or high-consequence cases should still reach you.

Make one decision easier

Turn the recurring interruption into a short instruction someone can use without guessing. State what triggers the process, what steps to take, what to record, and when to ask for help. Keep it where the person doing the work can find it.

Pair responsibility with the information and authority it requires. Be specific about what the person may decide and what needs your approval. A rule that grants responsibility without access to relevant records, or leaves the approval boundary vague, may simply move the interruption.

Give authority with context

Talk through a real example together, then let the person handle a similar case while you observe. Notice whether they can find the necessary information and explain their decision. If they cannot, improve the instructions or access before deciding they are not ready.

Start with work that is frequent, teachable, and relatively easy to reverse. A routine appointment change may be a better first handoff than an unusual complaint involving a major contract. The aim is not to remove your judgment from every decision; it is to reserve it for cases where it adds something important.

Reduce avoidable choices

Some interruptions come from unclear next steps rather than difficult decisions. If customers repeatedly ask how to book or prepare, make that information easier to find. If your team cannot tell which document is current, agree on one shared location and a naming habit. A new tool might help, but adopting software before agreeing on a process can create another place to check.

After a change, look beyond speed. Fewer repeat questions and less waiting may be encouraging, but also check whether records remain accurate, answers consistent, and errors or rework manageable. Ask the person doing the work what still feels awkward or risky.

Expand only when the boundary is clear

Use what you learn from one handoff to decide whether another process is ready for the same treatment; do not assume one successful change means everything should be delegated. Keep decisions that depend on your distinct expertise, relationships, or financial responsibility with you, and make the route for raising them clear. The aim is not a business that never needs its owner. It is ordinary work with a reliable next step and unusual work reaching you with enough context to decide well.