I didn't know that was a factor. It wasn't in the brief.

Context stripped in the handoff

Handoffs · Loss · Coordinate and act

WHAT’S GOING ON

The person handing off the work knew something the receiver needed, and the brief, ticket, or message didn't carry it. The receiver gets the conclusion, but not the context or reasoning that made it sensible.

SIGNS YOU’D NOTICE
  • Receivers spend hours rebuilding context before the real work starts.
  • Briefs say what to do but not why.
  • Rework traces back to information the sender had all along.
HOW TO OBSERVE IT

Who: the last two people who received this work. Ask: "What did you have to go and find out that the person before you already knew?" Count: hours spent rebuilding context on the last three handoffs. You're probably looking at this pattern if the missing context existed and wasn't passed on. Probably not if nobody had it. If not, compare it with Past work can't be found.

EASY TO CONFUSE WITH

Nuance gets squeezed out. That one happens as a finding travels upward to people who need a shorter version. This one happens between the people doing the work.

MOVES TO TRY
Start hereClosed-loop callouts

On important handoffs, the receiver says back what they have taken on.

Give Context, Not Control

Before you delegate a decision, hand over the full context behind it. The goal, the constraints, what matters. Then let them decide.

RESEARCH BEHIND THISEmerging

A structured handoff script ending in a read-back cut medical errors by about 23% across nine hospitals and 10,740 admissions (Starmer and colleagues, 2014). Read-backs are standard practice in aviation and surgery. Emerging for the script: one large, well-designed study. Established pattern for read-backs.