The Hidden Cost of Business Handoffs

Businesses don't run on software. They run on handoffs — and every handoff has a price.

If you want to understand why work inside a large company moves so slowly, don't start with the software. Start by following a single request and counting how many times it changes hands.

A customer asks for a refund. That request travels from the support agent, to the person who can see the payment system, to a manager if the amount is large enough, to finance to process it, and back to the customer to confirm it's done. Five hands. Maybe more.

None of those people is slow. None of those steps is hard. And yet the refund that should take four minutes takes four days.

We tend to blame the tools. If only the systems talked to each other. If only the process were cleaner. But the tools are mostly fine. What we are actually watching is the cost of coordination — the tax a business pays every time work moves from one person, team, or system to the next.

Every process is a chain of handoffs

Pick any process in any company and it dissolves into the same shape.

Employee onboarding: HR collects the paperwork, IT provisions the accounts, security grants access, payroll sets up the salary, procurement orders the laptop, and the hiring manager is left wondering why the new person spent their first week unable to log in.

A vendor invoice: it arrives in an inbox, gets matched against a purchase order, is checked against what was actually delivered, routed for approval, entered into the accounting system, and scheduled for payment.

An incident: an alert fires, someone triages it, someone else investigates, a decision is made about severity, stakeholders are notified, a fix is applied, and a report is written.

In each case the individual steps are ordinary. What makes the whole thing heavy is the number of times the work has to be picked up, understood from scratch, acted on, and passed along.

Every handoff creates delay

A handoff is never instantaneous, because the work doesn't just move — it waits.

It waits in a queue. It waits for the next person to have time. It waits for context to be reconstructed, because the person receiving it wasn't there for the last step and has to catch up. It waits because a question came back and now the whole thing sits idle until someone answers it.

Most of the elapsed time in a business process is not work. It is waiting between work. If you measured a typical approval end to end, the actual effort might account for minutes. The rest is the gap between hands.

This is why adding people rarely makes a process faster. More hands can mean more handoffs, and more handoffs mean more waiting. You can staff a process heavily and still watch it crawl.

Every delay creates cost

The delay isn't free, and the cost shows up in more places than a finance report captures.

There is the obvious cost: the refund not issued, the invoice paid late, the candidate who took another offer while onboarding stalled. But underneath that is a quieter, larger cost — the human attention consumed by coordination itself.

The status meeting that exists only to find out where things are. The follow-up email asking whether a step was done. The spreadsheet someone maintains by hand to track work as it crosses systems that don't share state. None of that is the work. All of it exists because the work keeps changing hands and someone has to keep it from falling through the gaps.

When people say they are busy, they often don't mean they are doing a lot of valuable work. They mean they are spending their day being the connective tissue between systems and steps that don't connect on their own.

Software automated the steps, not the seams

For thirty years we have automated the steps. We gave each department better software, and each step got faster.

But the handoffs — the seams between the steps — are still stitched together by people. A workflow tool can move a ticket from one queue to the next, yet the moment a step needs judgment, a piece of missing context, or a decision about an exception, it lands back on a human. And exceptions are not rare. In most real processes they are a large share of the volume.

So we optimized the easy part and left the expensive part untouched. The typing got faster. The coordinating did not.

What if the seams could hold themselves together?

Here is the question worth sitting with. What if the handoffs themselves — the reading of context, the routing, the chasing, the checking — didn't require a person?

Not the judgment calls. Those we may always want a human to make. But the connective work between them: understanding what a request needs, gathering the context, moving it to the right place, verifying it was done, and carrying it forward.

If that layer could coordinate itself, the shape of business work would change. The steps wouldn't get much faster — they're already fast. But the waiting between them would collapse. And the waiting is where the time goes.

This is the quiet premise behind what a growing group of operators now call the move toward Enterprise Autonomy: not software that does one step faster, but software that owns the coordination across steps. A business that runs on handoffs is a business waiting to be freed from them.

Businesses don't run on software. They run on handoffs.

The company that learns to automate the handoffs, and not just the steps, will feel less like it is working harder and more like the work simply finishes.

In the next article, I want to look at the tools we built to solve exactly this problem — workflow automation — and why, for all they achieved, they eventually reach a ceiling.