All Things Workplace

Delegation Without Dumping How-to

Sep 10, 2026 | How-tos, Leading Others

Dumping is assignment without authority. Delegate the outcome and decision rights, not just the task list. Include a mandatory line: what they can decide without you. If you will secretly reverse their call, you are not delegating. You are renting labor.

This timed handoff play sits beside the full framework Delegation without dumping. New managers often need it the same week they run Stop doing IC work detox. Track follow-through in Weekly 1:1 cadence.

Play card

Field Detail
Time box 15–25 minutes for a clean handoff (write + talk)
Players Delegator, new owner, stakeholders who need an FYI
Goal Written handoff note + first check-in scheduled
Done looks like Owner can restate outcome, constraints, and decision rights in their own words

When to use

  • Development opportunity: stretch that builds a skill you want on the team.
  • Capacity: you are the bottleneck and someone else can own the outcome with cover.
  • Specialist ownership: the work belongs closer to the craft or customer.
  • After an IC-to-manager shift when your old tickets still stick to you (From IC to manager).

When not to use

  • Success criteria are unclear even to you. Clarify before you hand off.
  • You are only offloading ugly work while keeping every interesting decision. That trains resentment, not ownership.
  • Political hot potato with no cover: do not “delegate” blame for a decision you will reverse upstairs.
  • Compliance-sensitive or irreversible calls that policy says stay with you. Involve others; do not dump oversight.
  • Fake delegation: authority in name only, veto in practice.

Handoff checklist (fill before or during the box)

Outcome (1–2 sentences):
Why it matters / team goal:
Done looks like (artifact + quality bar):
Owner:
Constraints / out of scope:
Resources (access, examples, budget, intro):
Decisions you own without me:
Recommend then decide with me:
Escalate immediately if:
Stakeholders (decide / consult / inform):
First check-in (date + what we’ll review):
Final due date:
Support I’ll provide:
Credit / where we’ll show the work:

If you cannot fill “Decisions you own without me,” stop. You are about to dump.

Steps inside the time box

  1. Pick one outcome (2 min). Not a vague “help with launch.” Name the finish line.
  2. Draft the checklist (8–10 min). Write decision rights first. Then constraints and done-looks-like.
  3. Match stretch to skill (2 min). High stretch needs closer check-ins and clearer escalate rules. Low stretch needs more autonomy, not more hover.
  4. Hold the assignment conversation (5–8 min). Use the script below. Ask them to restate.
  5. Send the note and schedule the first check-in (2–3 min). FYI stakeholders the same day when needed.
  6. Log a commitment in your next 1:1 doc so it does not vanish.

Move status between check-ins to async updates when useful.

Scripts

Assignment (no apology, no micromanage)

“I’d like you to own [outcome] by [date]. Done looks like [artifact/quality]. You can decide [X] without me. Recommend on [Y]. Escalate if [Z]. I’ll support with [access/intro/example]. First check-in is [date] to review [draft/decision]. Want to restate how you’re hearing it?”

Mid-flight support without takeover

“Show me the draft and where you’re stuck. I’ll help unblock. I’m not taking the work back unless we explicitly agree.”

If reverse delegation appears

“I can coach on the decision. The owner stays you. Bring options and a recommendation.”

Closing the loop publicly (credit)

In the team update: “[Name] owns [outcome]; here’s the result.” Do not reclaim the win in your own voice.

Weak dump vs clean handoff (fictional sample)

Weak dump: “Can you take the Q3 customer FAQ? Thanks.” No deadline, no decision rights, no stakeholder map. Owner guesses. Manager rewrites in private later.

Clean handoff: “Own the Q3 FAQ live on the help center by Sep 20. You decide article order and examples. Recommend final legal-sensitive wording with me. Escalate if Support says a top issue is missing. I’ll intro you to Support lead tomorrow. Check-in Friday on outline. Done = published pages + Support sign-off.”

Output artifact

  1. Handoff note (checklist above) in email, doc, or ticket.
  2. Calendar invite for first check-in with the review artifact named.
  3. Optional stakeholder FYI: owner, outcome, date.
  4. Commitment line in the pair’s 1:1 running doc.

Receivers on the IC track can keep a personal copy and push back when decision rights are missing. Start from the Individual Contributor hub if you are learning to accept ownership without absorbing chaos.

Support without takeover (mid-flight)

  • Review artifacts, not keystrokes.
  • Ask “what have you tried?” before solving.
  • Widen decision rights as quality proves out.
  • If you must take work back, say so explicitly and reset ownership. Silent takeover teaches learned helplessness.

Watch-outs

  • Dumping without context: Busy feels generous; rework follows.
  • Secret veto: Public owner, private reversal. Trust dies.
  • No escalation path: People either freeze or freelance into risk.
  • Only grunt work: Development requires some interesting outcomes, not only chores.
  • Skipping credit: Ownership includes recognition.
  • Labor-rule landmines: Do not use “delegation” to violate hours, duties, or classification rules. Practice framework only; follow employment policy.

Related hubs and plays