The decisions queue outside your door. The biggest clients still want you on the call. A fortnight’s holiday means a fortnight of things waiting for you to get back. You’ve hired good people and invested in tools, and your diary looks much the same as it did two years ago. That rarely means you hired badly. More often, the business has outgrown the way it was built.
This guide covers the whole picture: what founder dependency is, how to spot it, why it happens, what it costs, how to measure it and how to reduce it. Where one cause deserves more depth, it links to an insight that covers it properly.
What is founder dependency?
Founder dependency is the state where the founder is the connecting piece for too much of the business. Decisions, client relationships, quality standards and know-how all route through one person, so that person’s attention becomes the limit on everything else.
It usually shows up in four places:
- Decisions. Calls that others could make still wait for your approval.
- Relationships. Key clients, partners or deals depend on you personally.
- Quality. Work is only “right” when you’ve checked it.
- Knowledge. The reasoning behind how things are done lives in your head.
In the early days this is often how a business wins. You’re fast, you know every client and you can make a call in seconds. The trouble starts when the business grows past the point where one person can hold it together, typically somewhere between 15 and 75 people. Growth that should be adding capacity starts adding pressure instead, and most of that pressure lands on you.
What are the signs that your business depends on you too much?
The signs are usually familiar long before anyone names them. Look for these:
- Your team keeps bringing you decisions they could make themselves.
- Leadership meetings are mostly updates for your benefit.
- Decisions get quietly reopened once you hear about them.
- People wait for your view before committing to anything.
- The biggest clients only really trust you.
- Work slips, or stalls entirely, when you’re away.
- You’re the only person who knows why things are done the way they are.
- You’ve hired senior people and your diary is no lighter.
One of these on its own is normal. Several together is a pattern, and it’s the pattern that matters.
Why does founder dependency happen?
Founder dependency happens because the operating system never caught up with the business. The way your people, practices and technology work together was set up – often without anyone setting it up deliberately – for a much smaller company. That’s why Mallard treats it as a business operating system problem rather than a people, tools or effort problem.
Four causes come up again and again. They tend to reinforce each other, so most founder-dependent businesses have more than one.
Decision rights were never made explicit
Teams are often told they’re trusted to decide. Far fewer are told which decisions. When nobody knows where their authority starts and stops, a sensible person checks with the founder first, and the decisions drift upwards.
Rodney Evans of The Ready makes a similar point on their podcast: what leaders call a lack of accountability usually turns out to be a lack of clarity about roles, authority and information. The practical answer is to hand over decisions with clear edges, which is what delegation that hands over decisions rather than permission covers in detail.
Senior hires got a title but not authority
A new head of operations or finance lead gets a warm welcome, a handover of tasks and a seat in the leadership meeting. What they rarely get is a clear list of the calls that are now theirs. Add a meeting that exists to update the founder, and you have a leadership team in name only: capable direct reports who still look to you.
People aren’t yet equipped to decide
When someone hesitates or hands a problem back, founders often read it as a lack of ownership. Usually it’s a lack of competence. People take ownership of things they feel able to handle. You can solve those problems because you’ve seen hundreds like them, and your team hasn’t built that pattern recognition yet. Build the competence and accountability follows.
The founder’s own reflexes
The last cause sits closest to home. Founders tend to have the answer ready, give it before asking, reply faster than anyone else and step in when things wobble. Each of those habits is reasonable on its own. Together they teach the team that the quickest route to a decision is you. Why every decision still comes to you looks at those reflexes and what to do differently.
Knowing about the habit isn’t the same as changing it. Simon Wakeman, Mallard’s Principal Consultant, tells a story against himself here. A decade or so ago, as MD of a digital agency, he could have given an accurate account of his own worst habits. He knew he was the bottleneck on decisions and would have said so in a leadership meeting, with a self-deprecating joke attached. Saying it out loud didn’t change anything. His team could see that, and a team that sees a founder name a problem and then carry on learns to stop raising it.
What does founder dependency cost?
Founder dependency costs you speed, people and options – usually in that order.
Speed. Every decision that waits for you adds a delay. Across a business of 30 or 40 people, those delays compound into slower delivery, slower sales and missed opportunities.
People. Capable people want to own things. If they can’t, the best of them leave and the rest stop trying. The few “heroes” who keep stepping in to save the day burn out. Meanwhile you spend your evenings on work that should sit several levels below you.
Options. A business that depends on one person is harder to grow, harder to step back from and harder to sell. Holidays become risky. Illness becomes a crisis. And the strategic thinking only you can do never gets done, because you’re too busy holding everything else together.
There’s a quieter cost too. Founders who are pulled into everything tend to make worse decisions, simply because they’re making too many of them, too quickly, with too little context.
How do you measure founder dependency?
You measure founder dependency by looking at where decisions, relationships and knowledge actually sit, rather than where the org chart says they sit. Three simple methods work well together.
Take the bus test. Ask yourself what would happen if you were suddenly unavailable for a month. Could someone close your next deal? Keep your biggest client happy? Make a pricing call? Mallard’s bus test turns this into ten questions across sales, clients, decisions, delivery and knowledge, each scored 0–2, so you can see roughly where the business leans on you.
Run a decision audit. For two weeks, write down every decision you make. Next to each one, note who should have made it. The list is usually longer than founders expect, and a good share of it turns out to be habit rather than necessity.
Ask the team. Have your leadership team score the bus test independently, then compare answers. If their picture differs sharply from yours, the problem is wider than it looks from your chair, and quick fixes are unlikely to hold.
The aim isn’t a perfect number. It’s a shared, honest picture of where the dependency sits, so you can choose what to fix first.
How do you reduce founder dependency, step by step?
You reduce founder dependency by moving decisions, building competence and setting a rhythm that holds it all in place. It’s a process rather than a project, and it works best roughly in this order.
1. Decide what you’re keeping
Start with your own role. Which decisions genuinely need you – direction, the biggest bets, the few calls that are hard to undo? Write them down. Everything else is a candidate to move.
2. Make decision rights explicit
For each area, agree which decisions the owner can make alone, which they consult on and which stay with you. “You own client delivery” is a title. “You can change a project’s scope, timeline and team within the agreed budget, and anything that changes the price comes to me” is a decision right.
3. Start with reversible decisions
Hand over the decisions that are easy to undo first. If they go wrong, the cost is small and the learning is real. Widen the boundaries as confidence grows on both sides.
4. Build competence on purpose
Explain how you weigh decisions up, debrief them together and give people problems a little beyond what they’ve handled before. Write down why decisions were made, not just what was decided, so the context lives somewhere other than your head.
5. Turn the leadership team into a team
Give senior people real authority from day one. Run the leadership meeting for decisions rather than updates, and expect leaders to sort cross-team issues with each other first.
6. Change your own reflexes
Ask before you answer, let decisions stand once they’re made and resist rescuing. Every reopened decision tells people their authority was never real.
7. Set a boring rhythm
Accountability runs on rhythm. Use the same cadence of check-ins whether things are going well or badly, so a conversation never feels like an intervention. Ask forward-looking questions, such as “what could get in the way, and what are you doing about it?”, rather than “did you hit it?”.
8. Recalibrate as you grow
What works at 20 people won’t work at 50. Review the boundaries every few months, widen them where people are ready and tighten them where something isn’t working. Letting go is never finished.
Where do you start?
Start by finding out where your dependency is concentrated, so you work on the right thing first. An afternoon is enough for this:
- Score the bus test yourself. Be honest rather than generous. A 1 is a 1.
- Ask two colleagues to score it independently. Don’t show them your answers first. Note the three questions where your scores differ most.
- Find your cluster. Look at which of the four places – decisions, relationships, quality or knowledge – your lowest scores sit in. That’s where the dependency is heaviest.
- Write your keep list. The handful of decisions that genuinely need you, on one page.
- Choose one area for the next quarter. One, not four. Pick the cluster that costs you most and leave the rest for now.
When should you get outside help?
Get outside help when you’ve tried to let go more than once and it keeps sliding back. It also helps when the problem looks different depending on who you ask, or when you can’t see the operating system clearly because you’re standing inside it. Choose help that plans its own exit, or the interim can become the dependency.
That’s often the point where a structured diagnosis saves months of guesswork. Mallard’s Find diagnostic takes 14 days. It looks at 262 operational data points across your people, practices and technology, scores 12 operational capabilities and ends with a prioritised roadmap, so you know where the dependency sits and what to fix first. From there, an Improve sprint puts a senior Mallard operator inside the business alongside your team for three months to fix the biggest bottleneck end to end.
If you’re not sure you need that yet, the free 30 minute founder review call is the simplest place to start. If Mallard doesn’t think you need to go further, you’ll hear that too.
Contact us