Outcomes, not tasks

Every failure story I read for this module, the fired helper, the quit assistant, the owner back doing everything alone eighteen months after "scaling," traces back to one root. Not laziness, not bad luck, not the wrong hire. The owner delegated tasks instead of an outcome.

Watch how it dies, because it dies slowly and then all at once.

How task delegation kills the hire

You hand over tasks. Clean this kitchen on Tuesday. Confirm these appointments. Edit this batch. The tasks get done, competently. Then the questions start, because tasks have edges and the edges are everywhere: this kitchen has no oven listed, do I clean the oven? This client rescheduled twice, do I keep the slot? This edit needs footage that was never uploaded, what do I do? You answer. You answer again. Within a month you are answering forty small questions a week, and every answer is a decision you have not transferred.

The work got delegated. The decisions did not. You are now a dispatcher with a headset made of your own availability, and your calendar, which this hire was supposed to free, is fuller than before at a lower altitude. The bottleneck did not leave. It came back wearing your face.

The hire feels it too. Task workers get micromanaged, corrected on sequence instead of judged on results, and praised never, because completing tasks is invisible while owning something is visible. Good people leave bosses who run them this way. The ones who stay learn to stop thinking, which is worse.

And then the owner, now exhausted and paying payroll, concludes that hiring does not work, that nobody cares like they do, and does the work themselves at eleven at night. The business shrinks back to one person with a story about how they tried employees once.

The outcome version of the same job

Task version: "Clean the Hendersons' home on Tuesdays and Thursdays."

Outcome version: "You own the Henderson account. The home passes the walkthrough standard every visit, the client renews, and supply spend stays under budget. You decide sequencing, timing inside the agreed window, and supplies. Quality complaints or anything over fifty dollars comes to me same day. We both see the walkthrough pass rate and the renewal."

Same job, different machine. The task version produces questions. The outcome version produces a person who thinks on the job because thinking is now their job, not a hazard.

You already wrote the four sentences of an outcome statement when you defined the role. This is why. The outcome statement is not paperwork preceding the delegation; it is the delegation.

The delegation ladder

Nobody hands over an outcome on day one, and nobody should. Delegation is a ladder, and you climb it deliberately, with each rung named so both of you know where you are.

| Rung | What you say | What they own | |---|---|---| | 1. Do exactly this | "Here's the checklist. Follow it and flag anything off." | Execution | | 2. Do this, then tell me | "Run the job. Report the result same day." | Execution plus reporting | | 3. Decide inside the lines | "You handle it inside the checklist and the budget. Tell me weekly." | Method and sequence | | 4. Own the outcome | "This account is yours. Hit the number. I'll see the measure." | The result, end to end | | 5. Own and improve it | "This area is yours. Make it better and tell me what you need." | The result plus the system |

A new hire starts at rung one, and by day ninety a good one is standing on rung four in their core work, while new work always re-enters at rung one or two. That is not mistrust; that is how humans absorb new scope. What kills hires is parking a capable person at rung two forever. Client-service lanes feel this most, because the retainer is the measure: delegating client work in an agency is the social-media-agency course's own run of this ladder.

One caution before you sprint upward: climbing rungs is earned with evidence, one clean cycle at a time, not with hope or with exhaustion on your end. The owner who jumps from rung one to rung five in a busy week because they are drowning is not delegating; they are abdicating with a witness.

Checklists are the floor, not the ceiling

Rung one lives on checklists, and operators who train at scale treat them as sacred. But notice what the checklist actually is: the minimum, encoded, so that quality does not depend on memory or mood. It is a floor. The person standing on it adds judgment, pace, care at the end of the day, and the small mercies that turn a rebooking into a relationship. If you catch yourself saying "just follow the checklist" to a person you have had for six months, you have a rung problem, not a checklist problem.

The rescue, if you are already inside this mistake

You got here honestly; most owners do. The way out is mechanical.

Pick one area, the loudest one. Write the outcome statement: outcome, measure, boundaries, buy-back, four sentences. Sit down with the person and reset: here is what you own, here is how we will both see it, here is the rung we are on and the rung we are climbing to. Then hold your side, which is the hard part: when the question comes that they can answer, ask it back. "You own the Hendersons. What do you think?" Every question you bounce is a decision you transfer, and decisions transfer faster than skills.

Within a month of that reset, the owners I read describe the same moment: a problem got solved and you did not hear about it until the weekly meeting. That moment is the whole hire working. Protect it, because the next temptation is checking harder now that things run without you. The measure is the referee. Let it do its job, and spend your reclaimed hours on the work only you can do.