What Should a Business Owner Stop Doing as the Company Grows?
As your business grows, you should progressively stop doing work simply because you are capable of doing it.
That includes:
Routine administration.
Standard approvals.
Day-to-day scheduling.
Being the first person employees ask for answers.
Personally checking every piece of work.
Handling every customer relationship.
Solving problems that belong to managers.
Doing technical work somebody else can perform adequately.
Remembering everybody's commitments.
Acting as the link between departments.
And making decisions that could safely be made lower down the organisation.
That does not mean the owner eventually does nothing.
Quite the opposite.
Your job should become more concentrated on the things that genuinely require the owner.
Direction.
Capital.
Major commercial decisions.
Leadership.
Management capability.
Key people.
Risk.
Culture.
Strategic relationships.
The future of the company.
The problem is that businesses grow faster than owners change their jobs.
You keep doing the work that made you successful at £500,000 turnover while trying to run a £5 million company around it.
Eventually your capability becomes the constraint.
Growth requires subtraction, not just addition
When owners think about growth, they normally think about what needs adding.
More customers.
More staff.
More marketing.
More systems.
More managers.
More space.
More equipment.
But every stage of business growth also requires subtraction.
What should you no longer do?
This question gets considerably less attention.
You cannot continually add higher-level responsibilities without releasing lower-level ones.
There are still only so many hours.
So if the owner keeps:
Quoting.
Checking.
Approving.
Scheduling.
Fixing.
Selling.
Managing.
Chasing.
Producing.
while also becoming responsible for:
Strategy.
Leadership.
Management development.
Financial planning.
Recruitment.
Investment.
Growth.
eventually one of two things happens.
The owner works ridiculous hours.
Or the strategic work simply does not happen.
Often both.
The business you started needed a different owner from the business you are building
Early on, the owner's willingness to do everything is often an advantage.
Customer needs something?
You do it.
Invoice needs raising?
You do it.
Problem at 7pm?
You answer.
Important proposal?
You write it.
Something goes wrong?
You fix it.
This keeps a small business alive.
The dangerous assumption is that the same behaviour must therefore keep the larger business healthy.
It doesn't.
An owner doing everything in a five-person business can look committed.
An owner through whom everything must pass in a fifty-person business is a bottleneck.
Same behaviour.
Different organisational context.
There is real evidence that decision-making changes as firms become larger and more complex
Research involving more than 1,000 CEOs and CFOs found that executives were more likely to delegate decision authority in larger and more complex firms.
Another field experiment examining management practices found that better management information allowed owners to decentralise more decisions to middle managers while productivity also improved in the treatment plants.
Those studies are not a formula telling a British SME exactly what to delegate at twenty employees.
But the organisational principle makes sense.
As complexity increases, the owner's finite attention cannot remain the decision-making infrastructure for everything.
Something has to move.
The hardest work to stop doing is often work you are extremely good at
This matters.
Owners assume delegation starts with weaknesses.
Sometimes it does.
Bookkeeping you hate.
Admin you avoid.
Tasks obviously better performed by someone else.
Easy.
The bigger transition comes later.
Eventually you have to give away work you are good at.
Perhaps you are the best salesperson.
Best estimator.
Best engineer.
Best relationship builder.
Best operational problem solver.
That expertise helped build the company.
But if every valuable activity must still involve the best person in the business, growth eventually hits the capacity of that person.
Which happens to be you.
Being the best person for a job does not automatically mean you should continue doing it
Imagine you can complete something in thirty minutes.
An employee takes sixty.
Owner logic:
"It is quicker if I do it."
Correct.
For that individual task.
Now repeat it twenty times this month.
You spent ten hours.
Employee received zero opportunity to improve.
Next month you remain twice as fast.
So you do it again.
This can continue for years.
Delegation frequently makes performance worse before it makes the business stronger.
That initial inefficiency is partly the cost of transferring capability.
Stop doing routine administration
This is the obvious starting point.
Scheduling.
Formatting.
Data entry.
Basic correspondence.
Meeting administration.
Routine reporting.
Expenses.
Diary management.
Uploading information.
Repeated customer updates.
Anything regular, teachable and low judgement deserves examination.
You may still choose to do some of it.
Maybe you genuinely enjoy something.
Fine.
But do not confuse:
"I like doing this."
with:
"The owner needs to do this."
Those are different statements.
The test is not whether the task is important
A task can be extremely important without requiring the owner.
Invoices are important.
Payroll is important.
Customer enquiries are important.
Quality checks are important.
Scheduling is important.
The question is:
Does this require owner-level judgement, authority, expertise or relationship?
If not, why does it still belong to you?
Importance is not a reason to centralise work around the owner.
In many cases it is a reason to build a reliable system around someone else.
Stop being the automatic approver
This one creates enormous hidden dependency.
Holiday request.
Owner approves.
Supplier purchase.
Owner approves.
Discount.
Owner approves.
Overtime.
Owner approves.
Customer refund.
Owner approves.
Quote.
Owner approves.
Equipment purchase.
Owner approves.
Eventually your day becomes hundreds of tiny permission slips.
None particularly difficult.
Together they consume enormous cognitive capacity.
Replace approvals with decision rules
Ask why the approval exists.
Risk?
Cash?
Quality?
Customer relationship?
Compliance?
Good.
Define the boundary.
For example:
Manager can approve purchasing up to £2,500 within budget.
Sales can discount up to 3% while maintaining minimum margin.
Customer-service manager can resolve complaints up to £500.
Operations Manager controls overtime within an agreed weekly envelope.
Now exceptions reach you.
Normal decisions do not.
That is management control without personal control.
The Chartered Management Institute's current professional standard describes more developed leadership in terms of establishing clear accountabilities, delegating effectively and enabling others with increasing autonomy.
That is the direction of travel.
Stop being everyone's first point of escalation
Employee has a problem.
Calls owner.
Supervisor has a problem.
Calls owner.
Manager has a problem.
Calls owner.
Customer has a problem.
Calls owner.
Supplier has a problem.
Calls owner.
You become extremely informed.
And extremely trapped.
Ask:
Who should normally own this problem before it reaches me?
Then reinforce that route.
If there is a manager, let the manager manage.
If somebody bypasses them, send the issue back unless there is a genuine reason not to.
Otherwise the organisational chart becomes decorative.
Stop answering questions that somebody else should learn to answer
This is difficult because answers are satisfying.
Someone asks.
You know.
You answer.
Problem disappears.
Efficient.
Except you may have just created tomorrow's interruption.
Try:
"What do you think?"
"What are the options?"
"What would you recommend?"
"What information are you missing?"
You can still help.
But make the other person carry some thinking.
A growing company cannot scale if knowledge always flows towards the owner before decisions flow back down.
Stop personally fixing every problem
This is the Fixer Loop.
Something goes wrong.
You intervene.
Because you are capable, you fix it quickly.
Immediate cost falls.
Customer protected.
Everyone relieved.
But the person or system responsible for preventing recurrence learns very little.
The next problem arrives.
You fix that too.
Eventually the business becomes remarkably effective at supplying problems to the owner.
Article #34 dealt with firefighting in depth.
The important point here is different:
As the business grows, solving problems personally becomes an increasingly expensive use of the owner's capability.
Your job becomes improving the organisation's ability to solve them.
Stop confusing rescue with leadership
Sometimes rescue is necessary.
Important customer.
Serious error.
Commercial risk.
Fine.
But if rescue becomes your default leadership method, the business never fully experiences the consequences of its weaknesses.
Weak manager?
Owner compensates.
Bad process?
Owner compensates.
Missing information?
Owner remembers.
Poor handover?
Owner connects the departments.
The company looks healthier than it really is because one highly capable person keeps correcting it.
That delays improvement.
Stop doing work simply because nobody else can do it yet
"Only I can do it."
Maybe.
What are you doing about that?
Some work genuinely is owner-only.
But if something is operationally necessary every week and only one person can do it, that is also a risk.
Break the work down.
Which part actually requires your expertise?
Which part is:
Preparation?
Information gathering?
Administration?
Routine judgement?
Follow-up?
Could somebody perform 70% and bring you the 30% requiring owner input?
Start there.
Delegation does not need to happen in one giant leap.
Stop holding important knowledge exclusively in your head
Customers.
Pricing.
Processes.
Supplier history.
Commercial judgement.
Technical knowledge.
Why decisions were made.
If employees continually need access to your memory in order to operate, your brain has become company infrastructure.
That is fragile.
You do not need to document every thought you have ever had.
Concentrate on knowledge that is:
Frequently required.
Commercially important.
Repeatedly requested.
Critical when you are absent.
Transfer it through:
Processes.
Examples.
Training.
Shared information.
Decision rules.
People.
The goal is not eliminating your knowledge.
It is eliminating unnecessary dependence on accessing you personally.
Stop personally checking everything for quality
This is a huge one for technically strong owners.
"I have to check it because my name is on it."
Understandable.
But where does that end?
Every quote?
Every drawing?
Every installation?
Every report?
Every proposal?
Every finished product?
At sufficient volume, owner quality control becomes the production bottleneck.
The answer is not lowering standards.
The answer is moving the standard out of the owner's head.
Build quality into the process
Define what good looks like.
Examples.
Specifications.
Checklists where useful.
Peer review.
Supervisor checks.
Sampling.
Training.
Escalation for unusual work.
Then measure failures.
Your role should gradually move from:
Inspecting every output.
to:
Ensuring the quality-control system works.
Very different job.
Stop checking capable people because their method looks different from yours
This is one of the fastest ways to destroy delegation.
Employee reaches correct result.
But they took a different route.
Owner:
"I wouldn't have done it that way."
Fine.
Did their method:
Create risk?
Reduce quality?
Break compliance?
Increase cost materially?
Damage the customer?
If not, perhaps the problem is merely discomfort.
You are delegating the outcome.
Not cloning yourself.
If everybody has to work exactly like you, your growth strategy requires manufacturing additional versions of you.
Difficult recruitment brief.
Stop handling every major customer personally
This one frightens owners because customer relationships are valuable.
And sometimes the owner absolutely should remain involved.
But there is a big difference between:
Strategic relationship ownership.
and:
Being the customer's account manager forever.
If your ten largest customers all believe the only useful person in the business is you, you have created a commercial dependency.
That affects:
Your time.
Succession.
Business value.
Management credibility.
Holiday.
Exit potential.
And the customer's experience if something happens to you.
Transfer customer relationships deliberately
Do not suddenly disappear.
Introduce somebody.
Include them in meetings.
Let them lead parts of conversations.
Redirect operational issues.
Create multiple relationships between the companies.
Eventually the customer trusts the organisation.
Not merely its owner.
You may remain strategically involved.
But every phone call should not require you.
Stop personally managing employees who already have a manager
You promoted Sarah.
Her team officially reports to her.
Then they come to you.
And you answer.
You change their priorities.
Approve their requests.
Resolve disputes.
Give instructions.
Sarah technically remains their manager.
In reality, she is your assistant.
Article #38 dealt with this problem directly.
If you employ managers, allow the management layer to exist.
Manage Sarah.
Sarah manages her team.
Anything else creates duplicate authority.
Stop having too many direct reports
There is no magic universal number.
But your direct reports should reflect the work you actually need to do with them.
If you have:
Operations Manager.
Sales Manager.
Finance Manager.
Office Manager.
Eight project managers.
Three supervisors.
Two administrators.
all reporting directly to you, the structure deserves examination.
Every direct report creates:
Communication.
Support.
Review.
Decisions.
Performance management.
Context switching.
At some point the owner becomes a coordination department.
Organisational layers should earn their place
This is not an argument for building a huge hierarchy.
Quite the opposite.
Every layer costs money and can slow communication.
But as organisations become larger and more complex, decision-making has to be distributed somehow.
Research on firm organisation consistently treats owners' and managers' attention as finite and examines how increasing scale creates a need to allocate decision authority through a hierarchy.
In practical terms:
You cannot sustainably manage everybody.
Build the smallest management structure that allows the organisation to work without routing everything through you.
Stop being the connection between departments
Sales tells you something.
You tell Operations.
Operations tells you something.
You tell Finance.
Finance asks a question.
You ask Sales.
Congratulations.
You are now middleware.
A human integration platform.
Useful at five people.
Ridiculous at fifty.
Managers need relationships with each other.
Systems need to share information.
Cross-functional decisions need somewhere to happen without the owner translating everything.
Ask managers to solve cross-functional problems together
Sales versus operations.
Operations versus finance.
Customer service versus production.
Do not immediately referee every disagreement.
Ask:
"What have you two agreed?"
"What decision do you recommend?"
"What trade-off are we actually making?"
You want an organisation capable of coordinating horizontally.
Not several spokes connected only through the founder.
Stop remembering everything for everybody
You know:
Which job is late.
Which customer needs calling.
Which employee promised something.
Which invoice is overdue.
Which supplier needs chasing.
Which manager has not finished their action.
Then you remind everyone.
This feels helpful.
It also turns your brain into the company's operating system.
Replace memory with visibility.
CRM.
Task ownership.
Meeting actions.
Scorecards.
Project system.
Calendar.
Whatever fits.
If work matters, its survival should not depend entirely on the owner's memory.
Stop being the company's diary
"When is that due?"
"Ask Adam."
"What did we promise them?"
"Adam will remember."
"Who's dealing with that?"
"Adam knows."
Dangerous.
Your exceptional memory may actually slow system development because it makes the weakness survivable.
Sometimes the business only builds a proper process once the owner deliberately stops compensating for its absence.
Stop setting everybody's daily priorities
At a certain size, this becomes another bottleneck.
Owner arrives.
"Do this first."
Then a customer calls.
"Actually do this."
Another issue.
"Pause that."
Employees learn:
Do not commit too strongly because priority changes when the owner receives new information.
Managers lose authority.
Longer-term work gets constantly interrupted.
The owner becomes the scheduling algorithm.
You need priorities further down the organisation.
Give managers outcomes, then let them prioritise
You still set company-level priorities.
Absolutely.
But the Operations Manager should translate those priorities into operational decisions.
Sales Manager into sales activity.
Finance Manager into finance work.
That is what management is for.
Otherwise you hire managers but keep the managerial thinking.
The ONS Management and Expectations Survey measures structured management partly through targets, performance monitoring, continuous improvement and people management, and finds stronger management practices are significantly associated with higher productivity.
The principle is straightforward.
Direction can come from above without every individual action needing to.
Stop attending every meeting
This one gives owners hives.
"I need to know what's happening."
Do you?
Which meetings require:
Your decision?
Your expertise?
Your strategic input?
Your relationship?
Attend those.
Which meetings exist largely so you can hear information that could be summarised elsewhere?
Question them.
Your presence has another effect too.
People often direct the conversation towards the most senior person in the room.
If you attend every operational meeting, managers may never fully own them.
Test a meeting without you
Pick one.
The management team or manager runs it.
You receive:
Key decisions.
Relevant numbers.
Exceptions.
Anything genuinely requiring your input.
What happens?
If the meeting collapses, useful information.
Fix the meeting or capability.
If it works perfectly well?
Excellent.
You just recovered recurring capacity.
Stop being permanently available
This one often feels like good leadership.
Open door.
Phone always on.
Email answered instantly.
WhatsApp at night.
Staff can always reach you.
Wonderful service.
Terrible architecture if everything gradually depends upon it.
Availability changes behaviour.
If asking you is always faster than thinking, people ask you.
If you answer managers' teams directly, people bypass managers.
If customers know you respond at 10pm, some will contact you at 10pm.
The behaviour of the system responds to the access you provide.
Availability should become deliberate
Who genuinely needs direct access?
For what?
When?
What counts as urgent?
What should wait?
What belongs to a manager?
You do not need to become inaccessible.
You need to stop making your constant availability a prerequisite for ordinary business operation.
Stop using your inbox as the company's workflow
If every important operational issue arrives through your email, you own the workflow whether you realise it or not.
Approval.
Question.
Customer request.
Supplier issue.
Employee problem.
Everything becomes:
Owner reads.
Owner forwards.
Owner responds.
Owner remembers.
Move operational work into appropriate systems and roles.
Your inbox should not be the main distribution centre for an established company.
Stop personally chasing everybody
"Have you done it?"
"Remember Friday."
"Where are we with that?"
"Did you call them?"
This is accountability by owner attention.
Article #36 dealt with the alternative.
Outcome.
Owner.
Deadline.
Measure.
Review point.
Then the system holds the commitment.
Not you remembering to ask.
Stop measuring your usefulness by how needed you are
This is much harder.
You built a company.
People depend on you.
Customers value you.
Employees seek you out.
You solve things.
That feels like evidence of importance.
It is.
But eventually the owner's job changes from:
being essential to everything
to:
building something that doesn't require them for everything.
Those can feel psychologically opposite.
The second is the more scalable form of leadership.
Your value should increasingly appear in decisions, not activity
Early-stage owner value may look like:
Twenty tasks completed.
Later-stage owner value may look like:
One excellent senior hire.
One bad opportunity rejected.
One capital-allocation decision.
One management restructure.
One major customer relationship developed.
One pricing decision.
One strategic priority clarified.
Those outputs look smaller.
Their leverage can be much larger.
Do not mistake fewer visible tasks for reduced contribution.
Stop solving problems before your managers have had time to solve them
You spot an issue.
You can already see the answer.
You intervene.
Maybe give them a chance.
Ask:
"Who owns this?"
"What are they doing?"
"When should we expect resolution?"
Unless the risk demands immediate owner involvement, let the system operate.
If it fails, learn.
If it works, you have evidence you were not necessary.
Both outcomes are useful.
Stop protecting everybody from manageable consequences
This is linked.
Employee forgets.
Owner reminds.
Manager misses.
Owner catches it.
Someone plans badly.
Owner rearranges everything.
The business experiences no consequence because the owner absorbs it.
That makes poor systems remarkably durable.
You should protect the company from serious damage.
You do not have to protect every adult from every manageable consequence of their own responsibility.
Sometimes learning needs friction.
Stop automatically taking work back when delegation becomes uncomfortable
This is the moment most delegation fails.
You hand something over.
Employee struggles.
Customer asks a question.
Quality dips slightly.
Owner thinks:
"I knew this wouldn't work."
Takes it back.
Delegation finished.
What did we learn?
That the owner was better at something they had done for ten years than the person doing it for two weeks.
Hardly surprising.
Instead ask:
What specifically failed?
Standard?
Training?
Authority?
Information?
Capability?
Review point?
Fix that.
Do not automatically reverse the entire handover.
Stop delegating tasks while retaining every decision
This creates the illusion of delegation.
Employee prepares everything.
Then waits for you.
They draft.
You approve.
They investigate.
You decide.
They arrange.
You confirm.
You reduced activity.
Not dependency.
Real capacity appears when appropriate decision rights move as well.
CMI's professional framework explicitly connects effective delegation with clear accountabilities and autonomy.
That is the distinction.
Stop doing low-value work during your highest-value time
Suppose you are the only person who can currently:
Negotiate a major acquisition.
Choose the next Operations Director.
Decide market positioning.
Resolve a shareholder issue.
Reallocate £500,000 of capital.
And you spend Wednesday morning:
Sorting email.
Checking expenses.
Rewriting an employee's customer response.
Approving holidays.
The problem is not that those things do not matter.
It is opportunity cost.
What did the business not receive because the owner was doing them?
This becomes more important as the company becomes more valuable.
Owner time should be allocated like capital
You would not invest £100,000 without asking what return it should create.
Yet owners spend ten hours a week on £20-an-hour work because:
"It needs doing."
Your time is finite organisational capital.
Use it where owner involvement creates the largest difference.
That does not mean putting an absurd fake hourly rate on every moment.
It means respecting scarcity.
Stop starting new things faster than the company can finish them
This is another owner habit that becomes expensive at scale.
New idea.
Launch.
New system.
Launch.
New service.
Launch.
New initiative.
Team still implementing the previous five.
Owners generate opportunities faster than organisations can absorb them.
As the business grows, leadership increasingly includes restraint.
Which opportunities do we not pursue?
What gets finished before something new begins?
Strategy is partly saying no.
Stop changing direction without explicitly resetting priorities
You received new information.
Changed your mind.
Perfectly legitimate.
But your team may still be working on the previous plan.
If priorities changed, say so.
What stopped?
What moved down?
What replaces it?
Otherwise every new owner idea simply joins the existing workload.
Nothing truly loses priority.
Everything becomes urgent.
That is how companies become simultaneously busy and unfocused.
Stop believing that stepping back means disengaging
This misconception keeps owners trapped.
There are two bad extremes.
One:
Owner controls everything.
Two:
Owner disappears and hopes.
Neither is good leadership.
Stepping back from execution should mean increasing management through:
Clear outcomes.
Good people.
Useful information.
Review.
Decision boundaries.
Strategic attention.
You should know what is happening without personally causing everything to happen.
That is a much more sophisticated form of control.
Better information makes stepping back easier
There is useful evidence for this mechanism.
In Bloom and colleagues' management experiment, improvements in information collection and dissemination helped owners become more comfortable delegating decisions to middle managers.
That matters because owners often frame delegation as a trust problem.
Sometimes it is actually a visibility problem.
"I need to check because otherwise I won't know."
Fine.
Build a better way to know.
Scorecards.
Dashboards.
Management meetings.
Exception reporting.
Customer measures.
Then reduce checking.
Stop making yourself the only person who understands the whole business
As businesses grow, nobody understands every detail anymore.
That includes the owner.
You need managers who understand their areas better than you do.
That can feel uncomfortable.
Good.
You hired them for capability.
Your role shifts towards understanding how the pieces fit together and where strategic decisions need to happen.
If you insist on retaining the deepest operational knowledge everywhere, you either prevent other people developing it or work until you collapse.
Stop hiring managers and then treating them like senior administrators
A manager's purpose is not merely reducing your task list.
They should take:
Responsibility.
Decisions.
People.
Problems.
Performance.
If they merely prepare information so you can continue deciding everything, you haven't created much leverage.
Skills England's Operations Manager standard describes the role in terms of planning and implementing operational activity, managing teams and projects, prioritising work, driving improvement and managing change.
That is management.
Let managers manage.
Stop expecting management capability to appear automatically
This is the other side.
You cannot just announce:
"You're in charge now."
and disappear.
Develop people.
Give feedback.
Clarify authority.
Let them make decisions.
Review outcomes.
Help them understand numbers.
Support difficult conversations.
The UK Government continues to support Help to Grow: Management specifically to strengthen leadership and management capability in SMEs, combining structured learning, mentoring and peer learning.
Management deserves deliberate development.
Stop holding roles long after the business can support specialists
Early on, owner as:
Head of Sales.
Head of Operations.
Finance Director.
Marketing Director.
HR.
Normal.
Later?
Maybe not.
Ask periodically:
Would I hire myself into this role today?
Not:
Could I do it?
Would you deliberately recruit you as the best available person for this particular role at this stage of the company?
Interesting question.
If the answer is no, why are you still occupying the seat?
But do not delegate the owner's job
This needs saying.
There is also work I would be cautious about giving away entirely.
The exact list varies, but owners generally need meaningful involvement in:
Company direction.
Capital allocation.
Major risk.
Key leadership appointments.
Ownership/shareholder decisions.
Critical strategic relationships.
Fundamental culture and standards.
Defining what success actually means for the owner.
You can take advice.
Use managers.
Use a board.
Use coaches.
Delegate preparation.
But somebody has to own the ownership decisions.
That is you.
The goal is not delegating yourself out of relevance.
It is removing work that prevents you performing the actual owner role.
Create an Owner-Only Test
For every recurring responsibility, ask four questions.
1. Does this genuinely require ownership authority?
Shareholder, strategic or major capital decision?
Perhaps keep it.
2. Does it require my unique current expertise or relationship?
Maybe.
If yes, ask whether that dependency should remain permanent.
3. Could another capable person make this decision within boundaries?
If yes, consider moving it.
4. What happens to the business if I keep this for another three years?
This final question is excellent.
Maybe nothing.
Or maybe you become a permanent constraint.
Audit where your week actually goes
Do not guess.
For two weeks, record your work in broad categories.
Owner/strategy.
Leadership/management.
Sales.
Operations.
Technical delivery.
Admin.
Firefighting.
Customer service.
Approvals.
Then look.
You might discover that your strategic-growth problem is not mysterious.
You work fifty hours.
Forty-two belong to jobs somebody else could theoretically perform.
There is no hidden extra week where the owner role can happen.
Something has to move.
Use DROP on your own workload
This is one place my DROP framework fits naturally.
Dump
Capture what you actually do.
Every recurring responsibility, decision and interruption.
Review
Which work requires the owner?
Which exists through habit?
Which keeps returning?
Offload
Move appropriate work through deletion, simplification, systemisation, delegation, development, automation or recruitment.
Plan
Protect the capacity you created for the owner's actual priorities.
Because there is no benefit in delegating ten hours and then filling them with ten different low-value tasks.
The reclaimed capacity needs a destination.
Do not delegate your workload. Redesign your role.
That distinction is important.
A traditional delegation exercise asks:
"What can I give away?"
A role-redesign exercise asks:
"What should my job now be?"
Then:
Which current work does not belong in that job?
This is much stronger.
Otherwise you delegate around the edges while preserving the same underlying owner identity.
You need to know what you are trying to become.
A practical Stop Doing Matrix
Put your recurring work into four boxes.
Keep
Requires owner-level judgement, authority, strategic context or critical relationship.
Develop then delegate
Somebody else could own it, but capability needs building first.
Delegate now
Clear outcome, capable person, manageable risk.
Move it.
Stop entirely
Work that should not exist.
This last category matters.
Do not delegate pointless work.
Delete it.
Delegating waste merely gives somebody else waste.
Start with frequency, not emotional difficulty
One task that takes three hours twice a year is probably not your bottleneck.
A fifteen-minute interruption happening twelve times a day might be.
Look for:
High frequency.
Low owner necessity.
Repeatable outcome.
Clear standard.
Those often release useful capacity fastest.
Then work progressively towards higher-value decisions and relationships.
Keep a Stop Doing List beside your to-do list
Most owners have endless lists of things to start.
Try maintaining the opposite.
This quarter:
Stop approving purchases below X.
Stop attending Monday scheduling meeting.
Stop handling standard customer complaints.
Stop reviewing every quotation.
Stop directly managing supervisors.
Stop producing monthly report.
Each item should create actual capacity.
Review whether it stayed gone.
That matters because work has a habit of creeping back.
When delegated work returns, investigate rather than automatically accepting it
The employee leaves.
Manager struggles.
System changes.
Suddenly:
"I'll just take it back temporarily."
Fine.
Set an end date.
Otherwise temporary becomes three years.
Every responsibility returning to the owner should trigger:
Why?
What failed?
What would move it back out?
Owner dependency grows through tiny reversals.
Watch them.
A 90-day owner-role reset
If you genuinely feel trapped in too much work, I would approach it like this.
Days 1–30: See the role
Track your time, decisions and interruptions.
Identify:
What only you can currently do.
What somebody else should own.
What should disappear completely.
Choose three recurring responsibilities to move.
Days 31–60: Transfer capability
Define:
Outcome.
Standard.
Owner.
Authority.
Information.
Review point.
Train where needed.
Move decisions, not merely tasks.
Then deliberately stop interfering.
Days 61–90: Protect the new owner role
Use released capacity for:
Strategy.
Leadership.
Management development.
Commercial analysis.
Major decisions.
Improvement.
Then identify the next layer of work to transfer.
This should be continuous.
Your role keeps evolving as the organisation evolves.
Ask one question every time the business grows
What can only I do now that the business is this size?
Not:
What am I still doing?
What does this version of the company require from its owner?
The answer at:
£500,000 revenue
may differ significantly from:
£5 million.
And differ again at:
£20 million.
Growth requires the owner to keep renegotiating their relationship with the business.
You may discover the business does not yet have anyone to take the work
That is useful information.
Maybe you need:
An administrator.
Sales Manager.
Operations Manager.
Finance Manager.
Executive assistant.
Supervisor.
Fractional specialist.
Recruitment becomes easier when you understand the capacity you are buying.
Do not hire:
"Someone to help me."
Hire:
A person responsible for these outcomes, removing these dependencies and creating this capacity.
Much clearer.
You may discover existing people could already take more
Also useful.
Sometimes owners recruit too quickly because they underestimate their existing team.
Ask:
What decisions could managers make today if I simply gave them authority?
What work could somebody perform with training?
What responsibility could move with better information?
You may already employ significant unused management capacity.
Use it before automatically adding headcount.
You may discover you are the thing preventing the transition
This is uncomfortable.
Team ready.
Manager capable.
Systems decent.
Yet you keep:
Checking.
Changing.
Overriding.
Answering.
Rescuing.
Taking things back.
Then the constraint is no longer organisational design.
It is your behaviour.
That is not an insult.
It is excellent news.
Because behaviour can change.
But first you have to notice it.
This is why agency matters so much
You are not condemned to operate the business in the way that originally built it.
You can redesign the job.
You can decide:
I no longer approve this.
I no longer attend that.
I no longer answer these questions.
I no longer personally own this customer process.
I no longer solve that category of problem.
That is agency.
Not doing less because you care less.
Changing where your effort goes because the organisation now needs something different from you.
How Evolve approaches owner-role transition
When somebody tells me:
"I need to delegate more."
I am not particularly interested in producing a list of random tasks for them to hand out.
I want to understand:
What should your role actually be now?
Where does your time go?
Which decisions depend on you?
Which customers?
Which employees?
Which approvals?
Which information?
Which problems?
What does the company genuinely lose if you stop doing each one?
Then we start removing the dependencies.
Some quickly.
Some over months.
Some require recruitment.
Some require management development.
Some need better systems.
Some turn out not to need doing at all.
The objective is not making the owner less involved.
It is making their involvement more valuable.
This is one of the biggest transitions in business ownership
You start by proving:
I can do this.
Then build a team and have to learn:
Other people can do this.
Then build managers and eventually:
Other people can decide this.
Then develop an organisation capable of saying:
The business can handle this without me.
That progression can feel like giving things up.
In reality, you are creating leverage.
Your company gains capability outside your own hands.
That is what growth is supposed to do.
So, what should a business owner stop doing as the company grows?
Stop doing routine work that no longer requires you.
Stop approving normal decisions that capable managers could make.
Stop being everybody's first escalation point.
Stop answering every question.
Stop personally fixing recurring problems.
Stop checking every output.
Stop owning every customer relationship.
Stop managing employees who already have managers.
Stop connecting every department.
Stop remembering everybody's work.
Stop attending every meeting.
Stop making yourself permanently available.
Stop rescuing people from every manageable mistake.
Stop taking delegation back at the first sign of discomfort.
Stop keeping every decision simply because you are better at making it.
And stop measuring your value by how much the company needs you in ordinary operations.
Keep the work that genuinely requires ownership.
Transfer the rest as the organisation becomes capable of carrying it.
Because the owner's job is not supposed to remain static while everything around them grows.
At some point, the business cannot become something bigger until the owner stops doing the job that built something smaller.
