The quick test

Ask yourself one question: what would happen if you weren't available for the next month?

Not because anything is about to go wrong. It is simply that capability which matters to the business shouldn't live entirely inside one person's head. If the honest answer is "quite a lot would stop", the business depends on you. The useful next question is where the dependency sits, because there are several kinds and each needs a different fix.

Six kinds of owner dependency

1. Strategy

The direction lives mainly in your head. You know where the business is going. Others can only guess, so they wait for you or make choices that don't fit.

2. Decisions

Important decisions default upwards. Managers own outcomes on paper but can't make the decisions those outcomes need without you, so everything queues at your desk.

3. Customer relationships

Key customers or suppliers deal with you, and only you. The relationship belongs to a person, not to the business.

4. Knowledge

Critical knowledge sits with you: how a process really works, why a price is what it is, which supplier to call when something breaks.

5. Sales

Revenue depends on you being in the room. New business slows whenever you are busy with something else.

6. Approval

The organisation waits for your say-so before acting, even when nobody has asked it to. This is the hardest kind to spot, because it lives in habits rather than in any rule.

Most businesses have more than one. Knowing which ones you have matters more than knowing that you have some.

It isn't automatically a problem

Some owners want to stay closely involved in every major commercial decision. That is a legitimate choice, and nothing needs fixing.

The problem is a mismatch. If you say you want the business to run without you, but every significant decision still reaches you, the dependency has become a constraint on the very thing you want. The question isn't "how dependent are we?" It is "does the level of dependency match what I want for the business and for my own role?"

What to do about it

The fix depends on the kind of dependency. A few principles help with all of them.

Start with what must be owned, not with the org chart. Work out which outcomes and decisions need a clear owner, and who that owner should be, before you think about moving boxes. A finding about dependency doesn't automatically mean a restructure. Often it means clarifying who owns what, and leaving the structure alone.

Move authority, not just tasks. Handing someone a job without the decision rights that go with it only creates a new route back to you. If a manager owns margin, they need to be able to approve the discounts that affect it, up to a level you agree in writing.

Don't assume the answer is another senior hire. When the owner is overloaded, the obvious conclusion is to recruit. First check whether work is being duplicated, whether reporting has grown out of proportion, and whether decisions are delayed because nobody else is allowed to make them.

Deal with relationships and knowledge deliberately. Introduce others to key customers well before you need to step back. Write down the knowledge that only you hold, starting with the parts that would hurt most to lose.

Check it from more than one side

Your own view of where the business depends on you is a good starting point, but it is only one view. The people around you often see the dependency differently. They know which decisions they wait for and which customers ask for you by name.

Asking leadership and the team the same question, such as whether critical knowledge and responsibilities are shared widely enough that the business isn't overly dependent on particular people, and comparing the answers, will show you whether they see the same picture you do.