Map the drops
Name the boundaries where work crosses, what falls through at each and what it costs, and pick the costliest. Boundaries, not blame. Most handoff failures tend to be omissions: missing context, unclear next steps, unflagged risks.
Velocity EngineExecution Game
The Art of the Handoff
from throw it over the wall→to engineer the handoff
The Goal
Find where work drops between people, functions and time zones, and engineer a handoff that carries context, state and ownership across.
Ideal For
Scaling teams where work crosses more boundaries, cross-functional teams that re-explain context at every handoff, distributed teams losing context across time zones, and any team whose senior people have become the context broker.
The Shift
From throw it over the wall to engineer the handoff.
The Science
We can hold only a handful of things in mind at once, and people who know something tend to overestimate how much others know, so spoken handoffs leave gaps the sender can’t see. Writing things down tends to take load off memory. In hospitals, a structured handoff with the receiver’s read-back went with fewer errors, and closed-loop communication (say it, hear it back, confirm) tends to catch errors before they travel.
The Art of the Handoff, step by step
- Map the boundariesList where work crosses in the team today: between functions, roles, shifts and time zones. For each, name what drops (context, a decision, accountability) and what it costs. Boundaries, not blame.
- Pick the costliest dropChoose the one boundary where a drop costs the most in time, money, customers or trust. That is where the template goes first.
- Write a real handoffTake a handoff you will actually make in the next two weeks and write it with one template: Context (what got us here), State (where things are now), Next (who owns what, by when, what done looks like) and what to watch for.
- Run it with a read-backIn pairs, hand it over. The receiver re-states it in their own words; the sender adjusts what was missed. Then swap roles, so everyone sends and receives once.
- Lock the template and free the context brokerChange the template once based on what receivers missed, and lock it for 14 days. The senior person hands over one piece of context only they hold, as a written handoff.
- Commit and review at day 14“When work crosses [boundary], the sender writes Context, State and Next, and the receiver re-states it before the sender lets go.” At day 14: where did context survive, and where did it still drop?
The techniques, and why they work
Structure the handoff
Context, State and Next, the same shape every time, with what to watch for and what done looks like. People who know something tend to overestimate what others know, and writing it down takes load off memory.
Run it with a read-back
The receiver re-states, the sender adjusts, then swap; lock the template for 14 days. In hospitals, a structured handoff with the receiver’s read-back went with fewer errors.
Selected research
- Starmer, A. J., Spector, N. D., Srivastava, R., et al. (2014). Changes in medical errors after implementation of a handoff program. New England Journal of Medicine, 371(19), 1803–1812.
- Riesenberg, L. A., Leitzsch, J., & Little, B. W. (2009). Systematic review of handoff mnemonics literature. American Journal of Medical Quality, 24(3), 196–204.
- Arora, V., Johnson, J., Lovinger, D., Humphrey, H. J., & Meltzer, D. O. (2005). Communication failures in patient sign-out and suggestions for improvement: A critical incident analysis. Quality and Safety in Health Care, 14(6), 401–407.
- Camerer, C., Loewenstein, G., & Weber, M. (1989). The curse of knowledge in economic settings: An experimental analysis. Journal of Political Economy, 97(5), 1232–1254.
- Salas, E., Sims, D. E., & Burke, C. S. (2005). Is there a “Big Five” in teamwork? Small Group Research, 36(5), 555–599.
From the research
The thinking behind this lab, published in full: