Back to All Posts
POST

What Do You Do When Smart People Keep Missing Handoffs? A 2026 Guide

Why capable teams drop work between people, and what closes the gap at the moment of transfer.
Robert "Cujo" Teschner delivering a leadership keynote at the Meonske Professional Development Conference, shown on screens across the hall

A missed handoff is rarely a failure of care or competence. It is a failure of transfer: the person handing work over cannot see what the person picking it up is missing, because knowing something makes it very hard to model not knowing it. That is a documented bias, not a character flaw, and it does not respond to trying harder. It responds to structure.

Why do smart people keep missing handoffs?

Not because they do not care. A handoff fails when the person who hands work over cannot see what the person picking it up is missing. Deep knowledge makes that blind spot worse, not better. So the fix is a set format, not more care.

Handoff failures cluster among capable people. The work dropped between two strong performers is not work either of them was bad at.

That rules out the explanations most teams reach for first. It wasn't lack of effort, because both people were trying. It wasn't lack of skill, because both could do the job. And it wasn't usually a process, since most teams already have somewhere to write things down.

What is left is the transfer itself, and transfer has a specific failure mode. The sender is not deciding to leave things out. They are failing to notice that anything is missing, because the context is so obvious to them that it does not register as information.

We looked at the general shape of this problem in our piece on taskwork and teamwork: the gap sits between people rather than inside either one. A handoff is the sharpest version of that, because it is the one moment where the whole of one person's understanding has to survive the trip to someone else's head.

What actually gets lost when work changes hands?

Rarely the facts. What goes missing is the context around them: why this was done this way, what was tried and dropped, what to watch for. The sender has all of it. None of it feels worth saying.

The files get handed over. The status is usually accurate. What does not survive is the reasoning.

Three things tend to stay behind. The discarded options: the approach tried in week two and abandoned, which the receiver will now try again. The soft constraint nobody wrote down because everyone involved already knew it. And the early warning, the small signal the sender had learned to watch for and never named.

None of these feel like information to the person holding them. They feel like background. That's exactly why they aren't mentioned, and exactly why the receiver would have wanted them.

There is a second kind of loss that is easier to see and easier to fix. Nobody owns the gap. The sender's job ends when they send, the receiver's begins when they can act, and the distance between those two points belongs to no one. Work that is nobody's responsibility does not move until somebody notices it has stopped.

Why does knowing more make you worse at handing over?

Because you cannot un-know what you know. Once you have the answer, it is hard to judge what someone without it needs. That shows up clearly in the lab. Neither practice nor being told the score made it go away.

This has a name. Colin Camerer, George Loewenstein, and Martin Weber called it the curse of knowledge, in the Journal of Political Economy in 1989.

Their setup was clean. One group of 51 students estimated company earnings from published reports. A second group saw the same reports with the real earnings filled in. That group was then asked to predict what the first group had guessed. They knew more. Their only job was to set the extra knowledge aside.

They could not do it cleanly. The authors reject both the possibility that the better-informed group set their extra knowledge aside and the possibility that they were completely captured by it. The bias was real, and it was partial. As they put it, agents "are unable to ignore the additional information they possess."

Two details matter more than the headline. Running the judgments through a market cut the bias by only about half, and the reduction reached significance for just three of the eight companies. And in a smaller comparison, 19 people judging with an incentive against 13 judging with an incentive plus feedback, the feedback made no detectable difference.

Put those two findings side by side. A market with stakes helps a little. Being told you got it wrong doesn't appear to help at all. So this looks like a structural problem rather than a coaching one. Your most experienced person probably won't hand over better because you asked them to be thorough, or because the last one went badly. More information isn't always better, and they're carrying most of it.

Does a standard handoff format actually work?

Yes, and it has been put to the test. One large hospital study gave every handoff the same set shape. Errors fell sharply. Harm that had nothing to do with handing over did not move at all, which is just what you would want to see.

The clearest evidence comes from a setting where a dropped handoff is measurable. Amy Starmer and colleagues published a study of nine pediatric residency programs in the New England Journal of Medicine in 2014, covering 10,740 patient admissions before and after a change.

The change was not a tool. It was a bundle: a fixed structure for both spoken and written handoffs, training in how to run one, observation of people doing it, and a campaign to stop it sliding back.

Medical errors fell from 24.5 to 18.8 per 100 admissions, a reduction of 23%. Preventable adverse events fell from 4.7 to 3.3 per 100, a reduction of 30%. Both results held at p less than 0.001. Six of the nine sites showed significant reductions on their own.

The result that should persuade a skeptic is the one that did not move. Adverse events classed as not preventable went from 3.0 to 2.8 per 100 admissions, which was not significant. If the whole thing were a measurement artifact, or people simply becoming more careful across the board, that number would have drifted too. It did not. The improvement landed precisely where communication was the mechanism.

A business team isn't a hospital, and the stakes are different. The mechanism is not. A fixed structure makes the sender answer questions they would never think to ask themselves, which is the only reliable way around a blind spot.

Won't a standard format slow everything down?

No. In the same study, the spoken handoff took about as long as before. The rest of the day did not change either. A set format moves the work from recall to reading. It does not add time to the day.

This is the objection that kills most attempts, so it's worth answering with the measurement rather than with reassurance.

In the same study, the spoken handoff took 2.4 minutes per patient before the change and 2.5 minutes after. That difference was not statistically significant. The researchers also tracked how residents spent their time more broadly, including time with patients and time at a computer, and found no significant change there either.

A structure that covers more ground at the same time isn't a paradox. Unstructured handovers are slow in a particular way: they wander, they revisit, and they spend their time on whatever the sender happens to recall first. A fixed order removes the recall problem, and the time saved on remembering pays for the time spent on completeness.

The honest caveat is that this was a sustained program with training and follow-up, not a template emailed around on a Monday morning. A format nobody was taught to use is a form, and forms get filled in badly.

Why do handoffs break worst between functions?

Because space costs more than it looks. In one study, jobs ran late when the team sat far apart. That cost was twice as big across two sites. And where the people knew each other well, it all but went away.

There's evidence here from a setting much closer to most readers. Tuuli Hakkarainen, Anatoli Colicev, and Torben Pedersen studied new product work at a global maker of hydraulic pumps. They published in Production and Operations Management in 2026. The data covered 526 employees across 42 projects, tracked over 20 months.

Greater distance between the people on a project went with longer delays, and the link was significant. The conditions are the more useful part.

When research and production sat in the same country, the delay penalty was around 16 days. When they sat in different countries, it was around 31 days. Distance costs you on its own, and it costs you roughly twice as much where two functions meet.

Familiarity nearly erased the effect. Among people who had worked together before, the penalty dropped to roughly five days and was not statistically distinguishable from zero. Among people who had not, it was around 29.

And the obvious explanation doesn't carry the weight people give it. The authors tested time zone misalignment using daylight saving changes as a natural experiment, and found it does not explain the pattern on its own. So this isn't simply a matter of people struggling to find a meeting slot.

One caveat, because this study is being used slightly beyond its own frame. It measured each person's average distance from their project, not individual handoffs, and the authors say so themselves. Treat it as evidence about the cost of coordination across a seam, which is where handoffs live, rather than evidence about handoffs as such.

What should change on Monday?

Give the gap an owner. A handoff is a piece of work, not a moment. It belongs to one person until the other can act on it. Write down what they need, say it out loud, and check that it landed.

The single most useful move is also the least technical: decide who owns the handoff itself, as distinct from the work on either side of it. Our guide to holding a team accountable without creating fear covers why an unowned piece of work tends to stay unowned.

  • The person handing over: What they own at the handoff: Everything they know that is not in the file. What that looks like in practice: A short written note on what was tried and dropped, and what to watch for.
  • The person picking up: What they own at the handoff: Saying what they cannot yet do. What that looks like in practice: One question back, before the sender moves on.
  • The leader: What they own at the handoff: The gap itself, until someone closes it. What that looks like in practice: Asking who owns this piece between Thursday and Monday.
  • Both of them together: What they own at the handoff: A spoken exchange, not a forwarded file. What that looks like in practice: Ten minutes live, with the written note open in front of them.

Here's what I'll tell you: at VMax Group, we define accountability as taking absolute ownership for the outcomes a team achieves. A handoff is where that gets tested. If one of us fails, we all do, so the leader owns the gap until someone closes it. Beyond ownership, three things are worth building in.

Use a fixed order and keep it short. The point of a set structure isn't completeness for its own sake. It is that it asks the sender the questions their own knowledge stops them from asking. Four or five headings is plenty, and the same four or five every time.

Ask the receiver what they cannot do yet. That's the opposite of a comprehension check, and it works better, because it puts the burden back on the sender to fill a gap the receiver has just located. Naming a missing input is easy. Admitting you are confused is not. Our pieces How Do You Brief a Team So the Plan Actually Sticks? A 2026 Guide and How Do You Plan Work So Your Team Can Actually Execute It? A 2026 Guide cover the wider conversation around this.

Build familiarity on purpose where work crosses a seam. The finding that familiar pairs lose almost nothing to distance is the most actionable one here, because familiarity is something a leader can schedule. If the same two functions pass work back and forth every month, the people doing it should have met.

Finally, debrief the handoff, not the person. A dropped handoff is a system telling you where its seams are. And debrief the handoffs that went smoothly too, because a clean handoff you can't explain is one you can't repeat. That's the F-4 Debrief closing the loop of Plan, Brief, Execute, Debrief. Our guide to the no-blame debrief covers how to run that conversation so you find the seam instead of a culprit, and the after-action review gives you a structure for it.

In summary

  • A handoff fails in the gap, not at either end.
  • You cannot see what the next person does not know.
  • The more you know, the worse you are at handing over.
  • In hospitals, a set shape decreased errors. It took no more time.
  • When the two know each other well, the gap is much smaller.
  • Give the gap one owner, and say it out loud.

The reason this problem survives good hiring is that it isn't a problem with people. Your strongest performer is the one carrying the most unstated context, which makes them, on this one task, your least reliable sender. No amount of care fixes that, because the gap is invisible from the inside…and that includes your best people. A fixed structure and a named owner make it visible from the outside, which is the only place it can be seen from.

Losing time between people rather than inside the work? Book a call with VMax Group. Bring us one piece of work that changes hands every week, and we'll walk it end to end with you.

Frequently asked questions

Why do handoffs fail between people who are both good at their jobs?

Because the failure is in the transfer, not in either person. The sender cannot easily judge what the receiver is missing, since their own knowledge makes the gap invisible to them. Research on the curse of knowledge found that this persists even when people are paid to get it right, and that feedback had no detectable effect on it.

Does a standard handoff format actually reduce errors?

Yes, where it has been measured properly. A study of nine pediatric residency programs covering 10,740 admissions introduced a structured handoff bundle and saw medical errors fall by 23% and preventable adverse events by 30%. Adverse events that were not preventable did not change significantly, which suggests the improvement came from the communication itself.

Won't a handoff format add time we do not have?

The measured answer is no. In the same study, the spoken handoff took 2.4 minutes per patient before the change and 2.5 minutes after, a difference that was not statistically significant, and the researchers found no significant change in how residents spent the rest of their time. A fixed order replaces the time spent remembering what to say.

Why are handoffs between departments worse than handoffs inside a team?

Because the cost of coordination rises at the seam. In a study of 42 product development projects, the delay associated with distance was roughly twice as large when research and production sat in different countries as when they sat in the same one. Time zone differences did not account for the pattern on their own. Familiarity between the people involved reduced the penalty almost to nothing.

What is the single fastest change to make?

Name an owner for the handoff itself, separate from the work on either side of it. Most dropped work sits in a space that belongs to nobody: the sender has finished and the receiver cannot start. Giving that space one owner, and one short spoken exchange, closes more handoffs than any document template on its own.

Related Post
LET'S Get Started

Your team's story can change for the better. We're here to help it do so.

Book a call to talk about the outcome you need and the work it will take to get there.