Case in point: When Netflix reorganized around streaming in 2011, the formal structure moved executives into new reporting lines within weeks. But the actual work — content licensing, encoding, CDN delivery, recommendation algorithms, consumer product — kept flowing through the same informal paths built over years of DVD operations. The org chart changed. The operating model did not. Reed Hastings wrote about this explicitly in his 2011 culture memo: the structure had changed, but the habits, relationships, and decision patterns had not. It took two more years of deliberate redesign before the informal map began to match the formal one.
Every new hire gets shown the org chart. It's presented as the map of the organization — who reports to whom, where the boundaries are, who has authority over what. Then the new hire goes to work and discovers that the work moves through a different map entirely.
The org chart shows formal authority. It does not show decision latency, overloaded approval points, handoff risk, information gaps, or the teams that quietly carry work across the seams. It is useful, but only as a starting sketch.
Leaders who rely on the org chart are diagnosing from anatomy while the patient is moving. Leaders who map the work can see where execution actually breaks.
What to Read Instead
Build a diagnostic map of work. Four layers matter most:
The decision map. Which decisions were actually made, by whom, with whose input, and after how much delay? Trace real decisions backward. You'll find the actual authority and the approval depth.
The information map. Where does customer, operational, financial, and risk information travel? Who sees it early? Who sees it too late? Who never sees it but is expected to decide anyway?
The handoff map. Where does work move from one team to another? Count the handoffs. Look for lost context, duplicated work, and unclear ownership of the seam. Handoff count is one of the cleanest measures of structural drag.
The queue map. Where does work wait? Not where people are busy — where work is idle because a decision, approval, dependency, or specialist is unavailable. Queues reveal bottlenecks better than status reports do.
Leave the deeper politics of informal power for a separate map. At this stage, the goal is simpler: understand how work moves before you try to redesign the organization around it.
How to Build the Map
Start with three or four significant initiatives that recently moved through the organization: a product launch, enterprise deal, incident response, budget approval, or churn escalation.
For each one, trace backward from the outcome:
- Who initiated the work?
- Who did the work?
- Who gave input?
- Who approved?
- Where did it wait?
- Where was work redone?
- Who escalated, and to whom?
Then measure the basics: decision latency, handoff count, escalation frequency, approval depth, meeting load, and rework rate. You do not need a perfect dashboard. A rough map built from real work is better than a polished org chart built from intention.
The gaps are diagnostic. If authority lives lower than the chart implies, you may have a leadership bandwidth problem. If authority lives higher, you have a bottleneck. If work crosses too many seams, you have a topology problem. If no one can name the owner, you have a decision-rights problem.
