By Andreas Pettersson, Founder, Leaders ADAPT
On Tuesday you gave your sales lead the renewal list. By Friday the spreadsheet had a new owner, new colors, and zero calls to the three accounts that actually mattered.
"Renewed" meant one thing in your head and another thing on the sheet. The file changed hands. The finish line didn't.
Most advice on how to delegate stops at the handoff. The failure happens in the week after it. The Delegation Protocol I teach covers both, and its timing rule has one number in it: check in when the work is 25 percent done.
Delegation is handing someone an outcome, the authority to decide how to reach it, and one agreed check-in, so the result stays theirs.
Quick answer: To delegate so the work stays delegated, use four handoff moves: hand over the outcome instead of the steps, state the person's authority level out loud, and ask them to explain the assignment back in their own words. Then schedule a single check-in when the work is about 25 percent done and ask about blockers, not the draft. Most returned work traces to a skipped move.
How to delegate effectively: the four handoff moves
The top results for this question give you roughly the same nine tips. Know your people. Define the goal. Give feedback. Say thanks. None of them is wrong, and none of them tells you why the renewal list is still yours on Friday.
Here's the problem. Tips describe a good delegator. Moves are things you do, in order, in about three minutes. Skip one and you can predict exactly how the work comes back.
Move 1: Hand over the outcome, not the steps
A task is a set of steps. An outcome is a result with a number and a date on it. "Update the renewal sheet" is a task. "Every account over the threshold has a signed renewal or a written reason by the 30th" is an outcome.
With a task, the other person can only do it your way, so every fork in the road comes back to you. With an outcome, the forks are theirs.
Then ask the question I ask on coaching calls, word for word: "Do you know how you would do that?" If the answer is yes, stop talking. If it's no, you just learned the handoff needs more context, before the work starts instead of on Friday.
Move 2: Say the authority level out loud
Most leaders hand over the work and quietly keep the decisions. The person owns a result they aren't allowed to steer. So they ask. Every question lands on you, and you call it a trust problem.
It's an authority problem. Real empowerment is a decision right you can name, not a feeling. The Delegation Protocol uses three authority levels:
- Level 1: decide and inform me after.
- Level 2: decide, but tell me before you implement.
- Level 3: recommend options and I'll decide.
Pick one and say it. Leave it unsaid and the safest reading for the other person is Level 3, which means you're still doing the deciding.
Move 3: Ask for the read-back
A nod is not a read-back. Before the person leaves, ask three things: what did I just ask you for, why does it matter, and are you committed to it. The answers take sixty seconds. They also expose the gap between what you said and what they heard, which is the gap every returned piece of work falls through.
If what comes back is a hedge, don't accept it. Ask for a yes or a no. A clear "I can't take this on" is worth more than a soft yes that turns into a Thursday question.
Move 4: Put the 25 percent check-in on the calendar
The 25% Rule is a check-in timing rule: review delegated work once, when it is about a quarter done, and ask about blockers rather than asking to see the draft.
A one week project means Wednesday. A one month project means the end of week one.
At 5 percent the check-in is micromanagement with a calendar invite. At 90 percent it's too late to change direction without starting over. At 25 percent a wrong turn costs an afternoon.
Let the owner name the date, too. One line from a coaching session I run often: ask them when they can have it done. You're not dictating the time.
They know their week better than you do, and a date they picked is a date they'll defend. Your weekly one-on-one meetings are the natural home for that check-in.
The Delegation Protocol is the handoff method in The 5-Minute Leader: choose the work with the 70% Test, hand over an outcome at a stated authority level, confirm it with a read-back, and check in at 25 percent.
What is the difference between delegating a task and delegating an outcome?
The task vs outcome split decides most of what happens next. The table puts the two side by side.
| Task delegation | Outcome delegation | |
|---|---|---|
| What is handed over | A list of steps | A result with a measure and a date |
| Definition of done | Held by the manager, often unstated | Written down before work starts |
| Who chooses the method | The manager | The owner |
| Decision rights | Implicit, usually kept by the manager | One of three authority levels, stated |
| Check-ins | Ad hoc, whenever the manager worries | One scheduled check-in near 25 percent done |
| Typical failure | The work returns as a question | The result misses a standard both people knew |
| Skill it builds in the owner | Following instructions | Judgment and ownership |
Outcome delegation is harder to set up. It takes three minutes instead of thirty seconds. It also removes the reason the work comes back, which is that the owner could never finish it without you. That's the trade at the center of effective delegation.
What should you delegate and what should you keep?
Start with last week's calendar, not your intuition. Go line by line and ask one question of each item: could someone else get this to 70 percent of my quality? That's the 70% Test. If yes, it goes on the list.
Four conditions make a good first handoff, and all four have to hold: you do it regularly, someone can already do it at 70 percent or better, it needs little context, and the stakes are low if it's imperfect.
Scheduling, first drafts of weekly updates, expense reports, basic research and social posting usually qualify. That's how to delegate tasks without betting anything important on the first try. Three recurring items off your plate this month, then three more next month.
What you keep is shorter: the decisions only the person in your seat can make, and the one outcome that makes the week count. Your priorities are the list of things nobody else can carry. Everything else is a candidate.
When I was running Arcules, I hired 30 people in the first three months and 70 by year two. My week sat at 60 hours.
By the time the company passed 150 people, it was 45. The difference wasn't more trust. It was four protocols installed over 90 days, starting with this handoff, and later written down as The 5-Minute Leader. Nothing clever. The same three minutes, repeated until they were boring.
That's delegation in leadership at its plainest: fewer answers from you, more decisions from them. If your role is splitting from founder to CEO right now, the founder to CEO delegation systems guide maps which decisions move first. If you want your managers trained on the same handoff, delegation training for managers covers the five level approach, and the delegating leadership style explains when handing over the decision fits the person in front of you and when it doesn't.
When delegation fails: a router for the four breakdowns
Delegation fails in four recognizable ways. Each has its own page on this site, because each has a different fix. Find your sentence, then follow the link.
"It came back": why does delegated work come back?
The work returns as a review request, a quick question, or a decision in disguise. The cause is almost always Move 1 or Move 2: a task instead of an outcome, or an outcome with no stated authority. The guide to reverse delegation and how to send the work back gives you the sentences for the moment it lands on your desk, and a way to trace which move was missing.
"I keep checking": how do you delegate without micromanaging?
You opened the doc "just to look" and rewrote half of it. That isn't a personality flaw. It's what happens when you kept the outcome and handed off only the steps: watching the steps is the only protection left.
The fix is Move 4, one check-in at a fixed point, and a 70 percent bar for accepting work done differently than you'd do it. The full method lives in how to stop micromanaging your team, and the numbers behind the habit are in the micromanaging statistics.
"They missed it": the standard slipped and nobody said so
The deadline passed and you found out by asking. This is where delegation meets accountability.
If the definition of done was written down and read back, the miss is a conversation about a known standard, not an ambush. How to hold employees accountable has the read-back script for that conversation. For the team-wide version, where people correct misses without you in the room, see building a culture of accountability, and for the data on how wide the gap runs, the accountability statistics for 2026.
"Who owns it?": two names, or none
Two capable people each assumed the other one had the final call. The work didn't fail. Ownership did. The rule is one accountable name per outcome, said out loud at the handoff and written wherever the team tracks work, because if it isn't on the board, it isn't delegated. Responsibility vs accountability explains why several people can share the work but only one person answers for the result.
Sometimes the router points at a person rather than a move. If a manager two levels down keeps pulling work back up, the decision is whether to coach them yourself or bring in a management coach for a struggling manager. If the bottleneck is you, founder coaching for the founder who can't delegate is the one-to-one version of this page. And if nobody above you checks whether you did what you said, that's the job of an accountability coach for CEOs.
Delegation in leadership, by the numbers
Three figures frame how common weak delegation is. All three are sourced below, and the full set of verified figures, with the ones we rejected, is on the delegation statistics page.
19 percent. Share of more than 70,000 manager candidates assessed worldwide who demonstrate strong delegation abilities (DDI, Global Leadership Forecast 2025).
26 percent. Share of 1,259 respondents who say their organization makes delegated decisions that are both high quality and fast (survey fielded February 2018, McKinsey Quarterly, 2019).
32 percent. Share of 84 owner CEOs who came to Leaders ADAPT for coaching, advisory or a discovery call between June 2024 and September 2026 and raised delegation and being the bottleneck, against 25 percent of 56 executives (Leaders ADAPT, What CEOs Bring to Coaching, n = 199).
No first party delegation score distribution is published yet, because no delegation assessment has reached the 30 completion floor. The delegation assessment is where that number will come from.
Work out your own weekly leak
Industry figures don't change your week. Your own number does. Count two things for five working days.
- Rework passes: each time delegated work comes back and you touch it before it ships. Multiply passes per day by the minutes each one takes, then by five. Three passes a day at 20 minutes is five hours a week.
- Status time: the hours per week your team spends telling you where things stand, in meetings or messages, that a written update could have covered.
For scale, Asana's Anatomy of Work Index estimates the average knowledge worker loses 209 hours a year to duplicative work and 103 hours to unnecessary meetings (Asana, fieldwork year not disclosed). If your rework passes alone come to five hours a week, that's roughly 250 hours a year, already above Asana's duplicative work figure, and it's hours of your time, not an average employee's.
How to delegate: FAQ
How often should you check in on delegated work?
A common rule is one planned check-in when the work is about 25 percent complete: midweek for a one week task, the end of the first week for a one month project. Earlier checks tend to read as oversight of the method; later checks leave little room to correct direction. The check-in focuses on blockers and needed resources rather than reviewing the draft. Additional check-ins are agreed at the handoff, not added ad hoc.
How do you delegate to someone who is not ready?
Match the assignment to the person's current capability plus a modest stretch, sometimes framed as about 10 percent beyond what they can already do. Hand over a smaller, lower stakes outcome first, use the most restrictive authority level (recommend options, manager decides), and widen it as results come in. A request for step by step instructions is a common sign the outcome was too large for the person's current level.
What are the most important delegation skills?
Four skills cover most of it: defining an outcome with a measure and a deadline, stating decision authority explicitly, confirming understanding through a read-back, and timing a single check-in. Two supporting skills matter as well: choosing which work to hand off, and accepting a result that meets the standard even when the method differs from the manager's. Feedback after completion closes the loop.
Is it faster to just do the work yourself?
For a single instance, often yes. Doing a task yourself usually takes less time once than explaining it well. The comparison changes for recurring work: a handoff that takes a few minutes and holds removes the task from every future week, while doing it yourself repeats the full cost each time. The one-off speed advantage is why leaders under time pressure tend to keep work they could hand over.
How do you delegate work to a team instead of one person?
Deciding how to delegate work across a team starts with splitting it into outcomes. Give each outcome a single accountable owner, even when several people contribute. State each owner's authority level, write the outcomes where the whole team can see them, and set one check-in per outcome. Shared ownership of a single outcome is a frequent reason team delegation fails, because each contributor assumes another person holds the final decision.
What is the first step in learning how to delegate?
Audit one week of the calendar and mark every task someone else could complete to roughly 70 percent of the manager's quality. From that list, choose one recurring, low context, low stakes item and hand it over as an outcome with a stated authority level. Reviewing at the end of the week which handoffs held and which returned shows which part of the handoff needs work.
How to delegate as a leader, starting with one handoff
The guides aren't wrong about trust. They're wrong about where it comes from. Trust isn't the input to delegation. It's the output of a handoff that held: an outcome, a level, a read-back and a Wednesday, repeated until nobody needs reminding.
So don't start by trusting more. Start by saying more, once, at the start. Then stay out of the doc until the date you both agreed on.
Every returned task is data. It tells you which move you skipped. Count them for a week and the pattern shows up fast.
From one handoff to four protocols
The four moves above are the core of the Delegation Protocol, the first of four in The 5-Minute Leader, my system for running a team in five minutes a day. I wrote it after scaling a company past 150 people as one of Canon's youngest CEOs. Each protocol fixes one thing:
- The Delegation Protocol keeps work handed off: outcome, authority level, read-back, the 25 percent check-in.
- The 1:1 Protocol surfaces problems early, while they're still small enough to fix in the meeting.
- The Accountability Protocol puts the standard where everyone can see it, so a miss gets noticed without anyone chasing.
- The Rhythm Protocol sets the daily and weekly cadence, and the team keeps it running when you're out of the building.
Part 2 adds how to adjust the handoff for four kinds of people. One of them will agree to almost anything to avoid a disagreement, and the adjustment for that person is the opposite of what feels polite.
Here's your first step, tomorrow morning, before email. Find the item you keep telling yourself is faster to just do, and write the result it should produce in one sentence. Pick the authority level, hand it over, ask for the read-back, and let the owner name the day they'll be a quarter done.
Three weeks from now, that item isn't on your Friday anymore. Someone else is reporting the result to you, on a date they chose, and your evening has an hour in it that used to belong to their draft.
That's how to delegate in practice. The 5-Minute Leader walks you through the other three protocols, one week each.
