The Shadow Org Chart Running Your Company
Ask a room full of executives who has the authority to make an operational call, and you’ll usually get a similar answer every time: COO, VP of Operations, or maybe even a regional director. There's a box with a name in it, and that name has the authority to decide. It’s clean, logical, and matches the slide that gets projected at every all-hands meeting.
Watch what actually happens the next time a decision needs to be made. The person who signs off quietly checks first with an analyst so they can catch if the numbers are wrong. A "quick sync" gets scheduled with someone whose title suggests they should have nothing to do with any of this, and everyone agrees it's necessary without quite saying why. A director loops in a peer from another department entirely, not because policy requires it, but because that peer is the only one left who remembers why the last version of this broke. None of it shows up on the org chart, and nobody involved thinks of it as going around the system. The workaround got worn into a path so long ago that it stopped feeling like one.
The Chart Shows Authority. The Work Shows Influence.
An org chart is a map of who reports to whom and a decent record of formal authority. What it almost never captures is how the actual work flows, and those two things drift apart over time.
Natural authority collects around whoever is reliable, whoever has context, whoever answers quickly. Decisions route through them out of habit whether they have actual authority over the decision. Risks and roadblocks start to arise when these team members take two weeks off or move to a new role, and nobody can quite explain why - because on paper, they're just a coordinator in one corner of one department.
The formal structure tells you who is accountable, but it doesn’t tell you what the company depends on to function day to day. Leadership tends to plan around the first and get blindsided by the second.
Why the Gap Is Expensive
This is where a lot of organizational redesign goes wrong before it starts. A team pulls the official chart, spots the redundant layers, and redraws reporting lines to clean it up. It looks great on paper, but the trouble is they've just reorganized a structure that was never carrying the real weight to begin with.
The informal network, the one with the analyst everyone checks with, and the coordinator who holds three teams together, keeps running underneath whatever gets redrawn. And because nobody asked why influence had pooled where it did, the same dependencies quietly reassemble inside the new boxes. You've renamed the departments and moved a few reporting lines, and the same person is still the reason everything works, now with a slightly different title and the same invisible workload.
That dependency didn't appear by accident. Somebody became the go-to because the formal owner of that decision was too slow, too removed, or missing context the work actually required. Redesign without ever asking why, and you haven't fixed anything, you've just given people a new diagram to route around.
Go Find Who Gets Pinged
Fixing this has less to do with drawing a better chart and more to do with paying honest attention. Stop asking "who owns this," which just returns the org chart. Ask people to walk you through the last real decision they were part of and pay attention to every name they mention that isn't in their reporting line. Ask who they check with before they commit to something. Ask whose absence would quietly stall their week.
Do that across a dozen people and a second structure comes into focus, the one where the work lives. It rarely matches the official chart, and the mismatches are the interesting part. A node with heavy informal load and no formal authority is a single point of failure and a promotion waiting to happen. A formal owner nobody routes through is a signal that authority and capability have come apart.
This takes longer than opening the HR system and looking at the boxes. It's also the only way to see the structure that's running the place.
Restructuring Around the Wrong Diagram
The instinct in organizational design is to treat the informal network as messiness to be cleaned up, so that authority and work finally line up with the chart. Those informal paths are the clearest diagnostic you have and point straight to where formal structure fails to match how the work moves.
Redesign around the official chart and you're solving a problem the organization doesn't have. Redesign around where influence and dependency have collected, and you're solving the one it does. Good organizational design rarely starts with a cleaner box diagram. It starts with an honest look at who the company already runs on and whether the chart says so or not.