Hand over the outcome, not just the task

A four-step practice for managers and team leads who pass responsibility for work to someone else.

Agree the result, what the owner may decide alone, when to compare progress and what should make them pause and ask. The examples follow a fictional Northstar Services team refreshing its internal knowledge base; they illustrate how to coordinate work, not policy, and your own approval rules still apply.

Two colleagues talking at a desk

When delegating fits, and when it doesn't

Check the work against these before you start the conversation.

  • Delegate: a defined improvement with room for judgment Updating the 25 most-viewed help articles is clear enough to finish and open enough that the owner chooses how to approach it.
  • Delegate: work that builds someone's scope A recurring task, such as running the monthly content review, gives a team member a visible area to own and grow into.
  • Keep, or share: decisions that need authority the owner doesn't hold If a choice depends on budget sign-off or another approver, say so up front and agree who brings it to that person. Check your own organization's approval rules rather than assuming.
  • Pair first: work that needs access or expertise the owner doesn't have yet Work alongside them for the first round or arrange the training, then hand over ownership once they can do it without you.

Four steps to a clear handoff

Plan 30 minutes for the first conversation and shorter slots for each checkpoint.

  1. 1

    Choose the outcome

    Describe the result someone could see, and what counts as complete. For example: "Each of the 25 most-viewed onboarding articles has a named owner, a review date and no outdated screenshots."
  2. 2

    Define the boundaries

    List what the owner may decide without you, such as wording, order of work and which articles to merge. Then list what comes back to you, such as retiring an article or changing a team process.
  3. 3

    Agree checkpoints and how to raise a blocker

    Set dates to compare progress, based on the work rather than habit. Agree how a blocker is raised (a message the same day, not at the next checkpoint) and who covers if you're unavailable.
  4. 4

    Review what was learned

    At close-out, ask what worked, what slowed the owner down and which decisions should move to them next time. Record the answer so the next handoff starts further along.

Example agreement: knowledge-base refresh

A fictional agreement between a Team Lead and a Content Coordinator at Northstar Services. It is an example of the level of detail to agree, not a live work queue or a record of real assignments.

Example agreement: knowledge-base refresh
Agreement point Example
Outcome The 25 most-viewed onboarding articles are current, each has a named owner and a review date, and duplicates are merged.
Owner role Content Coordinator, with the Team Lead as sponsor.
Owner may decide Article wording and structure; the order of work; which near-duplicate articles to merge.
Bring back to the Team Lead Retiring an article; changing a process an article describes; anything affecting another team's content.
Checkpoint 1 (end of week 1) Agree the article list and the "current" criteria.
Checkpoint 2 (week 3) Review the first five updated articles together and adjust the approach.
Close-out (week 6) Compare the result to the outcome and hold a 20-minute review of what to carry forward.

Same task, two handoffs

The work is identical in both. What differs is how much the owner has to guess.

Unclear handoff

"Can you take over the knowledge-base cleanup? Let me know if anything comes up."

  • No finish line, so neither person can tell when it is done.
  • No stated limits, so the owner either asks about everything or retires an article they shouldn't.
  • No checkpoint, so problems surface in week five.
Clear handoff

"I'd like you to own getting the top 25 onboarding articles current by week 6. You can reword, reorder and merge duplicates without asking. Anything that retires an article or changes a process, bring to me. Let's compare notes at the end of week 1 and in week 3."

  • The outcome and the end point are both stated.
  • Decisions are split into "yours" and "bring to me".
  • Checkpoints are dated before work begins.

Questions managers ask

What if the owner gets stuck between checkpoints?

Agree in step three that a blocker is raised the same day by message, with what they tried and the decision they need. Checkpoints are for comparing progress, not the only time problems can be raised.

Am I still accountable for the result?

Delegating gives someone ownership of the work; it does not remove your responsibility to support them and to know how it is going. Your checkpoints are how you stay informed without taking the work back.

How many checkpoints are enough?

Enough that no surprise can run longer than a few days. Set more at the start of work that is new to the owner, and fewer as they show they can manage it.

Open the conversation with four questions

Ask them in this order, and let the owner answer in their own words.

  • What result are we aiming for?
  • What can you decide without me?
  • When should we compare progress?
  • What would make you pause and ask?

Delegation holds when both of you can state the outcome, the limits and the next checkpoint without looking at notes.