In fast‑moving product groups the invisible cost of “waiting” often dwarfs the visible cost of “doing.” When a handoff stalls, the downstream person’s clock stops, but the upstream person’s effort keeps ticking, creating a hidden queue that swells with partially finished work. The queue’s length is not measured in story points; it lives in idle meetings, re‑writes, and the mental load of “what if I finish this and the spec still changes?” Over time, the queue becomes a self‑reinforcing bottleneck: the more work that piles up, the more people protect their own time by adding buffers, and the organization gradually tolerates longer delays as normal.

At a mid‑size fintech, the design team produced high‑fidelity mockups only after the engineering sprint had begun. Engineers built scaffolding, wrote tests, and even shipped a beta, only to discover the UI required a different interaction flow. The product lead spent three sprint cycles re‑prioritising, while the engineers’ velocity visibly dropped, and the quarterly roadmap slipped. The root cause was not a lack of talent but a mis‑aligned handoff schedule that forced the downstream team to wait on upstream output, inflating coordination drag across the whole product line.

When the company finally instituted a “design‑first sprint” rule—no code starts until the mockup is signed off—the waiting desk cleared. Velocity rose, defect rates fell, and the same roadmap was met on time. The lesson is that the hidden queue of waiting, not the visible work, often determines whether teams sprint or stall.