Founder dependency

Delegation isn’t asking permission. It’s handing over decisions.

Delegating a task hands over the work but keeps the decision with you. Delegating authority hands over the decision itself, at an agreed level and within agreed edges, so the person doesn’t need to ask you at all – and that’s the only kind of delegation that reduces founder dependency.

By Simon Wakeman, Principal Consultant & Fractional COO
· 5 minute read

Take any approval that crossed your desk this week. A discount for a renewing client, a freelancer for a busy month, a change to a project plan. Someone else did the work, and you made the call. Repeat that across a month and you have a business where plenty has been handed over and very little has been decided by anyone but you.

The causes of that are covered in the guide to founder dependency. This piece is about the mechanics: how to hand a decision over so it actually stays handed over.

What’s the difference between delegating a task and delegating authority?

Delegating a task means someone else does the doing. You still decide what good looks like, approve the result and make the call if anything changes. Delegating authority means the decision itself is theirs.

The test is simple. When something unexpected happens, who does the person turn to? If it’s you, you’ve delegated a task. If they deal with it, within limits you both understand, you’ve delegated authority.

Task delegation has its place. It’s how you train people and how you hand over work that genuinely needs your judgement. The problem comes when it’s the only kind you do.

Why isn’t delegation a simple yes or no?

Because most decisions sit somewhere between “I decide” and “you decide”, and that in-between is where the confusion lives.

A useful way to make it visible is the seven levels of delegation from Management 3.0:

  1. Tell. You decide and explain.
  2. Sell. You decide and try to win them over.
  3. Consult. You ask for input, then decide.
  4. Agree. You decide together.
  5. Advise. They decide, after hearing your view.
  6. Inquire. They decide and tell you afterwards.
  7. Delegate. They decide and you don’t need to hear about it.

The point isn’t to push everything to level seven. A pricing exception might sensibly sit at Advise for a new sales lead and move to Inquire after six months. Hiring for their own team might start at Agree. What matters is that both of you know which level applies, because most frustration in delegation comes from one person assuming Inquire while the other assumes Consult.

What is a delegation board?

A delegation board puts those levels on one page. Recurring decisions run down the side, the seven levels across the top, and a marker shows the agreed level for each decision and each person. Management 3.0 suggests building it together, often by having each person secretly pick a level for a decision and then discussing the differences.

The board itself is less valuable than the conversation it forces. Founders are often surprised by how far apart their assumptions are from their team’s. A board that sits in a folder becomes an artefact. Put it somewhere everyone can see, and review it monthly: what’s been decided, how it went and which markers should move.

How do you define the edges of a decision?

A level tells someone how much of the decision is theirs. The edges tell them where it stops. Simon Wakeman’s phrase for what you’re aiming at is “clear freedom within defined constraints”, and the constraints need to be specific enough to act on. For each decision you hand over, agree four things:

  • The owner. One named person, not a function or a committee.
  • The limits. Budget, brand, legal, anything that affects another team, stated plainly.
  • What good looks like. An outcome specific enough that you won’t argue later about whether it was hit.
  • When it comes back to you. The specific triggers – a cost over a set amount, a client threatening to leave – that mean they should escalate.

“You run the account team” is a job description. “You can agree discounts up to 10% on renewals and move deadlines by up to a fortnight. Anything that puts the contract at risk comes to me first” is a decision with edges. The number is illustrative; yours will differ. The specificity is what matters.

How do you hand a decision over well?

Treat the handover as a short piece of work, not a sentence in a one-to-one.

Walk through how you’ve made it before. Show what you look at, what you weigh up and what would change your mind. Simon’s phrase for this is “showing your workings”, like a maths exam at school.

Make the first few together. Sit alongside for the first two or three, then step back. Agree the date you’ll stop.

Tell everyone else. The people affected need to know who now decides, or they’ll keep coming to you.

Start with what can be undone. Simon’s line in Build is that “a decision you can learn from beats a delay you can only regret”. The bulk of everyday decisions are reversible, and they’re the right place to start.

Review it, then move the marker. After a month, look at what was decided and how it went. If it’s working, move the level up. If it isn’t, tighten an edge rather than taking the whole decision back.

What if I don’t like the decision they make?

Ask yourself one question before you step in: is this actually wrong, or just different?

If it’s outside the agreed limits or genuinely risky, say so and use it to sharpen the edges. If it’s inside them and simply not what you’d have done, leave it. Overriding a decision you delegated tells everyone the delegation wasn’t real.

Talk about it afterwards instead. Ask how they reached the call, share how you’d have approached it and agree what you’ll both do next time. That’s how you earn the right to move the next decision up a level.

A delegation exercise for the next fortnight

  1. List your recurring decisions. Twenty is plenty. Only the ones that come up at least monthly.
  2. Build a rough board. For each decision, mark the level it sits at today and the level you’d like it at in six months.
  3. Run the conversation. Ask the likely owner to mark their own view of the current level before you show yours. Talk through the gaps.
  4. Write the edges for three. Owner, limits, what good looks like and when it comes back to you, on one page each.
  5. Diary the review. A 30 minute slot in four weeks to look at what was decided and move the markers.

If the people you’re delegating to are senior hires who still look to you, read the leadership team in name only alongside this.

Getting help making it stick

Defining decision rights sounds simple on paper. Making them hold is harder, because it means changing habits – yours included – in the middle of running the business.

That’s the kind of work Mallard’s Improve sprints are built for. A senior Mallard operator works inside your business for three months, alongside your team, to fix the biggest bottleneck end to end, with success measures agreed up front. When the bottleneck is decisions stuck with the founder, that means setting clear decision rights and putting in the rhythm that keeps them working after the sprint ends.

Some commonly asked questions from founders…

What’s the difference between delegating a task and delegating authority?

Delegating a task means someone else does the work while the founder keeps the decision. Delegating authority means the decision itself moves to them, within agreed limits. Only the second takes the founder out of the loop, because the person no longer needs sign-off to act.

What are the levels of delegation?

One model, from Management 3.0, sets out seven levels, from Tell, where the leader decides and explains, through Sell, Consult, Agree, Advise and Inquire, to Delegate, where the decision is entirely the other person’s. Agreeing the level for each recurring decision makes expectations clear for everyone.

What is a delegation board?

A delegation board is a simple grid with recurring decisions down one side and levels of delegation across the top, with a marker showing the agreed level for each. Management 3.0 popularised it. Keeping it visible means anyone can check who decides what without asking.

How do I decide which decisions to hand over first?

Start with decisions that are frequent, reversible and low in risk. They give people plenty of practice, and mistakes are cheap to fix. Keep the irreversible, high-stakes calls until people have built a track record on smaller ones.

What should I do when someone makes a decision I wouldn’t have made?

First ask whether it’s actually wrong or just different. If it’s within the agreed limits and simply not your choice, leave it. Overriding it teaches the team that the authority was never really theirs, and they’ll start asking permission again.

How can Mallard help a founder delegate real authority?

Mallard’s Improve sprints put a senior operator inside the business for three months, alongside your team, to fix the biggest bottleneck end to end. Where decisions are stuck with the founder, that usually means defining decision rights and building the rhythm that makes them stick.

Stop being a bottleneck in your own business

Book your free 30 minute
founder review call