Teams assume that once a backlog item is marked ready, the next step will happen automatically, but the real bottleneck is often a single person whose implicit authority stops progress without anyone noticing. That person’s “no‑comment” stance is read as a tacit approval, yet the downstream engineers keep waiting for a signal that never arrives, so they start padding their own tasks instead of moving the work forward.

The pattern thrives in organizations that reward seniority over velocity, because the gatekeeper’s silence protects their relevance and shields them from blame if the feature later fails. A vivid illustration comes from a streaming service where a well‑known product lead consistently ignored design reviews; the feature team spent weeks polishing UI mockups while the actual implementation never left the planning board, ultimately missing a critical market window.

When the silence finally broke, the team scrambled to re‑engineer a half‑built product, wasting talent and eroding trust across the squad. The hidden cost is not just delay; it is the gradual erosion of a culture that equates “no news” with “all good”, which in turn encourages more silent gatekeepers to emerge.