The Business Should Survive Your Vacation

There is a simple way to see how dependent an operation has become on one person: step away for a while and see what still needs your attention to keep moving.

Usually, it is not the major strategic decisions. It is the small ones. A refund that needs approval. A pricing exception. A customer issue nobody wants to close without checking first. One by one, they look harmless. Together, they show you where the operation still depends on a person rather than a system.

A team can be perfectly capable and still escalate constantly. That does not automatically mean they lack ownership or initiative. More often, the business simply never defined the boundaries.

People may know what they are responsible for without knowing what they are actually allowed to decide.

The Fix: Separate recurring decisions into three clear buckets: Decide, Escalate, Inform.

What can be handled without approval? What genuinely needs your judgment? What should simply be reported?

That distinction can remove a surprising amount of unnecessary escalation without taking control away from leadership.

Every business has exceptions. The problem is when the same one keeps appearing.

At that point, it is no longer an exception. It is a pattern the business has not designed for yet.

The Fix: Stop asking, “How do we solve this one?” and ask, “Why does this keep happening, and what should the process do next time?”

Maybe the answer is a clearer rule. Maybe it is a different approval point. Maybe it is a new step in the workflow.

The important part is that you stop rediscovering the same solution.

Sometimes the dependency is not the founder. It is the person who knows how everything actually gets done.

They know the workaround. They know where to look. They know who to call when the normal path does not work.

Everything looks fine until they are unavailable.

That is not a people problem. It is a dependency risk.

The Fix: Do not document everything. Document the parts that create a bottleneck when one person is unavailable.

For critical workflows, another person should be able to understand what comes in, what needs to happen, what “done” looks like, and what happens when the normal path breaks.

Before your next time off, make one list:
What still needs me?

Then look at each item and ask:
Does this actually require my judgment, or has the business simply never decided where it belongs?

That question usually tells you more than the vacation itself.

A business should not need you less. It should need you differently.