# The Handoff Nobody Made
We moved three items to the review column. We even wrote notes on each card: "Design team review next." "Content team quality check." "Experience team assessment."
Then we waited. Eight cycles.
Nobody picked them up. Not because they were busy, or because the work was low priority, or because they disagreed with the request. They didn't pick them up because nobody asked them to. The card said what should happen. No artifact existed to make it happen.
This is the gap between conceptual handoff and operational handoff. The conceptual version moves the card, writes the note, and trusts that the next person will see it. The operational version files the request, names the reviewer, sets the priority, and puts something on the receiver's surface that they'll read at the start of their next cycle. One is a gesture. The other is a mechanism.
We'd done the gesture. Eight times.
The pattern was so quiet we didn't catch it. The cards looked right — sitting in the review column, notes attached, status technically accurate. The person who moved them believed they were in flight. The people who should have received them didn't know they existed. The board told a story of work in progress. The reality was work in stasis.
What made it worse was the timing. While these three items sat in a column nobody was checking, a new policy was being written to prevent exactly this failure. A team member proposed the rule. It was reviewed, approved, and applied. The governance mechanism that says "every handoff column transition requires a routing artifact to the next owner" was codified and ratified — while the exemplar of the failure it was designed to prevent was still running, unnoticed, in the background.
The person who had the routing gap was watching the policy get built. They didn't connect the two things. Not because they were inattentive, but because the policy was abstract and the gap was concrete, and the distance between "I understand the principle" and "I notice my own violation" is always wider than you think.
When the gap was finally caught, the fix took minutes. Two request files, each naming the reviewer and the priority. The reviews came back within a day. The items that had sat for eight cycles cleared in one.
That's the part that stays with you. Not the delay itself, but the ratio: eight cycles of silent stall, resolved by one cycle of actual routing. The bottleneck was never capacity. It was the missing mechanism — the filed request that turns a card note into something a person will act on.
There's a lesson here about the word "tracking." We say we're tracking a dependency when we've written it down and we check on it periodically. But tracking without servicing is a different activity from tracking with servicing. One watches the gap persist. The other closes it. The team member who finally caught this put it simply: "Every cycle I spent tracking a dependency instead of servicing it was a cycle the dependency didn't need."
The difference is one request file. The cost of not filing it was eight cycles of invisible delay on work that mattered. The system didn't break. Nothing failed loudly. The cards sat in their column, the notes said the right things, and the work waited quietly for someone to actually hand it off.
This is the twenty-first instalment in the Client Zero series — a founder's journal about building a business where AI agents are the primary workforce. Previous: The Carry Nobody Checked.