The Handoff Is Where Work Gets Lost

The customer rang on Monday and asked for a price for a small job. The owner was out, so the person who answered wrote the details on a slip of paper and left it on the desk. The owner came back, read the slip, and meant to ring the customer that evening. That evening was busy. On Tuesday the slip was under another piece of paper. On Wednesday the customer rang a different business, got a price the same day, and took the job there. Nobody in the first business had refused the work. Nobody had even said no. The work was simply handed from one person to another, and somewhere in the handoff it stopped moving.

This article was drafted with AI assistance. It is written in plain English for people who run businesses, not for people who build software, and it makes no claim about any particular product. It is about the gaps between one step and the next, and why so much work is lost in them.

The gap is not the work

Most small businesses do not lose work because the work itself is hard. They lose it in the gaps: between the phone call and the reply, between the quote and the booking, between one person finishing a piece and another person starting the next. Each piece, on its own, is simple. Somebody takes a message. Somebody else is meant to act on it. The trouble is that "somebody else" is not a person, and "meant to" is not a plan.

The owner in the story above did not forget on purpose. He was doing the work in front of him, and the slip of paper had no owner once it left the desk. The person who took the message had done her part. The owner had not yet started his. In between, the job belonged to nobody, and jobs that belong to nobody do not get done. They wait. And while they wait, the customer, who has no way of seeing the slip of paper, reasonably decides that silence means the business is not interested.

This happens in every kind of small business. A request comes in by message and is read on a phone, then buried under newer messages. An invoice is promised and the promise lives only in somebody's head. A supplier is meant to be chased, a form is meant to be sent, a customer is meant to be told a date, and each "meant to" depends on somebody remembering at the right moment, in the middle of a busy day. None of these are big failures. They are small gaps, and a business can have a dozen of them open at once without noticing, until a customer goes elsewhere or a bill goes unpaid.

Why handoffs fail

Handoffs fail for three plain reasons, and all three are ordinary.

The first is that nobody owns the next step. A job is passed on, but nobody is named as the person who will do the next thing, or by when. "Can you look at this?" is not an assignment. It is a hope. If two people think the other one has it, nobody has it.

The second is that the details live in too many places. The request is in a message, the price is in a notebook, the customer's number is on a slip of paper, and the date agreed is remembered, roughly, by one person. To do the next step, somebody has to gather all of that again. When gathering it takes effort, the step gets put off, and putting it off once makes it easier to put off again.

The third is that nobody checks. There is no moment in the day when somebody looks at everything waiting and asks the plain question: what is stuck, and who is holding it? Without that check, a stuck job looks exactly like a job that is being handled. It sits quietly, looking busy, until the customer rings to ask what happened, or does not ring at all.

Notice what is not on that list. It is not laziness, and it is not a lack of care. The people in these stories care about the work. The system around the work — if it can be called a system — simply has no place where a handoff is recorded, owned, and checked.

One list, one owner, one next step

The fix is smaller than most owners expect, and it does not need new software to start. It needs one list, kept in one place, where every open job has three things: a named owner, a single next step, and a date for that step. Not a description of the whole job. Just the next thing that has to happen, who will do it, and when.

The list is checked once a day, for ten minutes, at the same time. The question for each item is short: did the next step happen, and if not, what is the next step now? A job that has no next step, or no owner, or no date, is not a job in progress. It is a job waiting to be lost, and the check is the moment to catch it.

The rule for handing work over is just as plain. A handoff is not finished when the details are passed on. It is finished when the other person has accepted it: they know what the next step is, they know it is theirs, and the list says so. A message sent is not a handoff. A message understood and owned is. That one change — asking for a plain "got it, I'll do it by Thursday" instead of assuming — closes most of the gaps that lose work.

A careful system can help with the keeping part. It can hold the list in one place, keep the details together, and put the stuck jobs in front of the owner at the daily check, instead of leaving them to memory. That is the part a system is good at: remembering, across many jobs, without getting tired or distracted. The handoff itself, and the judgement about what the customer needs next, belong to a person. A customer does not care how tidy the list is. She cares that somebody owned the next step, and did it, and told her.

The short version

Work is rarely lost while somebody is doing it. It is lost in the handoff: passed on without an owner, without a next step, or without a date, and never checked again. Keep one list in one place, give every open job a named owner, a single next step, and a date, and check the list once a day. A handoff is only finished when the next person has accepted it. Most lost work is not refused work. It is work that belonged to nobody for just long enough to disappear.

Ready-made AI agents for small businesses, built in public.

Originally published on Dev.to: https://dev.to/elarigent/the-handoff-is-where-work-gets-lost-3oji