Your Org Chart Is a Confession

Most organizational reviews begin with interviews. Someone books three weeks of one-to-ones, asks forty executives what they do and what frustrates them, and produces a synthesis. It is a defensible method. It is also a slow one, and it has a flaw that nobody names: by the time you have interviewed forty people, you have absorbed forty explanations, and explanations are not the same thing as facts.

There is a faster diagnostic. Take the organization chart, or if there is not one, take the staff roster with titles and reporting lines. Read it as though it were written by someone who had no idea it would be read. Do not ask anyone what it means. Just look at what it says.

A structure is a record of decisions. Every box was created by someone, for a reason, at a moment. Read literally, the chart confesses what those reasons were.

What one chart admitted

I recently reviewed a group operating across four markets, built by a founder, tripling revenue over seven years. I was given a roster with names, titles and locations. Nothing else. Before a single conversation, four things were visible.

Two senior functions were being run by managers, with no executive above them. The seats existed on paper. They were empty. That is not an oversight; it is a statement that these functions were considered operationally necessary but not strategically owned.

Business development reported directly to the Group CEO, through three separate managers covering three geographies. There was no commercial leader anywhere in the structure. Marketing sat in one place and revenue generation sat in another, and the two never met below the CEO.

The CEO carried functions, operating entities and business development simultaneously. Not as a temporary arrangement during a transition. As the standing design.

And several reporting lines could not be confirmed from the roster at all, because different documents said different things.

None of this required an interview. It required reading.

The chart is a fossil record, not a blueprint

Here is what founders find uncomfortable when I show them this, and what I think is worth saying plainly.

Almost nobody designs an organization. What happens instead is that an organization accumulates. Someone excellent joins and a function is created around them. Someone leaves and their responsibilities are distributed to whoever was nearby. A market opens and a country manager is appointed with a reporting line to the founder because at that moment the founder was the only person who understood the market. A capable person is promoted and the title is stretched to justify the raise.

Each of these decisions was rational on the day it was made. Together they produce a structure nobody would have designed on purpose.

This is why the chart is diagnostic. It is a fossil record of past decisions, and past decisions were made under past conditions. The question is not whether the structure is logical. It is whether it is logical now, for the business as it currently is, rather than the business as it was when each box was drawn.

The psychology of the unexamined line

There is a more delicate layer underneath, and it is the reason structural conversations get emotional.

Reporting lines are not neutral. In a founder-led business they carry meaning that has nothing to do with organizational efficiency. A direct line to the founder is a signal of trust and access. It is understood that way by the person who holds it, by their peers, and usually by the founder too, even if none of them would say so.

Which means that when you propose moving a line, you are not proposing an administrative change. You are proposing a demotion in the only currency that matters in a founder-led company: proximity.

This is why so many structures have a wide, unmanageable span at the top. It is not that the CEO is unaware the span is too wide. It is that every attempt to narrow it has run into a conversation the CEO did not want to have with someone loyal. So the line stays. Another line is added. And the span widens again.

The founders I work with are not naive about this. They usually name it themselves once someone has given them permission to. What they need is not to be told the span is too wide. They need a design conversation that separates the question of trust from the question of reporting, so that they can move a line without anyone experiencing it as withdrawn confidence.

That is a structural problem with an emotional solution, and it is the part most restructuring exercises get wrong.

Four questions the chart cannot answer

Reading the chart tells you where to look. It does not tell you what you are looking at. A roster gives titles and locations, not mandates. So the literal read produces a set of questions, and these are the ones worth putting to the CEO and each function head before anything is redrawn.

Which of the CEO's lines are true management, and which are informal? Some people report to the founder because they are managed by the founder. Others report to the founder because they always have. The two require different fixes.

Is a direct line by design, or by legacy? If business development sits with the CEO because the CEO has decided that market entry is his personal mandate for the next three years, that is a strategy. If it sits there because it was there in year two, that is inertia wearing a strategy's clothes.

Where does authority actually sit, as distinct from where accountability sits? A country manager with full profit and loss accountability but no pricing authority is not running a business. They are running an operation and carrying someone else's number.

And who owns revenue end to end? If marketing, business development and sales sit in three different reporting lines that only converge at the chief executive, then the chief executive is the commercial function, whatever the titles say.

The point

The chart is the cheapest diagnostic you own and the least used. It costs an hour. It requires no access, no survey, no consultant.

Print your structure. Read it as a stranger would. Then ask yourself, honestly, how many of those lines you would draw again today if you were starting from a blank page.

The gap between the structure you have and the structure you would draw is the size of the design problem. Usually it is larger than the leadership team expects, and usually everyone in the room already knew.

People & Co works with founder-led businesses, family enterprises and scaling companies across MENA and the GCC on organizational design, decision rights and governance architecture.