Every piece of work you hand to somebody involves two separate things you can keep or give away. The outcome — what a good result looks like. And the method — how they get there. Owners tend to treat these as one decision. Separating them is the model.
Split them and you get four ways of leading a piece of work: direct, delegate, guardrail and release. All four are right somewhere. The trouble in many owner-managed businesses is that the owner never picks at all, and default to the same corner for everything from a health and safety incident to a marketing plan.
What are the four quadrants?
Run the two dimensions against each other and four modes fall out. Read each one as a description of a task, not a description of a person — the label goes on the work.
Direct — you own both
You set the outcome and you specify the method. Correct for a new starter in their first fortnight, for anything with a safety or legal consequence, and for a real emergency where there is no time for anyone to work it out. It is wrong almost everywhere else, because a business run on direction produces people who wait.
Delegate — you own the what
You set the outcome and they choose the method. This is where most work in a healthy business should sit. You define what good looks like, by when, to what standard and with what budget. Then you leave the route alone — including the parts of the route you would have done differently.
Guardrail — you own the how
They set the outcome and you specify the method. It sounds like an odd corner until you recognise it: a qualified person choosing what to work on within a fixed process, a regulated file that has to be done a particular way regardless of what the individual is trying to achieve, brand and tone of voice, health and safety method statements. Here you fix the rails the work runs on.
Release — they own both
They set the outcome and they choose the method. Right for a proven leader running a whole function, where you agree a direction once or twice a year and then read the numbers. It is the corner every owner says they want, and the one that does the most damage when entered early — because from the outside, release and abdication look identical.
Why does an owner need the distinction?
The commonest complaint from owners is “I delegated it and it came back to me”. Usually it was direction presented as delegation. The outcome got handed over in the meeting and the method got taken back the following Tuesday, when the owner saw the work being done in a way they would not have chosen and stepped in.
The moment you correct the method after handing over the outcome, you teach the person that the real specification was in your head all along, and that the safest behaviour is to check with you first. You will then experience that checking as a lack of initiative, and the loop closes. Nothing about that is a capability problem in the other person.
A worked example
The figures are illustrative. A business turning over £1.4m has £96,000 sitting in debtors and an average of 68 debtor days. The owner hands credit control to an office manager who has been in post six months.
The direct version, which is what usually happens: “Ring these four, in this order, use this wording, copy me in, tell me what they say.” The office manager makes the calls. The owner reviews the replies, rewrites two of them, and picks up the awkward one personally because it is a good client. Debtor days come down for a month because the owner is on it, then drift back. A task has been lent out, and nothing has been handed over.
The delegate version is a different conversation and takes longer to have. The outcome is stated as a number and a date: debtor days under 45 by the end of the quarter, with no client relationship damaged. The constraints are stated plainly: nobody goes to a solicitor without the owner, and payment plans over £5,000 get signed off. The reporting is stated: one figure on a Monday, and a call if a client goes past 90 days. Then the method is left alone. If she decides to email before ringing, offer a small settlement discount, or rewrite the invoice wording completely, that is hers.
Some of what she does will not be what the owner would have done. That is the price and it is not optional. What the owner buys for it is a credit control function that keeps working during the fortnight he is not there, and one figure a week instead of an ongoing job.
Legal action and large payment plans stayed in guardrail, because they are rails rather than method choices. Naming the rails at the start makes the rest of the handover safe, and it is the step owners skip and then replace with supervision.
Say the quadrant out loud
Say which mode you are in as you hand something over. “This one is direct — do it exactly this way and I will explain why afterwards.” Or “this is yours; I care about the result and the deadline, and I do not mind how you get there.”
Much of the friction around delegation comes from the owner picking a mode silently and the other person guessing a different one.
How to use this in the next week
- List the last ten things you handed to someone. Put each in a quadrant based on how you behaved afterwards, not on what you intended at the time.
- Find your default. Almost everyone has one corner with seven or eight items in it. That corner is your leadership style, whether or not you would have chosen it.
- Move one task from direct to delegate. Choose something that matters but is not existential. Write the outcome as a number, a date and a standard before you speak to anybody.
- Write the rails down before you hand it over. Three or four things that are non-negotiable, in writing. If your list runs past six, you are not setting guardrails, you are specifying a method.
- Agree the reporting, then stop looking. One number, one frequency, one exception that triggers a call. Checking in between those points is method interference and it undoes the handover.
- Name the quadrant out loud every time for a fortnight.
Common mistakes
They move across the grid too slowly and then jump too far. Years of direction, followed by a bad month, followed by handing an entire function to somebody with a “you crack on” — no agreed outcome, no rails, no reporting. That is abdication, and when it goes wrong it gets used as evidence that delegation does not work here.
The other mistake is quieter. An owner who wants to delegate keeps hold of the method for one reason only: the method is the part they enjoy. Be honest about that. If you are holding the “how” because you like doing the “how”, that is a legitimate choice about your own job. It is not a judgement about your team’s capability, and it should not be presented as one.
Questions to ask yourself
- Out of 10, how clearly does your team know which mode you are in when you hand them something?
- Which quadrant did you spend most of last week in, and was that the situation’s fault or your habit?
- What are you still specifying the method for, and would the outcome suffer if you stopped?
- Where have you called something delegation while behaving as though it were direction?
This runs right through Leadership Coaching. The move from owner to leader means learning to choose a quadrant on purpose and then stay in it long enough for somebody else to grow into it.