When a business decides to automate something, it almost always picks a task. Generating the invoice. Sending the reminder. Filling in the form. These are visible, bounded and easy to point at, and automating them feels like progress. It usually is, a little. But the task was rarely the expensive part.
Watch where a process actually loses time and it is almost never inside a step. It is between them. The enquiry that sat in an inbox for two days before anyone noticed. The job that was finished but not invoiced because finishing and invoicing belong to different people. The approval that waited for someone to come back from leave. Each step, taken alone, is quick. The waiting between steps is where the days go.
What a handoff is
A handoff is any moment where work changes hands: from one person to another, from one tool to another, from one stage of a process to the next. Every handoff needs three things to happen. Someone has to notice the work is ready to move. Someone has to move it, which usually means re-entering it somewhere. And someone has to pick it up on the other side. Each of those is a place for work to stall, get lost, or arrive incomplete.
Most businesses have far more handoffs than they think, because tools create them. A booking made in one system has to become a customer in another and a line in a third. Every one of those boundaries is a handoff, and every one of them is currently done by a person copying and pasting, or by nobody, until something goes wrong.
A process is only as fast as its slowest handoff, and the slowest handoff is usually the one nobody owns.
Why task automation disappoints
Automate a task and you speed up a step that was already fast. The invoice that took ten minutes to write now takes none. The process it belongs to still takes a fortnight, because the invoice still waits for someone to remember that the job is done, and the payment still waits for someone to notice it has not arrived.
Worse, task automation can add handoffs. A new tool that generates documents beautifully is another place work has to be moved into and out of. The business ends up with a faster step and a longer process, and concludes that automation does not work for them.
What automating a handoff looks like
The shape is always the same: remove the noticing, remove the re-entering, and make the pickup automatic.
- The trigger replaces the noticing. When the job is marked complete, the invoice is created. When the enquiry arrives, the right person is told. Nobody has to remember, because the system does not forget.
- The shared record replaces the re-entering. The booking, the customer, the job and the invoice are one record, not four copies. There is nothing to copy across because there is no “across”.
- The queue replaces the pickup. Work that needs a human lands in one place, in order, with everything attached. The person opens one list rather than three inboxes.
Do this to one handoff and one part of the business gets quietly faster. Do it to every handoff in a process and the process changes character: it stops being a sequence of people remembering things and becomes something that runs.
Choosing where to start
Pick the handoff that hurts, not the task that is easy. Three questions find it quickly:
- Where does work most often wait for someone to notice it?
- Where is the same information typed into a second system by hand?
- Where does a customer wait while the business talks to itself?
The answer to at least one of those is usually obvious to everyone in the business and invisible in every tool, because tools measure their own steps and nobody measures the gaps. That gap is the first thing to automate, and it is almost never the thing on the automation vendor’s feature list.
Automation done this way is less visible than a clever bot and far more valuable. Nothing dramatic happens. Work simply stops waiting.