You Delegated It. So Why Is It Back on Your Desk?

Six weeks ago you handed purchasing to your shop lead. This morning you approved three POs before nine.

Nobody decided to take it back. There was no meeting, no conversation, no moment where anyone said this isn't working. It drifted. He asked about one vendor because a price looked off. You answered. The next week he asked about two. By week four he was forwarding them all “just so you have eyes on it,” and by week six you were doing purchasing again — except now with an extra step in the middle.

That is not a failed employee. That is a failed handoff. The difference matters, because you cannot fix the first one and you can absolutely fix the second.

You Gave Away the Task and Kept the Outcome

What transfers in a normal handoff is the work. What stays behind is everything that made the work yours.

The clicking, the calling, the paperwork — all of that moves in an afternoon. What does not move is what a good result actually looks like, which tradeoff wins when two good things conflict, and the right to be wrong once without losing the job.

Your shop lead knew how to place a purchase order after about twenty minutes. What he never got was the part that took you years to build: the instinct for when a price is worth questioning and when it is not. So he did the only rational thing available to a person holding a task without the judgment that belongs to it. He came and asked you.

A Handoff Sticks When Three Things Move Together

The task, the standard, and the room to be wrong. Most owners hand over the first one and keep the other two.

The task is the easy part. Nobody gets stuck here.

The standard is the piece that gets skipped, because it lives in your head and has never been said out loud. Not “do a good job.” What specifically makes a purchase order right or wrong in your shop? Lowest price, or the vendor who has never missed a delivery date in November? You know the answer instantly. Nobody else in the building does, because you have never had to explain it to anyone.

The room to be wrong is the piece owners give last and take back first. If the first mistake pulls the work back onto your desk, you did not delegate anything. You ran a test, and everyone watching learned the result.

It Comes Back One Reasonable Question at a Time

There is never a dramatic reversal. There are thirty small ones, and each is individually defensible.

Harvard Business Review has kept a 1974 article in print for fifty years describing the exact move, because the move has not changed: someone brings you a problem, you say “let me think about it and get back to you,” and ownership of that problem changes hands in a single sentence. Nobody notices, because it sounds like leadership. It sounds like being a good boss.

That is the whole mechanism. Work does not come back in one piece. It comes back in fragments small enough that saying yes to each one feels like nothing at all. And this is the same drift that keeps your calendar from being yours — the work you took back has to be done somewhere, and it gets done in the hours you meant to spend on something else.

The Part Owners Do Not Say Out Loud

You take it back because you are better at it, because it is faster, and because watching it done at eighty percent is genuinely uncomfortable.

Gallup's research on employer entrepreneurs found that roughly three out of four have limited-to-low natural talent for delegating, and that the ones who are strong at it grow measurably faster. That is not a character flaw showing up in the data. It is a selection effect. Nobody builds a manufacturing or contracting business from nothing by being relaxed about handing work to people who will do it worse than they would. The instinct that got the business off the ground is the same instinct that caps it.

Naming that honestly is more useful than trying to talk yourself out of it. You are not going to stop caring how the work gets done. The fix has to survive an owner who cares.

This Is Not the Same Problem as Decision Rights

Authority is permission. Delegation is ownership. You need both, and they are two different repairs.

Permission is about writing down where someone's authority ends so they stop asking. That fixes the decisions that reach you. It does not fix the work that comes home.

A shop lead can have full authority to place a five thousand dollar order and still forward you every one of them, because authority tells him he is allowed to and nothing has told him what right looks like. Give permission without the standard and you get a nervous team that asks anyway. Give the standard without permission and you get a capable team that still has to wait. This is the point where Alignment has to turn into Momentum, and both pieces have to land together for that to happen.

What a Handoff That Sticks Actually Looks Like

Three moves, and none of them is a conversation about trust.

First, write the standard down before you hand anything over. Three to five lines on what a right answer looks like, and which tradeoff wins when two good things conflict. If you cannot write it in five lines, you do not have a standard yet. You have taste, and taste does not transfer.

Second, agree in advance on what comes back to you and what does not, and put a number or a date on it. “Anything over five thousand dollars, or anything with a vendor we have not used before” is a boundary. “Use your judgment” is not.

Third — and this is the one that decides whether any of it survives — set a review date and hold the questions until then. When he comes to you in week two, the answer is “what would you do?” and then, whatever he says, “do that, and let's talk about it Friday.” Something will go wrong. Being wrong on a Friday is cheap. Being the purchasing department again in six weeks is not.

Where This Leaves You

What is sitting on your desk this morning that you already handed to someone else?

Start there. Not because it is the biggest thing, but because you already decided once that it should not be yours — which means the argument is over and only the structure is missing. Delegation is one dimension of a larger repair, and the full arc from founder-dependent to self-running is worth reading if you want to see where this one fits.

FAQs

How do I know whether I actually delegated something or just loaned it out?

Count the questions. A real handoff has a question curve that drops — a lot in the first week, almost none by the sixth. If the same work is generating questions at the same rate in week six as it did in week one, you loaned it out. Flat is the warning sign, and flat is easy to miss, because every individual question seems perfectly reasonable.

Everyone says accept eighty percent. Is that right?

No, and I think it is some of the worst advice in this space. “Accept eighty percent” asks you to permanently tolerate work you believe is wrong, which no owner actually does for long. You will take it back within a quarter and then call yourself a bad delegator. The real fix is upstream: define the standard precisely enough that someone who is not you can hit a hundred percent of it. If the only version that clears the bar is your version, the problem was never the missing twenty percent. It is that the standard is still just your taste, and taste is not something anyone else can aim at.

What if I sit down to write the standard and find out I do not have one?

That is the most useful outcome, and it happens more than owners expect. A good share of what feels like a delegation problem is actually a Clarity problem — the work has been consistent for years because one person does it the same way every time, not because anyone ever decided what right looks like. Discovering that on a whiteboard is a good afternoon.

My person genuinely is not ready. Is taking it back not the responsible thing?

Sometimes it is, and that is a real call rather than an excuse. But make it a decision instead of a drift. Say out loud that you are taking it back, say what has to be true before it goes over again, and put a date on that. What damages a team is not the owner reclaiming work. It is work quietly reappearing on his desk with nobody willing to admit it moved.