The Org Chart Is Not the Organisation: Understanding How Work Actually Gets Done

Every organisation has two structures. The formal one is the org chart: the reported lines, the titles, the hierarchy that describes how authority is distributed on paper. The informal one is how work actually gets done: the relationships through which information actually travels, the people whose opinions actually shape decisions regardless of their position, the channels through which problems actually get resolved. These two structures are never identical, and the gap between them is where most organisational design fails.

Why the informal structure matters more than the formal one

The formal structure defines authority. The informal structure determines effectiveness. A decision made by the person who holds formal authority but is then executed by people who trust a different person's judgement will be executed according to that different person's interpretation. A communication sent through official channels but not discussed in the informal network that actually processes information will not be understood and acted upon in the way it was intended. Leaders who understand only the formal structure are operating with an incomplete map of the organisation they are trying to manage. They make changes that look sensible on paper — moving a reporting line, creating a new function, appointing a new head — without accounting for the informal dynamics that will determine whether the change produces what they intend. The result is a formal structure that has been adjusted and an informal structure that has adapted around it, much as it always has.

How to see the informal structure

The informal structure is not invisible, but it requires a different kind of attention than the org chart. The questions that reveal it are not who does this person report to but who do people actually go to when they have a difficult problem? Whose opinion matters in a decision even when that person is not in the room? Where do important conversations actually happen? Who are the informal connectors — the people through whom information flows between parts of the organisation that do not interact formally? Spending time observing rather than directing — in meetings, in the spaces where informal conversation happens, in the channels where work is actually coordinated — reveals these patterns reliably. So does asking people directly, in conversations designed to understand rather than to manage: who do you find most helpful when you are stuck? Where do you find out what is actually happening? These questions, asked of enough people, produce a map of the informal organisation that is more useful for design purposes than the formal chart.

Designing with both structures in mind

Effective organisation design works with both structures simultaneously. It uses the formal structure to create the clarity of authority and accountability that the informal structure cannot provide — explicit decision rights, clear role mandates, defined reporting lines. And it uses understanding of the informal structure to anticipate where formal changes will encounter friction and where they will flow easily. A formal change that works against the informal structure — that requires information to flow in ways that conflict with established trust relationships, or that places authority in someone the informal network does not respect — will be undermined by the informal structure without anyone intending to undermine it. This is not sabotage. It is how organisations function. Designing around it is not capitulating to informal dynamics — it is incorporating realistic understanding of how organisations work into the design.

What this means for AI and technology implementation

The formal-informal gap is particularly relevant for technology and AI implementation. A system that is designed to route information through formal channels will be adopted if those channels match how information actually flows, and resisted if they do not. Implementation that does not account for informal dynamics — for who the trusted voices are, where the real concerns are likely to come from, which teams are early adopters and which will need more support — will encounter adoption friction that looks like resistance to the tool but is actually resistance to a change that does not fit the way the organisation actually works. Understanding the informal organisation before deploying something new into it is not a soft consideration — it is a practical precondition for adoption. The organisations that implement AI successfully are consistently ones where the implementation team understood how the organisation actually worked, not just how it was supposed to work. That understanding is available to anyone willing to look past the org chart.