In 30 seconds

A handoff is where work passes from one person or system to another. Mark each one on your map and note what travels across it and how the receiver knows it is their turn. Handoffs are where most delay and lost context hide.

Why this comes up

The steps in a workflow usually work. The gaps between them often do not. A request sits untouched because it moved to someone who did not know it had arrived, or arrived without the information the next step needed.

If your map shows steps but not handoffs, it hides the part of the workflow most likely to fail.

Spot the handoffs

Look for every point where work crosses a boundary:

  • one person to another
  • one team or department to another
  • email to spreadsheet, spreadsheet to a business system
  • an automated step to a human check
  • a human step to an automated one

Each of these is a handoff, even when it feels instant.

For each handoff, record three things

  • What is passed along? The full item, a summary, a link, a verbal note?
  • How does the receiver know it is ready? A notification, a shared queue, or nothing?
  • What happens if the receiver is unavailable or misses it?

That third question is where you find the silent failures.

A small example

A quality report is emailed from the factory to the office. The map originally showed one arrow labelled "send report."

Mapping the handoff properly reveals: the report is a PDF attachment, the office only processes it when someone happens to open the shared inbox, and if that person is on leave the report waits. The arrow was hiding a two-day delay and a single point of failure.

Why this matters for AI

An AI step often produces a result instantly, then hands it to a person or another system. If that handoff is weak, the speed of the AI is wasted. Designing the handoff is frequently more valuable than speeding up the step before it.

What this does not solve

Mapping handoffs shows you where work stalls. It does not fix an overloaded receiver. If the next step is a genuine bottleneck, a cleaner handoff only makes the queue visible, which is still useful.

Good enough to move on when

  • Every boundary crossing is marked as a handoff.
  • You know what information travels across each one.
  • You know how each receiver is signalled.
  • You know what happens when a handoff is missed.