How to delegate tasks effectively: a two-decision method

Most delegation advice fails because it treats delegation as one act: give the task away. It is actually two decisions you have to make out loud. First, how much authority you transfer (does the person decide, or do you?). Second, who owns the outcome versus who just does the work. The number one reason delegated work boomerangs back to your desk is not that you under-explained the task. It is that you left the authority level fuzzy, so the person defaults to checking with you, and the work quietly becomes yours again.

The fix is to name the authority level out loud, assign exactly one person who is answerable for the result, capture the brief and the agreed decision rights at the moment of handoff, and then refuse to take the work back when it comes wandering home. This guide gives you both decisions, copy-pasteable briefs, and the part everyone skips: making the handoff conversation survive past the meeting it happened in.

Why delegation sets the ceiling on your growth

This is not a soft skill. It is the throughput limit on you and everyone reporting to you. Gallup studied 143 CEOs on the Inc. 500 list and found the founders who delegate well grow dramatically faster than the ones who hoard.

Read those three numbers together and the pattern is blunt: the skill that most separates fast-growing founders from stuck ones is the one most founders are bad at. Delegation is not generosity you extend to your team when you have spare time. It is the ceiling on how much work your organization can move through, and if every decision routes back to you, you are the bottleneck no matter how hard you grind.

So the goal is not "give people more to do." It is to transfer real ownership so work finishes without you in the loop. That requires the two decisions below.

The real reason work comes back to you: the monkey

Before the two decisions, you need to understand the failure they prevent. In the Harvard Business Review classic "Management Time: Who's Got the Monkey?" (William Oncken Jr. and Donald L. Wass, originally November-December 1974), the "monkey" is the next move on a problem. Picture an employee who stops you in the hallway: "We have an issue with the vendor." You reply, "Let me think about it and get back to you."

In that one sentence, the monkey jumped from their back to yours. The next move is now yours. They are waiting on you. You have just reverse-delegated: you took work back from someone you were supposed to hand it to. Do that across ten people and your calendar fills with everyone else's next moves. The moment you say "let me get back to you," the next move leaps onto your back; keep it on theirs by naming the next decision they own before the conversation ends ("come back with a recommendation and your reasoning by Thursday").

Notice the fix is not more instructions. The hallway problem was not under-explained. It boomeranged because the decision rights were ambiguous, so the safest move for the employee was to hand it up. That is what the next two decisions make explicit.

Decision 1: pick the authority level

Jurgen Appelo's Management 3.0 framework defines seven levels of delegation, ordered by how much autonomy you hand over. Most managers operate at one default level for everyone and every task, which is exactly the mistake. The level should change based on the person's experience and how reversible the decision is.

The point is not to memorize all seven. It is to say the number out loud when you hand work off. "This is a level 6: you pick the agency and book the kickoff, then just tell me who you chose" is unambiguous. The employee knows they decide and that checking back with you would be a waste of both your time. Compare that to "go ahead and find us an agency," which gives them no idea whether you want to approve the shortlist. Ambiguity defaults to a lower level, which means it routes back to you.

A common mistake here is pseudo-delegation: handing over the task while keeping every decision (a permanent level 1 or 2). The person does the typing, you do the thinking, and nothing actually left your plate. Equally bad is dumping a level 7 on someone who has never done the task. Match the level to the person and the risk.

Decision 2: assign exactly one owner

The second decision is who is answerable for the result. The cleanest tool here is RACI, stripped of its consultant baggage. RACI assigns four roles per task:

• Responsible: does the actual work.
• Accountable: answers for whether it gets done, and done right.
• Consulted: gives input; this is a two-way conversation before the work.
• Informed: is kept up to date after the fact; this is one-way.

The single hard rule that prevents most dropped work: there must be exactly one Accountable person per task. Not two co-owners. Not a team. One name. The person who does the work (Responsible) and the person answerable for the outcome (Accountable) can be different people, and that is fine. What is never fine is zero Accountable or two Accountable. "Everyone owns it" means no one does, and "I thought you had it" is what you hear at the next standup.

You do not need a formal matrix for a single handoff. You need one sentence: "[Name] is accountable for [outcome]." For a multi-step project, a quick table keeps it honest:

Task                        | Responsible | Accountable | Consulted   | Informed
----------------------------|-------------|-------------|-------------|----------
Draft Q3 client proposal    | Priya       | Priya       | Marcus      | Dana
Approve pricing             | Marcus      | Dana        | Priya       | team
Send proposal to client     | Priya       | Priya       | -           | Dana

Read down the Accountable column and you should see one name per row, with no blanks. That column is the whole point.

Write a brief that actually transfers ownership

A good delegation brief is short and outcome-first. Step-by-step instructions feel thorough but they re-create dependence: you become the spec, so the person comes back every time reality differs from your steps. Instead, give them the destination and the decision rights, and let them find the route. Five things belong in every brief.

Here is a copy-pasteable brief for a recurring task:

Task: Weekly customer health report
Outcome: A one-page summary of at-risk accounts in the
  shared doc, ready before the Monday team call.
Why: Leadership uses this to prioritize save calls; late
  or vague reports mean we miss renewals.
Authority level: 6 (Inquire). You decide which accounts
  count as at-risk using the churn-signal rubric. Just
  flag anything above $50k ARR so I'm aware.
Accountable: Sam (also Responsible)
Done when: Doc updated by 9am Monday with status, dollar
  value, and recommended next action for each flagged account.

And one for a one-off project:

Project: Migrate the team off the old wiki
Outcome: All active docs moved to the new workspace,
  old wiki set to read-only, team notified where things live.
Why: We're paying for two tools; old wiki is the source
  of stale, conflicting info.
Authority level: 5 (Advise). You own the migration plan
  and tooling choice. I'll weigh in on the cutover date
  because it touches the client launch, but the call is yours.
Accountable: Jordan
Responsible: Jordan + Lee (Lee does the bulk moving)
Consulted: me (cutover timing only)
Done when: New workspace has every active doc, search works,
  old wiki is read-only, and the #team channel post is sent.

Notice neither brief tells the person how to do the work. They state the result, the stakes, who decides, who owns it, and what finished means. That is what transfers ownership. For project handoffs specifically, pairing the brief with a project kickoff meeting agenda keeps the room aligned on scope before anyone starts.

The handoff happens in a meeting, so capture it

Here is the part almost everyone skips. Delegation is verbal. It happens in a 1:1, a kickoff, a standup, a hallway. You say the outcome, you name the level, you name the owner, everyone nods. Then the meeting ends and that conversation, the single most important artifact in the whole process, starts decaying immediately. Two weeks later nobody can agree on whether it was a level 4 or a level 6, or whether Sam or Jordan was on the hook.

Relying on memory or chat scrollback for who-agreed-to-own-what is how good handoffs quietly come undone. The agreed authority level and the single owner need a durable home outside your head. The most reliable way to get one is to record the handoff conversation and pull the commitments out of it automatically.

This is where an AI notetaker earns its place, and it is worth being precise about what it does and does not do. It does not delegate for you. It captures the handoff: the transcript of what you agreed, and an auto-generated list of action items, each tagged to one owner with a date. That is exactly the record the two decisions above need to survive.

Scribbl records, transcribes, and summarizes meetings from your browser with no bot joining the call, and auto-generates that action-item list with one owner per item. For Google Meet it is free for individuals, so capturing your 1:1s and kickoffs costs nothing to try. Whichever tool you use, the move is the same: turn the verbal handoff into a written record with named owners before the day ends. Then route those items into one tracker, which is its own discipline covered in action item tracking, and use a consistent action items template so every owner and date lands in the same place.

Follow up without taking the monkey back

You assigned the level, named the owner, captured the brief. Now comes the test: the work-in-progress check-in, where most delegation silently reverts.

Set the check-in cadence at the handoff, not later. "Let's review progress next Thursday and at the halfway mark" is a pre-agreed milestone. Dropping in for an unscheduled status interrogation is a surprise audit, and surprise audits train people to hide problems until they are too big to hide. Agree the cadence up front and the check-in is collaboration, not policing.

When the person does bring you a problem, this is the exact moment the monkey tries to jump. Resist absorbing it. Coach the next move back to them: "What do you think we should do?" and "What would you do if I weren't here?" Your job is to keep the next move on their back, not to solve it and quietly reclaim ownership.

And when something goes wrong, treat it as feedback on your brief and your level, not just on the person. Did the work come back because you set a level 7 on someone who needed a level 4? Did "done" mean different things to each of you? Adjust the level, sharpen the definition of done, and re-delegate. That is how people climb the autonomy ladder over time.

Run your follow-up against the recorded action items and the definition of done, not your memory of the meeting. Reviewing open items at the top of the next recurring call is the cheapest way to make delegation stick. There is more on the cadence in how to measure team productivity.

A one-page delegation checklist

Run every handoff through this:

1. Pick the task to delegate. Recurring work and reversible decisions first. Founders who can't hand off the small stuff cap their own company's growth.
2. Choose the authority level. Name the Appelo number out loud. New person or high stakes, go low; trusted owner and reversible, go high.
3. Name exactly one Accountable owner. One name. Separate Responsible if a different person does the work.
4. Write an outcome-first brief. Outcome, why, level, owner, deadline and definition of done. Not step-by-step instructions.
5. Capture the handoff in meeting notes. Record the conversation and pull out action items with named owners so the decisions survive the call.
6. Set the check-in cadence at handoff. Pre-agreed milestones, not surprise audits.
7. Review against the captured action items. Coach the next move back to the owner; never take the monkey home.

If you manage a team or run client projects, the same method scales: see Scribbl for managers and Scribbl for project managers for how teams keep handoffs durable, and how to manage multiple projects for keeping several of these plates spinning at once.

Frequently asked questions

What is the difference between Responsible and Accountable?

Responsible is who does the work. Accountable is who answers for whether it gets done and done right. They are often the same person, but not always: a junior may be Responsible for drafting a proposal while a manager stays Accountable for it going out correctly. The rule that matters is that every task has exactly one Accountable person. Zero means it falls through the cracks; two means each assumes the other has it.

How detailed should a delegation brief be?

Detailed about the outcome, the stakes, the authority level, and the owner. Light on step-by-step instructions. Spelling out every step feels thorough but it makes you the spec, so the person returns to you the moment reality diverges from your steps. Tell them what "done" looks like and how much authority they have, then let them find the route. That is what builds capable owners instead of dependents.

How do I stop delegated work from coming back to me?

Name the authority level explicitly so the person knows whether they decide or you do, and when they bring you a problem, coach the next move back to them instead of saying "let me get back to you." That phrase is the moment the work becomes yours again. Pre-agree check-in milestones so you are not tempted to absorb status updates as new tasks.

Which delegation level should I start a new hire at?

Start lower (levels 1 to 3, where you keep the decision) on anything high-stakes or hard to reverse, then move them up the ladder as they earn trust on smaller, reversible tasks. The goal is to graduate them toward levels 5 to 7 over time. Keeping a capable person stuck at level 2 forever is just micromanagement with extra steps.

Does an AI notetaker delegate tasks for me?

No, and it is worth being clear about that. The human decisions, which task, what authority level, and who owns it, are still yours. What an AI notetaker does is capture the handoff conversation: the transcript and an action-item list with named owners and dates, so the decisions you made out loud do not decay into "wait, who was doing that?" two weeks later. It makes delegation durable; it does not make it for you.