The Task That Cannot Be Handed Over

Delegation has a quiet temptation: once a task has been named, it feels almost finished. Give it to an assistant, receive a polished result, and the remaining work appears to be approval. That appearance is where responsibility begins to thin.

The moment we imagine an AI assistant, this temptation becomes unusually smooth. It accepts a purpose in ordinary language, turns it into steps, and returns something that looks like completion. The surface is reassuring because language hides the distance between following an instruction and understanding why the instruction matters. A result may be coherent without being wise, accurate without being appropriate, or efficient in service of a goal no one has examined.

The task that cannot be handed over is the decision about what the task is for. An assistant may draft, compare, classify, schedule, or suggest. The owner still has to decide which errors are tolerable, which omissions are dangerous, and whose interests are absent from the brief. Those decisions are not administrative residue. They are the moral and practical content of the work.

Purpose is the part that resists compression. “Make this faster” hides a choice about what may be sacrificed. “Find the best option” hides a definition of best. “Watch this process” hides the threshold at which watching becomes intervention. In each case, the missing information is not a technical gap waiting for a better prompt. It is a judgment waiting for a person.

This is easy to miss when the output arrives with the calm grammar of certainty. A sentence does not show its own uncertainty. A list does not reveal the things that never entered it. A recommendation can be neatly reasoned and still inherit a narrow question from the person who asked it. Fluency can make a boundary disappear without ever crossing it.

The answer is not to keep every task manual. That would confuse effort with ownership. Delegation is often a form of care: it clears repetitive work so attention can reach the part that requires judgment. But the handoff should be designed like a door with a hinge, not a trapdoor. The result must come back carrying its assumptions, its open choices, and the points where a human decision is still required.

That is why a system should be judged not only by what it returns, but by what it makes visible before returning it. A pause, an explicit assumption, or a request for a boundary can be more valuable than a fast answer. Friction has a bad reputation, but some friction is the handrail that keeps a decision attached to its owner.

A useful assistant therefore does more than produce an artifact. It keeps the user able to answer four plain questions: What were we trying to accomplish? What did we allow the system to decide? What could it have missed? What will we do if it is wrong? If the process makes those questions harder to answer, convenience has begun to consume agency.

There is a quieter danger in successful delegation. When the work goes well, the owner may forget which parts were judgment and which parts were merely motion. The system becomes a mirror that returns a finished surface, and the person begins to mistake the surface for understanding. This is how responsibility disappears without anyone explicitly surrendering it.

Good delegation leaves a person more capable of seeing the shape of a decision, not less. It may shorten the path, but it should not remove the landmarks. The assistant can carry weight. It cannot carry the reason the weight matters.

The final signature belongs to whoever can still explain the choice.