STEP 05
DELEGATE OUTCOMES.
NOT TASKS.
Most owners have delegated plenty and felt no relief. The work left their hands and came back as questions, corrections and rework, and the conclusion drawn was that good people are hard to find.
Usually the people were fine. What was delegated was tasks.
Tasks versus outcomes
Delegating a task means handing over an action and keeping the judgment. 'Call these twelve people and tell them the schedule moved.' The person executes and returns for the next instruction. You have bought hands and kept the entire cognitive load, which is the part that was actually consuming you.
Delegating an outcome means handing over a result and the decisions inside it. 'You own customer scheduling. The outcome is that every customer knows their current date, nobody learns about a change from a crew arriving, and the schedule in the system matches reality by end of day.' Now the twelve calls are their idea, and so is the thirteenth one you did not think of.
The distinction is not about seniority. It is about whether the decisions travel with the work. If they do not, you have not delegated. You have queued.
Define done before you hire
The most expensive hiring mistake in a small business is not hiring the wrong person. It is hiring into an undefined process.
When the process is undefined, a new person cannot be wrong or right, only different from what you imagined. Every piece of their work requires your review because there is no standard other than your preference. They generate questions at exactly the rate you were hoping to reduce them, and within two months you are doing your job plus supervision, which is worse than where you started.
The sequence that works: write the process, run it yourself against the written version for a couple of weeks, fix what the writing got wrong, define what done looks like at each stage, and only then hire. It feels slower. It is the only version that ends with less of your time in the job rather than more.
The rest of the material, including Cash Property Offers, lives on the main site.
The transition cost nobody budgets for
Here is the part that gets skipped in every article about delegation. For a period, the work will be done worse than you did it. Not slightly worse. Noticeably worse, in front of customers, while you watch.
That cost is real and it has to be planned rather than discovered. Budget for the time you will spend training, the errors that will reach customers, and the rework. Choose the moment deliberately: hand off during a period you can absorb it, not during your busiest month, and not during the month you are least patient.
The reason most handoffs fail is that the owner takes the work back at the first bad outcome. That feels responsible. It is the most expensive possible decision, because you have now paid the entire transition cost and received none of the benefit, and you have taught the person that the work returns to you under pressure. If you are not willing to absorb a stretch of worse, do not start the handoff.
The handoff that actually holds
- You do it, they watch and take notes. Their notes become the first draft of the process document, which is a better draft than yours because they do not yet skip anything.
- They do it, you watch and stay quiet. Correct afterward, not during, unless a customer is about to be harmed. Interrupting mid-task teaches them to wait for you.
- They do it, you review the output. Against the written definition of done, not against how you would have done it. This distinction is where most handoffs die: 'different' gets corrected as though it were 'wrong.'
- They own it, you see the number. You stop reviewing work and start watching the one metric that shows whether the outcome is being achieved. That is the finished state.
Step four is the one that is usually never reached, because reviewing work feels like diligence. It is not. It is the bottleneck reinstalling itself with a respectable name.
When not to hire
Hiring is the default answer to overload and it is frequently the wrong one.
- When the process is not written. You will hire a person to need instructions.
- When the work is not actually full. A partially-occupied hire drifts into whatever is loudest, which is how the accidental org chart gets built.
- When the real problem is a wait, not a shortage of hands. Adding people to a process that is mostly idle time makes a more expensive idle process.
- When you are unwilling to let the work be done differently. Be honest about this one. If only your version is acceptable, you are not hiring a person, you are hiring a mirror, and you will be disappointed.
The audit tells you which of those you are in. That is most of the reason it comes first.
Frequently asked
Questions people actually ask
How do I know when I am ready to hire?
When a defined seat exists, the process for it is written, the definition of done is checkable, and there is enough recurring volume that you are the constraint on it. Hiring before those exist usually produces an expensive person waiting for instructions.
What if I cannot afford to hire?
Then the next move is removing waits and rework rather than adding capacity. Most small businesses have more idle time inside their process than they have shortage of hands, and closing gaps costs nothing but attention.
Should I hire part-time or full-time first?
Hire against a defined seat rather than against an hours figure. If the seat's work is genuinely part-time, that is your answer. Choosing hours before defining outcomes is how people end up under-occupied and drifting.
How long is the transition period?
Longer than you want and it varies with the complexity of the work. What is predictable is the shape: worse before better, with the largest risk being that you take the work back at the first visible mistake.
What do I do when they do it differently but it works?
Nothing, if the definition of done is met. Correcting method rather than outcome is the fastest way to convert a capable hire into someone who checks with you first.
Is a virtual assistant a good first hire?
It can be for genuinely repeatable, well-documented work. It is a poor first hire for anything undefined, because remote work removes the informal correction that hides how unclear the process actually is.
Make your next move
A year from now, what will you be glad you started today?
You don't need another promise that everything will be easy. You need something useful to learn — and a next step you're willing to take.