The first real delegation drops the ball because the owner hands over the tasks and keeps the outcome. The fix is to hand over one whole thing, agree the checkpoints before the work starts, and say in advance what the employee does when they get stuck. Pick a responsibility that is whole: a client account, the month-end close, the weekly schedule. Write the finish line in one sentence the employee can check without asking you. Then hold the first cycle to the checkpoints, and let the result be theirs, including the first bad one.
Hand over an outcome, not a slice
Most failed delegation is decided at the setup, before anybody has dropped anything. The owner hands over a slice. Watch the inbox, chase the invoices, run the posts this month. A slice has no finish line, so nobody can say whether it is finished, and the owner ends up carrying the result of work he is no longer doing.
Oncken and Wass named that shape a monkey in the November to December 1999 issue of Harvard Business Review. The employee arrives with a problem, the owner says "let me think about it", and the monkey has climbed onto the owner's back. The article opens by asking why managers run out of time while their people run out of work.
Drucker gives the positive version of the same discipline. His argument in The Effective Executive is that knowledge workers are effective only insofar as they can make a contribution to the organization, and he listed "choosing what to contribute to the organization" among the five practices an executive has to master. Applied to a handoff, name the contribution you are handing over and hand over all of it. We looked at what else that book asks of a small owner in our review of The Effective Executive.
Four moves, in order
Exhibit 1
Four moves in order close the gaps that make the first handoff fail
Pick something whole. A client account is whole. It has a customer, a deliverable and a date. "Answer client emails" is not.
Write the finish line as one sentence the employee can check alone. Edwin A. Locke and Gary P. Latham reviewed 35 years of goal-setting research in American Psychologist in 2002 and found that specific, demanding goals produced the highest levels of effort and performance. Naming the finish line beats telling someone to do their best. They also warned that specificity alone is not enough, since goals vary in difficulty, and on complex work a hard performance goal can hurt where a learning goal helps. For a first handoff, that argues for a finish line that is clear above all.
Agree the checkpoints in advance, and hold them only for this cycle. A checkpoint invented after something goes wrong is an inspection.
Decide the stuck rule now. Stuck should never mean silent. State what the employee does when the thing has not happened by the checkpoint, who they ask, and what they are allowed to change on their own.
Doing it yourself is faster once
"I will just do it myself, it is faster" is accurate for one cycle. It is a bad trade for ten. The owner pays for speed with his own calendar, and the employee never gets a task big enough to be good at.
Andy Grove set out the rule that settles this in High Output Management (1983, Vintage Books edition). He called it task-relevant maturity: a person's readiness for one specific job, built from achievement orientation, willingness to take responsibility, education, training and experience. He wrote the rule plainly: "The fundamental variable that determines the effective management style is the task-relevant maturity of the subordinate."
Grove is describing the pair, a person and one job. The employee who runs your calendar flawlessly may be low-maturity on a client's first invoice, and the same person can be high-maturity in one job and low-maturity in the next. When task-relevant maturity is low, he wrote, the effective approach is precise and detailed instruction: what needs to be done, when, and how. As it rises, the instruction thins and the checkpoints spread out.
Exhibit 2
Supervision loosens by stages as the person proves the task
The three ways the ball drops
The owner answers the client directly. One email, one quick answer, done in a minute, and the account is quietly back on his desk. The client learns who to email.
The owner re-does the work silently. This is the one that poisons the handoff. The employee ships something, the owner edits it without saying so, and the employee learns the standard is private and cannot be aimed at.
The owner never says what good looks like. Then a result arrives that is exactly as good as the instructions, and both sides are surprised.
Exhibit 3
Delegating the outcome with checkpoints produces a different week than delegating tasks and keeping the outcome
The employee's ability is the same in both panels. In the first one the owner is the only person who knows when the work is finished.
Checkpoints are pause points, not inspections
Atul Gawande's The Checklist Manifesto, published by Metropolitan Books in 2009, argues that a checklist earns its place on the items an expert can forget. In his 2012 TED talk he described the surgical items as pause points, including one where everyone in the room says their name and role, because teams often come together for the first time on the day of the job. He reported in that talk that after eight hospitals adopted the 19-item surgical checklist, complication rates fell 35 percent and death rates fell 47 percent.
A handoff checkpoint has the same character. It is a scheduled pause where two people confirm three things: where the work stands against the finish line, what is at risk, and what the owner should know that the employee would rather not say. It takes a few minutes, and it reviews the work. Two fixed, predictable pauses in the first cycle do more than one long debrief at the end, and the rhythm is worth keeping for your own week too, as we describe in how to run a weekly review in 30 minutes.
Receive the first bad result without taking the work back
The first bad result is the test of the handoff, and it comes inside the first cycle. The temptation is to take the work back and do it yourself.
If the failure came from instruction that was too thin for a low-maturity task, the fix is more instruction and a closer checkpoint. The work stays where it is. If the employee knew the finish line and missed it, the conversation is about the miss, on the record, with the next checkpoint already in the calendar. Julie Zhuo opened her book on management from exactly this position. She became a rookie manager at 25 and did not know what she was doing. Her conclusion, as the publisher puts it, is that great managers are made.
Gallup reported in 2015 that managers account for at least 70% of the variance in employee engagement scores across business units. That figure describes the spread between teams. It is not a claim that a manager causes 70% of any one person's engagement. Read narrowly, it puts weight on how the owner manages handoffs.
The one-page handover is the whole method on a page
Write it once per delegated responsibility, on one page, and give the page to the employee. It holds:
- What you own, in one line, with the client's name on it if there is a client.
- Done looks like, one sentence you can check yourself, with no reference to my opinion.
- By when, plus the dates of the checkpoints in this cycle.
- Decision rights: what you may promise, spend or change without asking.
- Stuck rule: if this has not happened by the checkpoint, do that, and ask this person.
- What I will not do: answer your client, edit your work without telling you, move your dates.
The page is not a legal document, and it does not replace the paperwork that comes with staff. The SBA's guidance to a growing owner is plain: set up a basic payroll structure, then manage employees properly with a general understanding of state and federal labor laws. On written job descriptions, the EEOC has stated that the ADA does not require employers to have them, and that employers who use them should use them for all jobs; the same letter calls it good practice to make sure applicants understand the job requirements. The handover page carries that understanding for one responsibility, with one person, for one cycle.
The sign it worked is boring
The client stops emailing you. You did not ask them to stop. The person who owns the account has been answering for a while and they have noticed. Your name stops appearing on the thread, the work arrives without a nudge, and the checkpoints shrink to one line in a message.
If you want help writing the page, choosing the first responsibility, and setting the checkpoint rhythm around your own week, this is the kind of work we do in management consulting.