Think about the last thing your team shipped that took far longer than it should have. If you trace it back honestly, the delay probably wasn’t in the work itself. Nobody spent three days writing the proposal or two days editing the photos. What actually happened is that the proposal sat finished in someone’s drafts for a day before it got sent for review, then sat in the reviewer’s queue for another day because they didn’t know it was waiting, then bounced back with a small change that took ten minutes to make once someone finally noticed. The work took an hour. The handoffs took a week.
This is the quiet tax on almost every small team. We obsess over how fast individuals move, but most of a task’s life is spent not being worked on at all — it’s spent waiting in the gap between one person finishing and the next person starting. Those gaps are invisible, which is exactly why they’re so expensive. You can’t fix what you can’t see. So the first job is to drag handoffs out into the open.
Handoffs Are Where Work Goes to Wait
A handoff is any moment a task changes hands: designer to reviewer, sales to fulfillment, writer to editor, tech to front desk. Each one is a tiny transfer of responsibility — and every transfer is a chance for the work to stall. The person handing it off assumes the receiver knows it’s coming. The receiver assumes someone will tell them when they’re up. In between those two assumptions, the task sits.
The reason this hurts so much is that the waiting compounds. A job that passes through four people isn’t just four bits of work — it’s four handoffs, each with its own little pause. If every handoff adds even half a day of dead time, you’ve lost two days on a task that involved maybe three hours of actual effort. Speeding up the people won’t help; the people were never the problem. The gaps between them were.
The Three Ways a Handoff Fails
Once you start watching handoffs, you’ll notice they break in one of three predictable ways. Naming them makes them easier to spot.
It gets dropped. The task is finished on one side, but it never actually reaches the next person. It’s sitting in an inbox nobody checks, a shared folder nobody opens, or a verbal “I’ll pass it along” that never happened. The work is done and still going nowhere.
It gets delayed. The receiver knows about it eventually, but not promptly. It lands in a pile with everything else and surfaces whenever they happen to look. A five-minute review waits a day and a half not because it’s hard, but because nobody knew it was urgent or even present.
Nobody owns it. The most insidious failure: the task is between people, so it belongs to no one. The sender thinks their part is done; the receiver hasn’t accepted it yet. It falls into the seam between two roles and just… hovers, until someone finally asks “whatever happened to that?”
Make the Next Owner Obvious
The single most effective fix is also the simplest: every task should have exactly one clearly named owner at all times, and when it changes hands, the new owner’s name changes with it. No task should ever be in a state where two people could each reasonably assume the other has it.
On a kanban board this is natural, because a card can only sit in one column and carry one assignee. When the designer finishes, they don’t just mark it done — they move the card to the next stage and reassign it to the reviewer. Now the board itself answers the question “whose turn is it?” for every piece of work in flight. That’s a big part of why moving from scattered notes and messages to a shared board is worth the small effort — it turns invisible ownership into something anyone can see at a glance. If your team is still tracking work across sticky notes, chat threads, and inboxes, getting it onto one board is the foundation everything else here builds on.
Give the In-Between a Column of Its Own
Most boards have columns for doing — To Do, Doing, Review, Done. But the dangerous moment isn’t when someone is doing the work; it’s the instant between stages, when the first person is finished and the second hasn’t started. If your board doesn’t have a home for that moment, the task hides inside a column labeled “Doing” long after doing has stopped.
The fix is to make the handoff itself a visible step. Add a short buffer column — call it “Ready for Review,” “Ready for Fulfillment,” “Waiting on Client,” whatever fits — that sits between the person who finished and the person who’s next. Now a card parked there is a loud, obvious signal: this is done on one side and waiting to be picked up. Handoffs that used to happen in the dark now happen in a lit column everyone can see. This is closely related to managing dependencies on your board — a handoff is just a dependency between two people, and the same visibility that untangles dependencies is what rescues handoffs.
Write the Handoff Note
Moving a card to the next person solves where the work is. It doesn’t solve whether the next person can actually start. Half the delay in a handoff is the receiver picking up a task and realizing they don’t have what they need — the file, the context, the one decision that was made in a meeting they weren’t in. So they message back, wait for an answer, and the task stalls again.
Kill that round-trip with a habit: whenever you hand a task off, leave a two-line note on the card. What’s done, what the next person needs to do, and anything they’d otherwise have to ask for. It takes fifteen seconds and it means the receiver can start the moment they see it rather than starting a conversation. Agree as a team on what “ready to pass” actually means for each stage — a shared, written standard for handing off is the same idea as a definition of done, just applied to the moment between people instead of the end of the line.
Watch for Cards That Quietly Age
Even with owners, columns, and notes in place, some handoffs will still slip — a reviewer gets buried, a client goes quiet, a card lands in a buffer column on a Friday and nobody looks until Wednesday. The last piece of the puzzle is noticing when a task has been waiting too long before someone asks about it in frustration.
The signal to watch is card age: how long a card has sat in one place without moving. A card parked in “Ready for Review” for three days isn’t a review problem, it’s a handoff problem — the work is done and rotting in the gap. Glance at your board once a day and look for the cards that haven’t budged, especially the ones sitting in your in-between columns. Those are your stalled handoffs, and a thirty-second nudge clears most of them. If certain handoffs are genuinely time-sensitive, give them a fast track so they don’t wait behind routine work at all — the same logic behind running an expedite lane for urgent requests.
The Takeaway
Your team is probably faster than your delivery times suggest. The lost hours aren’t in the work — they’re in the seams between people, where tasks wait in silence for someone to notice them. You don’t fix that by pushing people to hurry. You fix it by making every handoff visible: one clear owner at all times, an explicit column for the in-between, a two-line note so the next person can start cold, and a daily glance for cards that have quietly aged. Do that, and the gaps that used to swallow days shrink to minutes. A simple shared board won’t do the work for you — but it will make sure no piece of work ever again gets stuck waiting for someone who didn’t know it was their turn.