If every quote, every customer issue, and every small decision needs your sign-off, your days fill up with work while the company spends its time waiting on you.
Early on, a founder in the detail is an advantage. You are closest to the product and the customers, and you can settle a lot quickly. But as the work grows, decisions pile up faster than one person can handle, and your judgement turns into a door everyone has to pass through.
Why does the team bring everything back to you?
Sometimes it is a lack of experience. Often it is the absence of clear limits. Someone who does not know what they are allowed to approve, or what they will be judged on, will ask for permission by default. And if you reverse their calls without explaining why, they learn that waiting is safer than taking initiative.
So delegation starts by making the decision rules explicit: what outcome do we want, what are the limits, and when should this be escalated?
Delegate the decision, and its ownership
Imagine a salesperson who comes back to you on every discount request. Telling them to use their judgement does not show them how to balance closing the deal against protecting margin.
Instead, define what they can offer, the conditions attached, and the cases that still need approval. The exception might depend on contract length, payment terms, or service volume. What matters is that the limits fit your economics and that the person understands the reasoning.
They also need to know where the decision is recorded, who reviews it, and what happens if something goes wrong. That is what makes delegation something you can learn from and improve.
Start with the decisions that repeat
For one week, log the decisions that came back to you. Sort them into routine calls you can systemise, calls that need training, and the genuinely strategic ones that deserve your involvement.
Pick one recurring process and define:
- A clear owner of the outcome, not just of carrying out the task.
- A simple standard for quality, time, and cost.
- Written authority and limits, with examples.
- Specific escalation cases, and a time to review the decisions made.
Review the results without re-making every call yourself. If something goes wrong, check whether the rule was clear, the information was available, and the training was enough, before pulling the authority back entirely.
You may spend longer explaining the first decision, but you are building a capability that needs you less on the ones that follow. Growth means spending your time on direction, priorities, and building the team, while still being able to follow execution without becoming a permanent waiting point.