Newsletter
By Aster Angagaw
June 25, 2026
The Org Chart Lies: Where Real Decision Rights Actually Live
Every organization has an org chart. It is neatly formatted, carefully maintained, and often presented as if it explains how the company actually operates.
It doesn’t.
The org chart is the formal architecture: who reports to whom, who holds the budget, and who signs off. It is real, and it matters. But it is only half the system. Running underneath it, in every organization I have ever been part of, is a second structure that never appears on any chart: the social architecture. Who people actually defer to. Whose quiet objection can stall a decision that has every formal approval it needs. Whose support has to be earned before a rollout, not assumed because of a title.
Formal architecture tells you who is allowed to decide. Social architecture tells you whether that decision will survive contact with the organization. Most execution failures get diagnosed as a strategy problem or a talent problem, when they are actually a mismatch between these two architectures: a decision that was fully authorized and entirely unsupported.
I have watched this gap play out at close range, more times than I can count, and it never announces itself the way you’d expect.
I have seen this exact pattern play out again and again. A leadership team makes the case to centralize customer service across business units. The analysis is sound. Costs fall, service levels improve, and customers get a more consistent experience. Weeks of debate produce a decision, and around the table, nobody objects. The leader leaves that meeting believing alignment has been achieved.
The real conversation starts the following week, in rooms they weren’t in. A few leaders tell their teams, quietly, that they’re worried about losing control. Others question whether the savings are realistic. No one challenges the decision directly. Everyone hedges it behind closed doors. Within a month, managers are escalating concerns that were already answered. Implementation slows. New requests for “additional analysis” appear from nowhere. Three months later, the team is debating the same decision again, as if it had never been made.
The problem is never authority. The leader had it and used it. The problem is mistaking agreement in the room for commitment outside it. The org chart says who owns the decision. It never shows you the half-dozen people whose quiet skepticism will determine whether it survives contact with the organization.
I have watched this fail at a larger scale too, the same way, more than once. A board approves a major transformation. The CEO champions it publicly. Resources move. And underneath the public commitment, a handful of senior leaders never actually buy in. Not loudly. No open dissent, no resignation in protest. Just a steady drip of hallway commentary: we’ve tried this before, leadership doesn’t understand the disruption this creates. Employees hear it and do what employees do when they sense leadership isn’t unified: they hedge. They keep the old systems running in parallel. They wait to see who turns out to be right.
Eighteen months in, the results are exactly as disappointing as the skeptics predicted, which they then point to as proof they were right all along. The organization drifts back to its old operating model within two years. The strategy didn’t fail. The org chart said the CEO owned the transformation. In practice, its survival depended on a handful of people whose informal influence outweighed their formal authority, and nobody had mapped that before launch.
This is social architecture, in its plainest form: every enterprise has an invisible network running underneath the formal one. The operator everyone consults before acting. The long-tenured leader who remembers why the last three attempts at this failed. The risk function that controls approval in practice, regardless of what the policy says. None of them show up as decision owners on the formal chart. All of them are load-bearing in the social one, and all of them can stop a decision cold.
This is also why decision rights drift rather than move, after watching this happen repeatedly. Nobody decides to centralize authority upward. Organizations accumulate exceptions, workarounds, and review layers, one reasonable request at a time, and each one makes sense in isolation.
The cumulative effect is that the formal architecture becomes more complicated while the social architecture becomes more decisive, until nobody is quite sure who can decide what, and decisions migrate up to whoever still has clear authority, which is usually the CEO, regardless of how good the org design looked on paper. You end up with more leaders and fewer actual decision-makers, which is the opposite of what the formal chart promised.
When execution stalls, the instinct is to assume a talent problem. Usually, it’s an architecture mismatch instead: a decision that the formal structure approved and the social structure never ratified. The symptoms are familiar: meetings built to secure alignment rather than make calls, multiple approvals for routine actions, escalation as the default mechanism rather than the exception.
The cost isn’t abstract. Opportunities sit too long. Customers wait. Competitors whose social and formal architectures are actually aligned move faster, every time, on the things that compound.
What I’ve learned to do differently, after watching this happen repeatedly, is to treat the informal network as something to map deliberately before a major decision launches, not something to discover after it stalls. Who can stop this, even though they don’t own it on paper? Whose private skepticism will outweigh their public agreement once the room empties? Those are answerable questions if you ask them early. They are very expensive questions if you only ask them in the post-mortem.
High-performing organizations understand a simple truth: disagreement before a decision is healthy. Disagreement after a decision is expensive. The first sharpens a decision while the formal and social architectures are still being reconciled. The second means they were never reconciled at all. It just took three months for that to become visible.
This is why mapping the social architecture has to happen before a decision launches, not after it stalls. In practice, that means treating it with the same discipline most organizations reserve for the formal one. Before a major decision goes out the door, it is worth asking, deliberately and in writing: Who can stop this, even though they don’t own it on the formal chart? Whose private skepticism is likely to outweigh their public agreement once the room empties? Whose support is necessary but not sufficient, because three other people will look to them before they move?
Naming the five or six people who function as the organization’s actual gatekeepers, and what each of them needs to hear before they’ll stop hedging, is a different exercise than building consensus in a steering committee meeting. It surfaces the objections that would otherwise show up three months later as a stalled rollout.
The second discipline is making space for real dissent before the decision is made, and refusing to tolerate it after. One organization I was part of institutionalized this through a principle it called “Disagree and Commit.” Not because it expected uniform agreement, but because it understood execution becomes impossible when every decision is reopened after the meeting ends. The standard was not that everyone had to agree. The standard was that once a decision was made, the organization moved as if everyone did, and anyone who was still unconvinced said so in the room, not in the hallway three weeks later. That single discipline would have changed the outcome in both of the examples above. The dissent wasn’t the problem. The timing and the venue were.
None of this replaces good strategy or sound analysis. It replaces the assumption that a decision is real the moment the formal architecture approves it. A decision becomes real when the social architecture has ratified it too: when the people who can quietly stop it have said so out loud, before it ships, and have nowhere left to hide their disagreement but in the room where it can still be addressed.
Boards spend real time on strategy, risk, and succession. The question I’d put in front of more boards is simpler and gets asked far less often: how does this organization actually make decisions, not how the formal architecture says it does, but how it really happens when something contested is on the table? A board that understands where its social architecture sits, and whether dissent is being surfaced before launch or absorbed as cost after, is asking the right question about an organization’s actual operating system, not its org chart.
The org chart tells you how the company is organized. Decision rights tell you how it actually operates. The distance between the formal architecture and the social one is usually where performance is won or lost. In my experience, it’s almost never visible until you’ve already paid for it once.