The handoff is where the work goes to die.

The most expensive moment in any operation is not the work itself. It is the seam between two people doing the work. We have walked into operations carrying weeks of delay, double-booked teams, and quietly burning out senior staff — and almost every time, the cost is concentrated in the same place: the spots where work changes hands.

Leaders rarely describe this as a handoff problem. They describe it as a meeting problem, a chasing problem, an alignment problem, a follow-through problem. Those are the symptoms. The seam is the source.

Why teams don’t see their handoff problem

A handoff that works is invisible. The receiver gets what they need, when they need it, in a form they can act on, and the sender stops thinking about it. Nobody talks about handoffs that work. They talk about the ones that fail — and they call those failures by every name except “handoff.”

So the team accumulates a hidden inventory of failed seams. Each one shows up as a meeting that should not have been needed, a sender who keeps the work in their head “just in case,” or a receiver who quietly re-does work because they cannot trust what was sent. None of those line items is labelled “handoff cost” in any budget.

Three things that disappear in an undocumented handoff

Context. The sender knows why the work is shaped the way it is. The receiver gets the shape and not the why. The first time the receiver hits an exception, they have to choose between making it up, going back to the sender, or escalating — and most of the time they make it up.

Ownership. Once the work leaves the sender’s desk, who owns it? Most operations would say “the receiver,” but in practice ownership is shared, ambiguous, or quietly held by the sender, who keeps re-checking. Ambiguous ownership produces the longest queues in any operation, because nobody is fully responsible for moving the work forward.

Deadline. The sender has a deadline. The receiver has a different deadline. Neither of them has the deadline that actually matters: the downstream commitment the operation made to a client, a regulator, or another team. Without a single agreed-on deadline anchored to that commitment, the work drifts to whichever calendar yells loudest.

What changes when handoffs are documented

Senior people stop holding work “just in case.” The team stops booking recurring catch-up meetings whose only function is to find out where things stand. Exceptions get raised earlier, because the receiver knows what was supposed to happen and can name where it didn’t. The operation gets quieter — which is what a healthy operation actually sounds like.

None of this requires a new tool. It requires writing down, for the four or five seams that carry the most work, what the packet contains, who owns the result, and how acceptance is acknowledged. The operation lightens before anything else is changed.