The founder is still approving everything. That is the problem.

How the ceiling forms

Early on, the owner knows every customer, every price, every supplier and most of the staff by name. Decisions are fast because context lives in one head. That is a genuine advantage, and it is why many businesses reach their first stage of success.

Then the business doubles. The same person now sits in the path of purchase approvals, discount requests, hiring calls, customer escalations and the occasional bank conversation. Nothing has gone wrong. There is simply more of everything, and only one route through.

The symptoms are familiar. Managers wait outside the office instead of deciding. Straightforward matters take a week because the founder was travelling. Good people become order takers because their judgement is never actually used. And the owner, who started the business partly for independence, cannot take two uninterrupted weeks away.

Delegation is not the same as letting go

Most advice on this subject stops at the instruction to delegate more, which is not useful on its own. Delegation fails for identifiable reasons, and each of them can be addressed.

The person does not have the information. You cannot ask a manager to approve a credit limit if they cannot see the customer's payment history. Decision rights without data produce either paralysis or bad calls, and both send the decision back to the founder.

The boundaries were never set. Telling someone to handle purchasing is not delegation. Telling them they can commit up to a stated amount with a named supplier list, and that anything beyond that comes to you, is delegation. Clear limits make people braver, not more restricted.

There is no forum to review the decision. If the only feedback is a correction after something goes wrong, people stop deciding. A short weekly review where decisions are discussed openly turns delegation into a training process rather than a gamble.

The founder keeps reversing. If a manager's decision is overturned in front of their team twice, it will not be made a third time. Trust, once withdrawn publicly, is expensive to rebuild.

A practical sequence

Start by writing down every decision that came to you last month. Most owners are surprised by the list, and by how many items on it are routine.

Sort them into three groups. Decisions that must stay with you, such as significant capital commitments, senior hires and the direction of the business. Decisions that could move immediately with a limit attached. Decisions that could move once someone has the right information or a little coaching.

Then move one decision at a time. Name the owner, set the boundary, agree what information they need and when the two of you will review how it is going. Give it a quarter before judging it. Moving ten decisions at once tends to produce ten new problems arriving at your desk simultaneously.

The management rhythm does the heavy lifting

Founder dependency is often described as a personality problem. More often it is a structural one. Where there is no reliable rhythm of review, the founder becomes the rhythm, because they are the only mechanism that notices when something is off.

A workable rhythm is unglamorous. A short weekly operating meeting with the same handful of numbers. A monthly review of performance against what was agreed. A quarterly conversation about priorities. Each with a named owner per item and a record of what was decided.

Once that exists, the founder can step back from daily approvals without stepping away from control, because the business now has another way of seeing itself.

A closing thought

The test is not whether the owner can leave the business. It is whether, while they are away, decisions still get made at roughly the same quality and speed. Building that takes longer than a reorganisation and matters more than one.