What does "dropping the baton" mean at work?

It's the moment a handoff fails—when work passes from one person, shift, or team to another and something essential gets lost in the transfer: context, momentum, ownership, or a key detail. Like a relay runner who fumbles the exchange, the team doesn't lose because anyone was slow on their own leg. It loses in the few seconds of the pass itself, which is also where the failure is hardest to see and easiest to pin on whoever happened to be holding it last.

Why do most errors happen during handoffs and not during the work itself?

Because a handoff is where information has to survive a jump between two people who don't share the same context. The Joint Commission's Center for Transforming Healthcare estimates that 80% of serious medical errors involve miscommunication when patients are handed off. The hard part of a job is usually done by a competent person doing their thing; the fragile part is transferring the state of that work to someone who then has to act on it without having lived it. Standardizing the handoff measurably reduces those errors.

How do you reduce handoffs on a remote team?

Mostly, you don't—and trying to is the wrong goal. Handoffs are how teams scale past what one person can do; a relay is fast because it's four handoffs, not one runner. The goal is cleaner exchanges, not fewer. Make each handoff an explicit, bounded moment, pass the context and not just the deliverable, and confirm the receiver actually has it before the sender moves on. Cutting the number of passes usually just creates heroes and bottlenecks.

What should a good handoff include?

Everything the receiver needs to keep running without stopping to reconstruct: why the work exists, its current state, the next concrete action, the known risks, and an explicit signal that it's now theirs. A good handoff is a baton placed firmly in the hand—a self-contained, front-loaded summary—not a link to a long thread the receiver has to excavate. The test is simple: can the next person act on it without having to find and interrupt the last person?

How is dropping the baton different from context switching or Brooks's law?

They're related but distinct. Context switching is the tax one person pays to resume a task after an interruption; it's part of what makes a dropped handoff expensive for the receiver. Brooks's law is about the communication overhead created when you add people to a project. Dropping the baton is narrower than both: it's the specific loss that happens at the moment of transfer between people, and it occurs even at a fixed team size with no interruptions—every shift change and time-zone rollover is a fresh chance to drop it.

Dropping the Baton: Why Fast Teams Still Lose

The fastest men's 4x100-meter relay team in the world keeps losing—and it keeps losing the same way: by dropping the baton. At the 2024 Paris Olympics, the United States, stacked with elite sprinters, was disqualified in the final when, per Yahoo Sports, the second-leg runner "took off too soon and then had to slow down to receive Christian Coleman's handoff as they collided." It wasn't a fluke. The U.S. "hasn't won a medal in the event in 20 years, and it's been 24 years since they won gold"—a drought built on botched exchanges, not slow legs. They dropped the baton in the first round in 2008. They were disqualified for an illegal handoff in 2016. In 2021 they didn't make the final at all.

Here's the part that should worry you: your team is that relay squad. You hired the fastest people you could find, handed them AI to move even faster, and you're still losing time you can't account for—not on the work itself, but in the handoffs between people. This piece is about why teams keep dropping the baton, why the loss is nearly invisible on a distributed team, and how to engineer the one moment that actually decides the race: the exchange.

What the relay actually teaches about handoffs

A 4x100 relay is 400 meters of running, but it isn't decided over 400 meters. It's decided in four windows of 30 meters each—the exchange zones, where one runner hands the baton to the next. Per World Athletics rules, summarized on Wikipedia, the baton must change hands inside that zone (lengthened to 30 meters in 2017 to cut down on disqualifications). Pass it outside and the team is disqualified, no matter how fast anyone ran—what's judged is the baton, not the bodies. The clock doesn't care about your top speed. It cares whether the stick made it across the line.

What makes the exchange so hard is that it's done at a dead sprint, and it's done blind. Wikipedia describes it plainly: "The transfer of the baton in this race is typically blind. The outgoing runner reaches a straight arm backwards... The outgoing runner does not look back." The receiver starts accelerating before the baton arrives, trusting a verbal cue and the timing of a teammate they can't see. The entire technique exists so neither runner has to slow down. Look back to check, and you've already lost a step.

Now the line that should be printed on every org chart. Wikipedia again: "Polished handovers can compensate for lack of basic speed to some extent, and disqualification for dropping the baton or failing to transfer it within the box is common, even at the highest level." Read that twice. A clean handoff can beat raw speed. And the fastest teams on earth drop the baton routinely. The race is not won on the track. It's won—or lost—in the exchange.

Why your team keeps dropping the baton (and never sees it)

Every team has exchange zones; you just don't call them that. Every time a piece of work crosses a boundary—one person to another, day shift to the next, your time zone to a teammate's, design to engineering, sales to delivery—that's a handoff. Those everyday team handoffs are 30-meter windows where the baton can hit the track, and most teams have no idea how many they run per day. Cross the boundary cleanly and nobody notices; fumble it and you're dropping the baton.

The cost is invisible for a specific reason: what travels across the boundary is the artifact, not the run. The receiver gets the finished doc, the closed ticket, the merged branch—the baton—but not the context, the momentum, or the half-formed reasoning that produced it. So they do exactly what a relay runner must never do: they slow down to grab it. They stop to reconstruct what the last person already knew. That deceleration is the drop, and it rarely shows up in any metric.

The most quantified version of this comes from medicine, where the handoff is literally life and death. The Joint Commission's Center for Transforming Healthcare estimates that "80 percent of serious medical errors involve miscommunication between caregivers when patients are transferred or handed off." Eighty percent. The errors don't cluster on the hard diagnosis or the tricky surgery—they cluster at the moment one person hands a patient to another. Handoff communication, in other words, is where the leverage is. Work is no different; it's just less fatal. As one engineer put it on Hacker News, "IT operations will be seen to be responsible for something that was thrown over the wall by developers months ago. And the developers have moved on." The baton hit the track somewhere around that wall, and whoever's holding it when it stops gets the blame.

This is the receiver's tax—a quiet coordination tax that compounds with every context switch the handoff forces on them. It's also why the cost is so hard to bill to anyone: the person who made the messy pass is already three legs down the track.

The case for more handoffs (and the exact condition where it breaks)

Now the honest objection, because the obvious takeaway—"reduce handoffs"—is wrong. Handoffs are not a bug. They're how you go faster than any individual can. No one can run 400 meters at 100-meter speed; the relay exists precisely so four specialists can each run flat-out for a short stretch. Specialization, shift coverage, follow-the-sun development where the work never sleeps—every one of these is a deliberate handoff, and they're how teams scale beyond what one person can carry. A team that refuses to hand off is a team where one hero runs the whole race and collapses. Steelman it fully: the goal is more clean handoffs, not fewer handoffs.

Here's the hidden condition that decides which one you're getting. A handoff adds speed only when the exchange is engineered. Otherwise, every handoff is just another 30-meter window to drop the baton—and every fast individual you add creates more of those windows, not fewer. This is the trap hiding inside the most natural move a leader can make. You hire A-players. You give everyone AI so they ship faster. And the team somehow gets slower, because the bottleneck was never the running.

The data on this is brand new. Atlassian's State of Teams 2026, fielded across 12,035 knowledge workers and 173 Fortune 1000 executives in early 2026, found that "companies have invested billions in AI to help employees move faster. But coordination hasn't kept up, resulting in a fragmentation tax that costs the Fortune 500 $161B each year." Make every runner faster and leave the exchanges untouched, and you don't get a faster team. You get the same number of drops, happening at higher speed.

This is close to, but not the same as, Brooks's law—the rule that adding people to a late project makes it later. Brooks is about the explosion of communication paths when a team grows. The baton drop is narrower and meaner: it's the loss at each transfer of in-flight work, and it bites even when you add nobody. A team of fixed size, running the same handoffs it ran last quarter, loses to those drops every single day.

How to run a clean handoff

Relay teams don't fix drops with pep talks. They drill the exchange until it's mechanical. Here's how to install the same discipline on a team that passes work instead of a baton.

Define the exchange zone. A drop usually starts as ambiguity about who has the baton. Make every handoff an explicit, bounded moment: who is passing, who is receiving, and by when. "Someone will pick this up" is how the stick ends up on the track. Outside the zone is a disqualification, even in the office.
Pass the run, not just the baton. The deliverable is not the handoff. The receiver needs what they can't see: why this exists, what state it's in, what the next move is, and where the landmines are. Write the handoff so they can keep running, not stop to reconstruct. A tight, front-loaded status update is a baton placed firmly in the hand; a link to a 40-message thread is a baton rolled in their general direction.
Earn the blind handoff. Async handoffs are blind exchanges: the receiver has to start before they hold the baton, trusting it will arrive. That trust isn't free—relay teams earn it with thousands of reps of the same motion. Standardize the pass. A known format and a clear cue ("this is yours now, here's everything you need") is what lets someone start running without looking back.
Confirm the grip before you let go. In a relay, the incoming runner doesn't let go of the baton "until the outgoing runner takes hold of it." The receiver has to actually have it. That's the entire point of the readback rule: a handoff isn't complete when you send it, it's complete when the other person confirms they've got it. A pass nobody caught is a pass nobody made.
Drill it, and count the drops. The exchange is a trainable skill with a measurable failure rate—so train it and measure it. The proof is in the medical data: when hospitals rolled out a structured handoff program called I-PASS, medical errors fell 23% and preventable adverse events fell 30%. Nothing about the doctors changed. Only the handoff did. Find where your work stalls at boundaries, and treat each stall as a dropped baton worth preventing.

Why distributed teams drop the most batons

Distance does two cruel things to the exchange: it multiplies the zones and it hides the drops.

On a co-located team, a fumbled pass is loud and instantly recoverable. The receiver is at the next desk; they turn around, ask one question, and the baton is back in motion in seconds. Spread that same team across time zones and the exchange now happens across a gap of hours. The outgoing runner has gone home—asleep, in fact—by the time the receiver reaches back and finds nothing in their hand. The drop is silent. You discover it the next morning, when the work that should have advanced overnight instead sat on the track, untouched.

And async is exceptional at hiding it, because what crosses the distance is always the artifact, never the runner's state. It's the same blind spot that lets busy teams mistake motion for progress and lets the real signal get buried under everything everyone ships. A follow-the-sun workflow can make a team move 24 hours a day—but only if the pass itself is clean; built on sloppy exchanges, it just drops the baton in a different time zone every night.

The fix—and really, the whole game of distributed team coordination—is to make the exchange happen in the open. The baton, the context it carries, and the cue that it's now yours have to live somewhere the whole team can see—not scattered across DMs where a pass gets dropped by default. That's the gap a tool like Coommit is built to close: by keeping the conversation, a live shared canvas, and contextual AI in one workspace, the outgoing and incoming runner are looking at the same thing at the moment of the pass—so the receiver picks up the full context, not just the artifact, and keeps running.

The bottom line

The teams that win relays are not the ones with the fastest legs. They're the ones that don't drop the baton. Your work runs on the same physics: a 4x100 of specialists will lose to a slower, smoother team every time the exchange goes wrong—and the exchange goes wrong constantly, even at the highest level.

So stop optimizing only the running. The race is decided in 30-meter windows you probably aren't measuring—every time work crosses from one person, shift, or time zone to the next. Define those windows. Pass the run, not just the artifact. Confirm the grip before you let go. Do that, and you stop bleeding the speed you already paid for. Because the fastest team on the track still loses if it keeps dropping the baton.