Insights

How can a business reduce dependence on its founder?

Short answer: by moving what lives in the founder’s head into structure the team can use. That means clear owners for outcomes, agreed rules about who decides what, written procedures for repeating work, reporting that brings information to the founder, and a regular rhythm that keeps it all moving. It works best done in that order, and with the team rather than for them.

Why founder dependence happens

It usually isn’t a character flaw. In the early days the founder is the system: they know every customer, approve every expense and fix every problem. That speed is an advantage. As the team grows, the same habits mean every decision queues for one person, the team learns to wait rather than decide, and the founder’s time becomes the limit on growth.

Step 1: Find out what actually waits on you

For two weeks, write down every decision, approval and question that comes to you, and who it came from. Then sort the list into three groups:

  • things only you should decide,
  • things someone else could decide if they knew the rules,
  • things that shouldn’t need a decision at all, because they happen the same way every time.

Most founders find the second and third groups are much bigger than they expected.

Step 2: Give every outcome an owner

Name one person who owns each important outcome, for example on-time delivery, customer complaints, stock levels or collections. “Owns” means they are responsible for the result and are the first person to act when it goes wrong. Shared ownership usually means nobody owns it.

Step 3: Agree decision rights

For the decisions in your second group, agree who can decide what, and within which limits. A simple way to frame it is three levels:

  • Decide: the owner decides and acts.
  • Decide and inform: the owner decides, then tells you.
  • Recommend: the owner brings a recommendation, and you decide.

For example, a store manager might approve refunds up to an agreed amount, approve larger ones and inform you, and bring anything unusual to you with a recommendation. Write the limits down, so nobody has to guess.

Step 4: Document the work that repeats

Take the third group, the work that should happen the same way every time, and write SOPs (standard operating procedures) for it. Start with the processes that cause the most problems or that only one person knows. Keep each SOP short: the steps, who does them, and what “done” looks like. A one-page SOP that people use beats a manual nobody opens.

Step 5: Make information come to you

If you only learn about problems by asking, you’ll keep asking. Agree a short, regular report from each owner, with a few numbers and a few lines on what is on track and what isn’t. The aim is that you hear about issues early, without chasing.

Step 6: Run a weekly operating rhythm

Hold a regular weekly meeting where owners report progress, raise blockers and agree next actions, and where decisions are written down with an owner and a date. This rhythm is what keeps the structure alive. Without it, things drift back to you.

Step 7: Step back, and stay out

The hardest step is the founder’s. When someone brings you a decision they’re allowed to make, send it back. When an owner makes a call you would have made differently but within their limits, let it stand and discuss it later. Every time you take a decision back, the team learns to wait for you again.

Common mistakes

  • Writing processes without the people who do the work, so nobody uses them.
  • Delegating tasks without delegating the decisions that go with them.
  • Buying a new tool before agreeing who owns what.
  • Expecting it to stick without a weekly rhythm to reinforce it.

Want help putting this in place?

Our Business Systems & SOPs service designs and installs this structure with your team. If you’re not sure where to start, an Operations Audit shows what to fix first.