Blog

Most owners do not have an effort problem. They have a dependency problem.

The business has grown, the team is busier, the number of decisions has increased, and there are more customers, more projects and more moving parts. Yet too much of the thinking, deciding, checking, chasing and problem-solving still runs through the owner.

The usual response is to work harder. Add another meeting. Check more closely. Follow up more often. Explain the process again. Stay later. Keep more things in your head.

For a while, that can work.

But if the business needs more of the owner every time it grows, it is not becoming stronger. It is becoming more dependent.

The answer is rarely more effort.

It is a better way for the business to run.

Every business already has a way of operating

When I talk about the way a business runs, I do not mean software.

I mean the practical way the business makes decisions, hands work over, follows up, deals with problems, shares information, keeps people accountable and knows what needs attention.

Every business has some version of this, even if nobody has deliberately designed it.

In a small business, much of it often sits in the owner’s head.

The owner knows which customers need extra attention, what good work looks like, when a project is drifting, which enquiries are worth pursuing, how far someone can negotiate, what should be escalated and what can wait.

That can work well when the team is small and the owner is close to everything.

As the business grows, it becomes a problem.

The same knowledge, judgement and decision-making that once made the business agile starts creating dependency.

The business starts waiting for you

One of the clearest signs is that work slows down when the owner is unavailable.

A manager needs a decision before moving forward. A team member wants approval before replying to a customer. A proposal sits waiting for review. Someone asks a question that has been answered many times before.

None of these things feels particularly significant in isolation.

Together, they tell you something important.

The business has not yet worked out how to move without routing too much through the owner.

This can happen even in businesses with good people. In fact, it often does.

The issue is not always that the team lacks ability. It may be that they lack clarity, authority, information or a reliable way to make decisions without checking first.

That is a design problem.

More meetings will not necessarily solve it

When things feel messy, owners often add more communication.

Another weekly meeting.

Another project call.

Another check-in.

Another reporting requirement.

Sometimes that helps. Often it simply adds activity without removing dependency.

If people are still unclear about what they own, what they can decide and what happens next, more meetings do not fix the underlying issue.

They just create more places to talk about it.

The same applies to documentation.

Writing more processes can be useful, but a folder full of procedures is not automatically a better-run business. If nobody uses them, they are not clear enough, or they do not reflect how the work actually happens, they add little value.

A better way of running the business is not about adding bureaucracy.

It is about making the important things clearer and easier.

Look at where the friction really is

A useful starting point is to notice where work regularly slows down, gets confused or comes back to you.

You might see it in:

• decisions waiting for approval;
• tasks that repeatedly need chasing;
• inconsistent customer experiences;
• sales opportunities with no clear next step;
• handovers that depend on verbal explanation;
• reports that only appear when someone remembers;
• the same questions being asked repeatedly;
• managers escalating issues they should be able to handle;
• work that only runs smoothly when one particular person is available.

These are not just irritations.

They are clues.

They show you where the way the business currently runs is too dependent on memory, goodwill or individual intervention.

The owner often becomes the invisible system

This is where things get uncomfortable.

In many owner-managed businesses, the owner is not simply leading the system.

They are the system.

They remember what matters.

They know who needs chasing.

They join the dots between departments.

They spot when something feels wrong.

They keep the history in their head.

They interpret exceptions.

They make the awkward decisions.

They step in when things wobble.

That can make the business look more organised than it really is, because the owner is constantly filling the gaps.

The danger is that the gaps remain hidden.

A business can appear to have good systems when, in reality, it has a highly capable owner compensating for weak ones.

Start with decisions

One of the best places to improve how the business runs is decision-making.

Ask:

Which decisions still come back to me?

Why do they come back?

What information does the team lack?

What authority have I not given them?

What judgement am I applying that has never been made explicit?

In many cases, the owner has a mental rule that the team does not know.

For example, they may know when a customer problem is serious enough to justify a refund, when a prospect is worth pursuing, when a project is genuinely at risk or when a cost needs additional scrutiny.

The team simply sees the decision.

The owner sees the pattern behind it.

The opportunity is to make more of that pattern visible.

Turn judgement into something usable

This does not mean trying to document every possible scenario.

It means taking recurring decisions and asking whether the thinking behind them can be made clearer.

That may take the form of:

• decision criteria;
• thresholds;
• checklists;
• examples;
• escalation rules;
• simple workflows;
• standard questions;
• agreed review points.

The goal is not to remove human judgement.

It is to stop concentrating all judgement in one person.

That is a very different kind of delegation.

You are not simply handing work over.

You are helping the business think better without you.

Make ownership obvious

Another common weakness is vague accountability.

A task may involve several people, but nobody is truly responsible for the outcome.

The owner notices the gap and steps in.

Again, the business learns that the owner is the final safety net.

A better approach is to make ownership explicit.

Who owns the result?

What does success look like?

What can they decide?

What needs to be escalated?

When will progress be reviewed?

These questions are simple, but they remove a surprising amount of friction.

People work better when they understand not only what they are doing, but also what they are responsible for.

Build useful management rhythms

A well-run business does not depend on constant checking.

It depends on good visibility.

That usually comes from a small number of useful management rhythms.

Perhaps that is a weekly leadership meeting focused on priorities, issues and actions.

Perhaps it is a short sales review.

Perhaps it is a monthly KPI review.

Perhaps it is a project checkpoint.

The exact rhythm matters less than the discipline.

The purpose is to surface the right information before something becomes urgent.

That allows the owner to move from chasing to reviewing.

Those are very different roles.

Capture knowledge before it becomes a bottleneck

Knowledge trapped in one person’s head creates fragility.

That person might be the owner, but it could also be a long-serving manager or technical expert.

If the business repeatedly relies on someone remembering the history, explaining the process or making the same judgement, that knowledge needs to become more accessible.

This does not always require a huge documentation project.

Start with the things that are repeatedly asked, repeatedly explained or repeatedly missed.

Those are usually the areas where knowledge capture has the greatest value.

The aim is not to document everything.

It is to reduce unnecessary dependence.

Where practical AI starts to become useful

This is where AI begins to have a meaningful role.

Not as a shiny add-on.

Not because every process should be automated.

And not because AI can replace good management.

It becomes useful once the business understands what it is trying to improve.

For example, AI can help turn repeated knowledge into accessible guidance. It can summarise information, support handovers, identify patterns, draft responses, prompt follow-up or help people apply agreed decision criteria more consistently.

Agentic AI can go further.

Instead of simply waiting for someone to ask a question, an AI agent can potentially monitor a workflow, notice when something has stalled, gather relevant information, prompt the right person or take a defined action within agreed boundaries.

That can be powerful.

But only when the business has first clarified the process.

If the workflow is unclear, automating it simply creates a faster version of the confusion.

Do not start with the tool

This is one of the most important principles.

If you start with the question:

“Where can we use AI?”

you may end up looking for problems to fit the technology.

A stronger question is:

“Where does the business still rely too heavily on people remembering, chasing, deciding or repeating the same work?”

Then ask whether clearer systems, better management or practical AI could remove some of that dependence.

That keeps the focus where it should be.

On improving the business.

Not collecting tools.

A simple way to review how your business runs

Choose one area of the business that regularly consumes too much management attention.

It might be sales, customer service, recruitment, project delivery, reporting or finance.

Then ask:

Where does work slow down?

What repeatedly comes back to the owner?

Where are people unclear about what they can decide?

What knowledge only exists in someone’s head?

What gets chased manually?

What problems appear again and again?

What information arrives too late?

Once you can see the friction, you can redesign it.

Some of the solution may be process.

Some may be management.

Some may be clearer accountability.

Some may be automation or AI.

The important thing is to solve the right problem.

The real goal is not efficiency

Efficiency matters.

But it is not the main outcome.

The bigger goal is capacity.

Can the business handle more customers, more work and more complexity without creating the same increase in pressure on the owner?

If not, growth eventually becomes self-defeating.

Every new customer adds more decisions.

Every new employee adds more questions.

Every new service adds more complexity.

Every new opportunity adds more coordination.

The owner becomes busier precisely because the business is doing well.

That is not sustainable growth.

Build a business that works better without you in the middle

The goal is not to remove the owner from the business.

It is to change the level at which the owner contributes.

You should not need to be the person who remembers everything, checks everything, chases everything and makes every awkward decision.

Your value should increasingly come from direction, judgement, leadership and the design of the business itself.

That is the shift.

From being the person who keeps everything moving to building a business that knows how to keep moving.

And increasingly, that will involve a combination of better management, better systems and practical AI used in the right places.

At Summit SCALE, this is where my work is evolving: helping owners get out of the middle of everything by improving the way the business runs, and using practical Agentic AI where it can genuinely reduce dependency and increase operating capacity.

If your business still depends on you to notice, chase, decide or fix too much, the next step is not another productivity hack.

It is to look at the way the business runs underneath all that effort.