A single page that neatly lists every role sounds like clarity, but it silently forces every manager to become a gatekeeper of information. When a leader can point to a static diagram and claim “that’s who does what,” they also create a hidden expectation that all cross‑functional requests must travel through the person who owns the box on the chart. The result is a cascade of “who should I ask?” emails that never reach the right specialist until the request is rerouted, duplicated, or dropped.

Netflix discovered this when its original recommendation squad, a tight‑knit group of engineers, data scientists, and product partners, tried to scale the algorithm for a new market. The team’s leader posted a one‑page map that showed “product” as a single node, even though dozens of product owners now existed. New hires, unaware of the informal sub‑teams, began routing feature requests to the original product lead, who became a bottleneck. The delay pushed the rollout timeline back by weeks and sparked frustration across the data and engineering groups.

The deeper problem is that a static chart freezes the perception of who holds authority, while the real authority landscape is fluid, shifting with project phases and expertise. As a consequence, people default to the most visible name rather than the person whose current workload matches the request, inflating coordination tax and eroding trust. The only way to break the cycle is to make the map itself a living, queryable surface that shows not just titles but real‑time capacity and ownership signals.