What actually counts as a handoff?
A handoff is any point where the system stops carrying the information and a human has to carry it instead. Reading a number off one screen and typing it into another is a handoff. Forwarding a photo to a manager is a handoff. Telling a crew lead the gate code over the phone is a handoff.
Most owners underestimate the count. A single job from first call to final payment routinely passes through fifteen to thirty of them.
Why handoff cost is larger than the time spent
- Delay: the receiver acts only when they next check the channel.
- Loss: some transfers never happen — the message that was meant to be sent later.
- Distortion: each retelling drops detail and adds interpretation.
- Rework: the downstream person asks upstream to repeat it.
- Attention: the sender was pulled out of another task to perform the transfer.
How do you measure it?
Take one recent job. List every point where a person moved information. For each, note how long the work waited before the receiver acted. That waiting time — not the typing time — is the real number.
Then estimate how often each transfer fails. Even a three percent failure rate across twenty handoffs means most jobs contain at least one break.
Which handoffs should be removed first?
- The ones that repeat on every single job.
- The ones that happen after hours, when the receiver is unavailable.
- The ones where the information already exists somewhere in a system.
- The ones whose failure is invisible until a customer complains.
What replaces a handoff?
Shared state replaces most of them. If both parties read the same record, nothing needs to be transferred — the information never changes hands.
Events replace the rest. Instead of a person remembering to notify someone, the change itself triggers the notification.