The handoff is where work goes to die

Look at any task that died in your company, and trace it backward. The contract didn’t stall because the lawyer couldn’t draft it or because finance couldn’t approve it. It stalled in the inch between “draft is ready” and “finance has it”, a sentence said in a meeting that never became a message, a file attached to an email nobody opened, a “can you take this from here” that landed in a chat at 6pm on a Friday. Each person did their part. The work still died.

It didn’t die at a desk. It died in the corridor between two desks.

That corridor has a name in every operations review, even if nobody says it out loud: the handoff. And it’s the single most expensive place in any company, because it’s the one place no single person is responsible for. This post is about why that gap is where work goes to die, and what it takes to build something that lives there.

Nobody owns the inch between two people

Here’s the model every org chart quietly assumes: work is a relay. Someone runs their leg, hands the baton, and someone else runs the next leg. Draw it as boxes and arrows and it looks clean, sales to onboarding, onboarding to delivery, delivery to billing. Each box has an owner. Each owner has a job.

The arrows have no owner.

That’s the flaw hiding in plain sight. We staff the boxes obsessively, we hire for them, review them, build whole teams around them, and we staff the arrows with nothing but hope. The assumption is that the baton passes itself: that “I sent it over” and “they received it” are the same event. They are not. The most reliable thing about a handoff is that one side believes it’s done and the other side doesn’t yet know it’s their turn.

So the work doesn’t fail loudly. It just sits. In the inbox of someone on vacation. In a thread that scrolled out of view. In a verbal promise that felt like a commitment to the person who made it and like background noise to the person who heard it. Nothing breaks inside a lane; everything breaks in the gap between two lanes. And the gap is exactly where we’ve decided no one needs to stand.

The dropped baton has a shape

Once you start looking for it, the failure has a consistent anatomy. It isn’t random. A handoff dies in one of a few specific ways, and they rhyme across every team and every tool.

The first is said, not written. The decision happened out loud, in a meeting, on a call, in a hallway, and felt so settled that nobody captured it. A week later, two people remember it two different ways, and the version that survives is whoever’s louder, not whoever’s right.

The second is sent, not received. The file went out. The message was typed. But it landed in a stream of forty others, and “I sent it” got mistaken for “they have it.” The sender’s job felt finished the moment they hit send. The receiver’s job hadn’t started, because nothing told them it was theirs now.

The third is done on my side. Each person genuinely completed their part, and assumed the next part was either automatic or someone else’s. The draft was ready, so the lawyer moved on. Finance never knew it existed. Both are blameless. The work is still dead.

The fourth is the cruelest: waiting on each other. Two people are each certain the ball is in the other’s court. Nobody is being lazy. Both are being polite. The task sits in a standoff that neither will break, because breaking it means admitting you weren’t sure whose turn it was.

None of these is an intelligence failure. None is a competence failure. Every one is a gap failure, a moment where the work needed a hand to carry it across, and the only hands available had already let go.

Why we keep trying to fix this with reminders

The instinct, when handoffs fail, is to add a process. A checklist. A status field. A rule that says “always cc the next person.” And it helps, a little, for a while, until it doesn’t.

The naive fix treats the gap as a memory problem. If people just remembered to pass the baton properly, the thinking goes, it wouldn’t drop. So we install reminders. We make a Kanban board with a column called “Handoff.” We write a runbook. We ask everyone to be more disciplined about closing the loop.

But the gap isn’t a memory problem. It’s an ownership problem wearing a memory problem’s clothes. A reminder still puts the responsibility on a person, usually the busiest person, at the worst moment, to notice that a thread went quiet and chase it down. You’ve automated the nag. You haven’t automated the catch. And the catch is the part that was hard: noticing that something which should have moved hasn’t, while it’s still early enough to matter.

A checklist tells you what should happen. It has no idea whether it did.

That’s the ceiling every process hits. A status field can say “in review,” but it can’t notice that “in review” hasn’t changed in nine days while everyone assumed it was moving. The board shows you the boxes. It still can’t see the arrows. Which is why the most disciplined teams in the world still lose work in the gap, they’ve optimized the lanes to a mirror shine and left the corridor dark.

A promise made in one lane, dropped in the next

Here is the failure in its everyday clothes. A customer is mid-purchase, almost in, and asks for one thing before they’ll commit: “Can my data import from our old system on day one?” The salesperson, wanting the yes, says yes, and means it. It’s a reasonable promise. Onboarding does this all the time. The deal closes that afternoon, everyone’s pleased, and the promise travels from the lane where it was made to the lane where it has to be kept.

Except it doesn’t travel. It was said in a call. It lived in the salesperson’s head and the customer’s expectation, and nowhere else with a timestamp.

So how do teams patch this today? They ping. The salesperson drops a line in the onboarding channel, “heads up, new customer needs the day-one import, told them we’d handle it”, and maybe tags whoever’s on rotation. A plus-one gets added to the thread. Someone reacts with a thumbs-up. It feels closed. The baton, to the person who threw it, is now in someone else’s hands. They go back to selling.

But the ping is not the catch. The ping is just another handoff wearing a helpful face. It can be skimmed past at the bottom of a busy channel. The tagged person can be out that week, and the thumbs-up can come from someone who read it but doesn’t own it. Nobody confirmed they had it, because a reaction emoji is “sent, not received” with a friendlier icon. And critically, nothing is watching whether the promised thing actually gets scheduled before the customer logs in expecting it. The promise made in the first lane is now a quiet liability in the second, and the first person who’ll learn it was dropped is the customer, on day one, when the import isn’t there.

That’s the cruelty of it. The patch that was supposed to close the gap is a gap. You forwarded the risk; you didn’t retire it.

An always-on coworker living between the two lanes treats that promise as a single object with two ends, not as a message that someone hopefully caught. It hears the commitment when it’s made, “day-one import”, and turns the said-out-loud thing into a written, tracked obligation with a deadline tied to the customer’s start date. It confirms the receiving side actually picked it up, instead of trusting a reaction. And if the import isn’t scheduled while there’s still time to schedule it, it doesn’t post a fifth reminder into the same noisy channel, it routes the task to the right hand, drafts the setup request, and surfaces the standoff loudly enough that someone breaks it before the customer ever feels the drop. Nothing breaks inside a lane; everything breaks in the gap between two lanes, and a promise is just a handoff that hasn’t found its second hand yet.

What it takes to stand in the gap

So if a person can’t reliably own the inch between two desks, and a checklist can’t see it, what can? Something that is always running, sees both sides of the handoff at once, and is allowed to act when the baton stops moving.

That’s a short sentence with three hard requirements buried in it, and they’re worth pulling apart.

It has to be always on. A handoff dies in the hours when no human is watching it, overnight, over a weekend, in the lull after the meeting ends and before anyone opens their task list. A system that’s awake in those hours sees the silence for what it is: not “everything’s fine,” but “nothing has moved when something should have.”

It has to see both lanes. The whole reason the gap is invisible is that each person only sees their own side. The sender sees “sent.” The receiver sees nothing yet. Only something watching both the outgoing message and the incoming queue at the same moment can tell that the two haven’t connected. The handoff only exists as a single object if something holds both ends of it.

And it has to be allowed to act, to close the loop, not just observe it open. Noticing the dropped baton is worth little if all it can do is file another reminder onto the same overloaded person. The point is to carry the work the last inch itself: route it to the right next hand, draft the message that should have been sent, surface the standoff so someone can break it, log the decision that was only said out loud.

Put those three together and you don’t have a smarter checklist. You have something standing where no one was standing before, in the corridor, watching the batons, catching the ones that drop. Nothing breaks inside a lane; everything breaks in the gap between two lanes, and now, for the first time, the gap has someone in it.

The gap is most of the work

Here’s the part that reframes the whole company once you see it. We tend to think the work is the lanes, the drafting, the building, the deciding. The handoffs feel like connective tissue, the boring plumbing between the real parts.

It’s the other way around. In a company of any size, an enormous share of what slows everything down lives in the transitions, not the tasks. Suppose a deal touches eight people on its way from “interested” to “signed.” That’s seven handoffs, seven inches where it can stall, against eight stretches of actual work. The work each person does might take an hour. The wait between them can take days. The lanes are fast. The gaps are where the calendar disappears.

This is why “just hire great people” never fully fixes it. Great people make great lanes. They don’t make the corridor between their lane and yours any shorter, because that corridor isn’t anyone’s lane. You can staff a company entirely with your best operators and still watch a contract die in the pass from one to the next, not because either is bad, but because the pass itself was nobody’s job. The handoff is the one role no résumé describes.

The turn: the corridor was always the lonely part

Ask anyone who’s held a company together what actually exhausted them, and it’s almost never the work in their own lane. They liked that part. That part they were good at. What ground them down was being the human glue, the one who remembered that the thing finance was waiting on never got sent, who pinged the designer because the brief had gone quiet, who carried the loose ends in their head across every gap because they’d learned that if they didn’t, the gaps would swallow them.

That person is doing a real job. It’s just an invisible one, and a brutal one, and the wrong one for a human to hold. Vigilance across every corridor in a company is not a skill you get better at, it’s a weight you carry until you drop something, and then carry the guilt of the drop on top of it. We’ve been asking our most capable people to spend their best energy being a relay system made of memory and anxiety.

The promise isn’t a faster lane. It’s that the corridor finally has a tenant. Something awake in the gap, holding both ends of every handoff, catching the baton before it hits the floor, so the work stops dying in the inch between two people, and the person who used to live in that inch gets to come back inside and do the work only they can do.

That’s the role we keep forgetting to hire for, because no person can really hold it. The gap was never a discipline problem. It was a vacancy.

---

That’s what we’re building at Apollo Space: not a better box for each lane, but a coworker that lives in the corridor between them, awake when the office is dark, holding both ends of every handoff. If the most tiring part of your week is being the human who remembers what hasn’t moved yet, that was never supposed to be your job. The inch between two people finally has someone standing in it.