Adding hierarchy to a supposedly flat organization creates a hidden “approval canyon” that saps velocity without anyone noticing. The new manager becomes the gatekeeper for every cross‑functional request, and the team learns to route problems through that gate rather than solving them directly. This shifts incentives: individuals protect their own bandwidth by offloading decisions upward, while the manager gains status by being the “only one who can say yes.”

The result is a network of informal dependencies that looks flat on paper but behaves like a multi‑layered bureaucracy. Google’s Project Aristotle (2015) revealed that teams with high psychological safety outperformed those with formal hierarchies, precisely because members could act without waiting for a sign‑off. In a product group of twelve engineers, a new API version that should have shipped in two weeks stalled for a month after the team began routing every change request to a newly hired “integration lead.”

The delay was not due to technical difficulty but to the extra approval loop that the lead introduced, turning a straightforward hand‑off into a bottleneck. When the lead left, the team reverted to direct collaboration and reclaimed the original cadence, proving that the hidden gate was the real culprit, not the work itself.