How to reduce founder dependency: a 90-day plan
Delegation fails when the task moves and the standard stays in the founder's head. The work is writing down the judgement, not handing over the to-do list.
Founder dependency is what you have when the standard behind a decision exists only in the founder's head, so nothing reaches the right quality without them in the room. You reduce it by writing that standard down, transferring named decisions with an explicit boundary, and building managers capable of holding the bar once it is theirs. Ninety days is enough to move the first decision type out of the founder's hands and see whether it holds.
It is usually described as a delegation problem, which makes it sound like a personal failing. It is more accurate to describe it as an information problem. The founder holds a standard that has never been written down, so anyone else making the decision is guessing at criteria they cannot see.
This is why the usual advice does not work. "Let go more" produces worse decisions, the founder intervenes to correct them, and the organisation learns that delegation is provisional. The loop tightens.
The 90-day plan
One decision type, moved properly, in three stages. The order matters more than the speed: nothing transfers before the standard behind it is written, and nothing is considered transferred until a decision inside the boundary has survived without the founder reversing it.
| Weeks | What moves out of the founder's hands | What has to exist first | The sign it worked |
|---|---|---|---|
| 1 to 2 | Nothing yet. The founder writes down the standard behind the decision type that consumes most of their week. | Ten recent decisions — five they would defend, five they overruled — with the reasoning behind each written out. | Two managers can predict the founder's call on a live case before hearing it. |
| 3 to 6 | The first decision type, transferred to a named role rather than to the team in general. | A written boundary: what is decided alone, what is decided after consulting whom, what is only recommended. | Decisions of that type stop arriving in the founder's inbox, and are not being made worse elsewhere. |
| 7 to 12 | The second decision type, plus the client or partner relationships attached to it. | A manager who has been through one cycle of holding the standard, and a joint handover plan for the relationships. | Something inside the boundary is decided differently from how the founder would have decided it, and it stands. |
What founder dependency actually concentrates
It is worth being precise about what sits with the founder, because the four things have different solutions.
| What is concentrated | How it shows up | What transfers it |
|---|---|---|
| The standard | Work is redone after the founder sees it | Written criteria and worked examples |
| The decision right | Things wait for approval that nobody formally requires | Explicit decision rights with named boundaries |
| The context | People cannot weigh a trade-off because they do not know the strategy behind it | Stated priorities and the reasoning behind them |
| The relationships | Key clients, partners or candidates only respond to the founder | Deliberate introduction and joint handling over a defined period |
Most founders try to solve all four by attending fewer meetings. Only the second responds to that.
Write down the standard first
This is the highest-leverage document a founder-led company can produce, and almost none of them have it. It answers, for the two or three decisions that matter most: what does good look like, what trade-offs are acceptable, and what must never be compromised.
A workable method: take five recent decisions the founder made and would defend, and five they overruled. For each, write the reasoning — not the outcome, the reasoning. The pattern across ten cases is the standard, and it is usually shorter and more consistent than the founder expects.
Transfer decisions, not tasks
Task delegation moves work and keeps the judgement. Decision transfer moves both, which is the only version that reduces load. It requires four things to be stated:
- Which decision is transferring, specifically.
- The boundary: what this person can decide alone, and at what threshold it comes back.
- What "consulted" means, if anyone must be consulted, and by when.
- What the founder will do when they disagree with a decision inside the boundary.
The fourth is the one that determines whether any of this holds. If the founder reverses decisions inside the boundary, the boundary does not exist, and everyone learns that faster than they learn any framework. The workable position is to accept outcomes inside the boundary, and to change the boundary explicitly if it turns out to be wrong.
Build the managers who will hold it
Decision rights transfer to roles, and roles are held by people who need to be capable of exercising them. In many founder-led companies the management layer was promoted for individual excellence and never told what management here involves. Where the same decision keeps returning to the founder no matter who holds it, the problem is usually the organisational structure rather than the person.
The minimum is a written statement of what a manager is accountable for, the routines that carry it — one-to-ones, team meetings, goal reviews — and one training cycle on the conversations they will have to hold. This is the substance of leadership and management work, and it is what makes the transferred decisions stick.
Sequence it over quarters, not weeks
Beyond the first ninety days, a realistic sequence for a company of fifty to a hundred and fifty people:
- Quarter one. Write the standard for the two decision types that consume the most founder time. Define role ownership for the layer below the founder.
- Quarter two. Transfer the first decision type with explicit boundaries. Establish manager expectations and the management routines.
- Quarter three. Transfer the second. Run the first performance cycle where managers, not the founder, hold the standard.
- Quarter four. Review what came back and why. Adjust the boundaries rather than reclaiming the decisions.
The measure of progress is not how many meetings the founder skips. It is how many decisions are made correctly without them and never mentioned.
What good looks like eighteen months in
The founder is still the highest-judgement person in the company. That does not change and does not need to. What changes is that their judgement is available as written criteria rather than as personal availability, and the organisation can reach the same conclusion without them in the room.
There is also a commercial dimension worth stating plainly. Founder dependency is a valuation issue. Any acquirer or investor conducting diligence will test how much of the company's decision quality is transferable, and a company that can show written standards, defined decision rights and a functioning management layer answers that question considerably better than one relying on the founder being in every room.
This is the work we do with Founder-led companies, and it is usually the first thing we look at.
Co-founder — Organisation & Operations
Francisco Campos
Built growing companies from the inside: first employee to COO at Onport through its acquisition by Farfetch.
More from Francisco