Insights
·7 min read

The Handoff Costs More

The task comes back.

It is almost right.

That is the expensive part.

You asked someone to take work off your plate. Now you are reading their questions, repairing their choices, and trying to remember what you meant when you said, "Just make it clean."

So you reach for the obvious diagnosis. They are not ready. They do not have your judgment. It would have been faster to do it yourself.

The task moved. The judgment did not.

That is why the handoff feels like a refund you had to process. You gave away the visible labor while keeping every hidden decision. The typing left your desk. The work did not.

Ambiguity Collects Interest

A vague handoff looks efficient because it is short. "Write the email." "Fix the page." "Handle the launch." Three seconds, task assigned, little green check beside your name.

Then the missing context begins to charge you. Which reader? What must they believe? What can change? What cannot? Does this need your approval, or does the owner get to decide?

The other person has only two choices. Interrupt you now, or guess and interrupt you later with a draft. Either way, the bill returns.

This is not an argument for writing a manual before anyone can move. That is another hiding place. It is an argument for moving the judgment that makes the task possible.

Harvard Business Review's discussion of effective delegation offers a simple check: ask the receiver to summarize what they heard, including what happens next, by when, and when you will check in. The point is not ceremony. It is catching the gap while it is still cheap.

Short is not clear.

Stop Delegating Motions

Most bad handoffs describe motion. Make a deck. Research competitors. Set up the campaign. Motion tells someone what their hands should do. It does not tell them what a good result must change.

That omission is seductive. If you state the result clearly, you have to admit whether you know what you want. You may discover that the task is foggy because your own decision is foggy.

It is easier to call someone a poor executor than to admit you handed them a sentence you had not finished thinking.

Asana's current guide to delegating work puts goals, expected outcomes, deadlines, priorities, documents, and resources inside a clear assignment. Notice what this does not require: dictating every move. The owner still gets room. The task simply stops asking them to read your mind.

This is the difference between control and clarity. Control says, "Use my hands from across the room." Clarity says, "Here is the finish line, the fence, and the part you own."

Send a Handoff Receipt

Before the task leaves, make it print a receipt. Not a brief thick enough to stun a horse. Four lines that prove the work can travel without your private context.

  1. Change. Name what must be different when the work is done. Not "make a landing page." Try "help a first-time visitor choose the right plan without asking us."
  2. Proof. Show what acceptable looks like. A past example, a customer quote, a screenshot, or a test can carry judgment faster than a cloud of adjectives.
  3. Fence. State what cannot move. Budget, promise, deadline, brand rule, legal line, or customer commitment. Freedom works better when the cliff has a rail.
  4. Return. Decide when the work comes back and what question the review must answer. Review the risky choice early, not every harmless choice forever.

Then ask the owner to play it back in their own words. If the summary surprises you, do not correct their character. Correct the receipt.

The receipt also needs one name. GitLab's public handbook uses a directly responsible individual to make ownership and decision authority explicit. A group can help. A group cannot be the one person who knows the next move is theirs.

Move the right to decide.

Review the Risk, Not the Person

Your first clean handoff will still make you twitch. The owner will use a phrase you would not use. They will solve a small problem in a way that feels wrong mainly because it is not yours.

Leave it alone.

If the work meets the change, proof, and fence, preference is not a defect. Taking the task back because you prefer a different shade of blue teaches everyone that ownership is theater. Next time they will wait for your hand to enter the frame.

Put checkpoints where uncertainty is costly. Review the promise before the full campaign is built. Review the data definition before the dashboard is polished. Review the offer before fifty versions of the ad appear.

The aim is not zero contact. The aim is contact that reduces risk instead of contact that rents out your judgment by the minute.

Make the Work Travel

The next task arrives. Your fingers move toward the chat box. You almost type, "Can you handle this?"

Instead, you stop. You name the change. You attach one piece of proof. You draw the fence. You set the return point and give one person the right to decide inside it.

The message takes longer to send. That is fine. Efficiency would make the handoff shorter. Effectiveness makes the work stay gone.

A day later, the task comes back. It is not how you would have done it. It does what it needed to do. You approve it without reopening every choice, and for once the space on your plate remains empty.

That is leverage. Not work leaving your sight. Work carrying enough judgment to move without you.

SharePostLinkedIn

A five-minute interruption

Still in research mode? Good. Put the idea on trial before you open another tab.

The first tool inside The Vault is The Kill List - five private questions that force one of three answers: kill it, test it this week, or admit the research is protection.

The decision waiting inside

The Kill List

Use it on the idea that has survived on notes, tabs, and respectable reasons instead of signal.

One email. Permanent access.

Put My Idea On Trial