The First Workflow to Automate Is Usually a Handoff

When a team decides to automate something, they almost always point at the work. The data entry. The report. The reply.

Most of the time, the work is not the leak. The handoff is.

A handoff is the moment one step passes to the next — one person to another, one tool to another, one stage to the next. It is the gap between the boxes on the org chart, and it is where almost everything goes to die.

Why handoffs leak

The work inside a step usually has an owner. Someone is responsible for writing the report, answering the ticket, closing the deal.

The space between steps has no owner. That is the whole problem.

A lead converts on the website, then has to get from the form to a salesperson with enough context to be useful. Nobody owns that journey. So it becomes an inbox, then a Slack message, then a mental note, then a missed follow-up.

> The lead did not go cold because the work was hard. It went cold in the three feet between two tools where nobody was standing.

Handoffs leak because they are everyone's job, which means they are no one's job.

Handoffs are where loops actually break

If you map any operating loop, the broken step is rarely Action. The team is usually doing the action fine. The break is almost always in the connective tissue:

• the signal that never reaches the person who acts on it
• the context that does not travel with the work
• the follow-up that depends on someone remembering
• the decision that waits because nobody knows it is their turn

Those are all handoffs. Automating the action step harder does nothing if the leak is the gap before it.

What to automate first

Look for the handoff with three properties:

1. It happens constantly. A daily or hourly gap leaks more than a quarterly one.
2. It loses context. Information exists on one side and arrives incomplete on the other, so someone rebuilds it by hand.
3. It depends on memory. The only thing keeping it alive is a person remembering to push it forward.

That handoff is your first automation. Not because it is the hardest work, but because it is the cheapest fix with the largest leak behind it.

What fixing a handoff actually looks like

It is rarely a big build.

Sometimes it is an integration that carries context from one tool to the next so nobody retypes it. Sometimes it is an automatic routing rule with a follow-up attached. Sometimes it is a small agent that watches for the signal and makes sure it lands with the right person, with everything they need to act.

The result feels disproportionate to the effort, because you did not add capacity — you stopped a leak that was draining capacity every single day.

The reframe

Stop asking "what work can we automate?"

Start asking "where does our work fall on the floor between steps?"

The first question gets you a faster version of a broken process. The second question gets you the handoff that, once closed, makes the whole loop run.

Tell us about the handoff that keeps dropping. It is almost always the first thing worth fixing.

— The Slateworks Operator