ALL THE POWER

Do the job before you delegate

Most delegation attempts by UK owner-managers do not fail because the person was wrong. They fail because the owner never set a standard the person could meet. Here is the principle that fixes it, and the four-step sequence that makes it stick.

Where to start

Do The Job Before You Delegate

Roy Castleman's signature principle for UK owner-managed service businesses preparing to hand over work. Before delegating any task, do it yourself, even for a week. You cannot train someone on something you have not experienced. You cannot hold them accountable to a standard you have not set. Do the work, document the work, and hand over the document rather than the instructions. The practical sequence that lets delegation stick inside a small service business. Sits inside the Process competency of BOS UP.

The delegation fails before the person ever sees the task

Most UK service business owners have delegated something at least once, watched it come back wrong, and concluded that the person was not up to it. The conclusion is usually incorrect. The far more common cause is that the owner delegated a task they had never actually done themselves, or had not done for years, and so could not describe the standard the work needed to meet. The person did something reasonable. The owner said it was not quite right. The person asked what would be right. The owner could not quite say. After three rounds of that, the person stopped asking and produced mediocre work, or quietly resented the lack of clarity, or both.

The principle is short. Before delegating any task, do it yourself. Even for a week. You cannot train someone on something you have not experienced, and you cannot hold them accountable to a standard you have not set. Do the work, document the work, and hand over the document rather than the instructions. That is the move. Everything below is how to execute it cleanly.

This is one of the principles I come back to most often in coaching calls with service business owners. It looks like it says slow down. What it actually says is invest once, properly, at the start, so you can leave cleanly afterwards.

The four-step sequence

Each step maps to a question the owner needs to answer before the next step can land properly.

  1. Do the job. A week minimum for a simple task, a month for a complex one. The question this answers: what does good actually look like when my hands are on it? You are not becoming the permanent holder of the work. You are borrowing it long enough to see the edges. Watch where you slow down. Watch where you improvise. Watch what you do when the obvious answer does not apply. Those are the places the standard lives.
  2. Document the job. Write the SOP while the work is still fresh. Five elements are non-negotiable. Name and purpose of the process. The person responsible. The step-by-step sequence, in enough detail that someone who has never done the task can execute it. The decision rules for the common edge cases. The definition of done. Most SOPs fail because they have steps one and two and nothing else. The value is in the edge cases and the definition of done, because that is where judgement lives.
  3. Hand over the document, not the instructions. The person receiving the work reads the SOP, asks clarifying questions, and then executes. The SOP is the standard. You do not add verbal instructions on top of the document, because verbal instructions contradict each other over time and the team starts hearing three different versions of the truth. The document is the version. Update the document if the standard changes.
  4. Step back and hold them to the document. After the handover, your job is to hold the person accountable to the documented standard. Not to redo the work. Not to hover. If they miss the standard, you show them the part of the document they missed. If the document is unclear, you update the document. If you find yourself redoing the work inside the first month, the problem is that the document was incomplete, not that the person is incompetent. Go back and fix the document.

Four steps. The discipline is in the order. Skip any one of them and the delegation reverts to the pattern that was failing before.

The trap most owners fall into

The trap is obvious once named. Owners skip step one because they feel that stepping back into doing the work themselves is a regression. It is not. Stepping back into the work for a week is the investment that pays every future hour back. Refusing to do that week is what keeps the owner trapped in the pattern of delegating, taking back, redelegating, and redoing.

The second version of the trap is delegating a task the owner knows well in principle but has not done recently. The world has moved on. The clients have changed. The tools have changed. The standard that applied three years ago no longer applies. The owner delegates based on the old standard, the person executes to something close to it, and neither of them quite understand why the result feels off. Do the job for a week, even if you know it, because the week reveals what has changed.

The third version is delegating without writing the SOP at all, on the grounds that the person is capable enough to figure it out. This usually works for the first round, because capable people do figure things out. It fails quietly over months, because every person who joins the team afterwards inherits a standard that lives only inside one other person's head. That is not a delegation. That is a hostage situation.

Before you delegate, ask whether it should be automated

There is a sibling principle that lives next to this one, also from the Process competency: automate before you scale the person. Before you hire someone to do a repetitive task faster, ask whether the task can be automated entirely. SOP first, then automation, then the person. The logic is that a good SOP is readable by an AI tool just as easily as it is readable by a human, and for repetitive work with clear decision rules, automation scales without adding headcount.

The test is simple. Once the SOP is written, look at it honestly. If the work is mostly sequential, mostly rule-based, and mostly low-judgement, it is a candidate for automation. If the work involves regular edge cases, real judgement calls, or human-to-human relationship quality, the person path is correct. The SOP is the artefact that lets you make the choice, which is why the SOP has to be written either way.

The shift this principle unlocks for UK service businesses is that the AI pillar and the BOS UP pillar reinforce each other. AI reads SOPs fluently. The Business Brain is where the SOPs live in a place any AI tool can read. The Process competency is where the SOPs get written. Put together, a small UK service team can operate at the process maturity of a business twice its size.

The short version

Do the job for a week. Document the standard. Hand over the document. Hold the person to the document. If you find yourself redoing the work, the document was incomplete. Fix the document, not the person.

This sits inside the Process competency of BOS UP. The principle is old. The reason it matters right now is that AI makes the documented standard more valuable than it has ever been, because the document is what both a person and an AI tool can execute against. Start with the handful of tasks that currently drain the owner most. Do each one properly once. Watch what happens across the next ninety days.

Read the nine competenciesBack to the pillar

Keep reading

BOS UP Pillar · Live

The Nine Core Competencies

The parent discipline. Where the Process competency sits inside the full BOS UP system.

BOS UP Pillar · Live

The BOS UP Pillar

The pillar hub. The operating system that delegation hangs off.

BOS UP Pillar · Live

BOS UP vs EOS

Both systems honour the delegation principle. BOS UP installs it earlier in the sequence because of the UK service-business shape.

Guide · Live

How to Stop Being the Bottleneck

The broader guide. Three-lever approach to operational independence, where delegation is lever three.

AI Pillar · Live

The AI Pillar

The pillar that makes the SOP-then-automate path practical. AI reads documents fluently and executes the repetitive work.

Methodology · Live

Where to start

The Sequence Rule. Why time reclamation via AI has to come before delegation work lands properly.

Delegation, answered

Why does delegation fail for most business owners?+
The most common reason is that the owner delegates a task they have never actually done themselves, or have not done in years, and so cannot describe the standard the work needs to meet. The person doing the task does something reasonable, the owner says it is not quite right, the person asks what would be right, and the owner cannot quite say. After three rounds of that, the person either stops asking and produces mediocre work, or quietly resents the lack of clarity. The fix is not better communication. The fix is doing the task yourself for long enough to know what the standard looks like, then documenting the standard, and handing over the document rather than the task.
How long should I do the job before delegating it?+
Long enough to see the edges of it. That usually means a week at minimum for a simple task, a month for a more complex one. The goal is not to become the permanent holder of the work. The goal is to understand what good looks like, where the common mistakes happen, what the decision rules are when the obvious answer does not apply, and what the finished product should feel like when it is right. Once you can describe all four of those, you have enough to write the SOP. If you cannot describe them, you have not done the job long enough.
What if I have already delegated it and it is not working?+
Take it back. Do it yourself for a week or two. Write down the standard as you observe it in your own hands. Hand it back with the document. This is uncomfortable, because the person you delegated to will feel the swap, and you will feel like you are regressing. You are not. You are installing the thing that should have been installed before the first delegation. Do it cleanly, explain what you are doing and why, and the person usually thanks you afterwards because now they finally know what they are supposed to be doing.
What does a good SOP actually contain?+
Five things. The process name and purpose. The person responsible. The step-by-step sequence with enough detail that someone who has never done the task can execute it. The decision rules for the common edge cases. And the definition of done, which is what the finished work should look like to count as complete. Most SOPs fail because they only have step one and step two. The value is in the edge cases and the definition of done, because that is where judgement lives.
Does AI change this principle?+
AI amplifies it. The SOP is a written document, and written documents are exactly what AI reads fluently. Once you have done the job, documented the standard, and written the SOP, you can ask an AI to execute the repetitive version of the task following that SOP. The owner holds the judgement calls. The AI handles the documentation-and-execution cycle for the predictable work. The sequence is now: do the job, document it, then choose whether the next step is to train a person or automate the task. Automation usually wins for repetitive work, people win for work that needs judgement, and the SOP is the artefact that lets either path work.
Is 'Do the job before you delegate' the same as micromanaging?+
The opposite. Micromanaging is hovering over someone else's work without having set a clear standard. This principle is setting the standard yourself before anyone else is asked to meet it, then stepping back entirely once the document is in their hands. After the handover, the owner's job is to hold the person accountable to the documented standard, not to redo the work. If you find yourself redoing their work inside the first month, the problem is that the document was incomplete, not that the person is incompetent. Go back and fix the document.
Where does this fit inside BOS UP?+
Inside the Process competency, one of the nine core competencies. The parent principle is 'systematise the predictable to humanise the exceptional.' Documented processes are what let a business be flexible on the things that matter. The sibling principle is 'automate before you scale the person.' SOP first, then automation, then the person. All three sit underneath Enterprise Value, the culminating competency, because a business worth buying is a business whose processes do not depend on the founder being present.
More questions →