Your Org Chart Is Not a Map of How Work Happens

An org chart shows who reports to whom. A process map shows how work actually moves through a business, step by step, person by person, and the two almost never match.

That mismatch is not a sign of a badly run company. It is normal. Every business of any size develops routes that the boxes and lines were never drawn to describe: the finance person who quietly checks every contract before it goes out, the engineer everyone messages directly instead of raising a ticket, the founder who still approves refunds over a certain amount. None of that appears on the chart. All of it appears in the work.

The trouble starts when you make decisions using the chart.

Org chart vs process map: what each one is actually for

An org chart answers a question about authority. Who is accountable, who sits in which function, who a new starter escalates to. It is a governance document. It is genuinely useful for that, and if you have more than about eight people and no org chart, draw one.

A process map answers a different question entirely. It answers: what happens, in what order, and who touches it. A single order coming through your website might cross four people and six tools before the customer gets anything. On the org chart those four people may sit in three different functions with no line between them. The chart says they are unrelated. The work says they are a chain.

Both documents are true. They are just true about different things, and only one of them tells you where your business is slow.

The gap is where the problems live

Hiring is the clearest example. A team feels stretched, so the chart gets consulted, and the box with the most people underneath it looks like the one carrying the load. So that is where the hire goes. Six weeks later nothing feels faster, because the actual bottleneck was a single approval step sitting with somebody in a different function who was never part of the conversation.

Handovers are the other one. Work rarely goes wrong in the middle of a task. It goes wrong in the space between two tasks, when one person has finished and the next has not started because nobody told them. Those gaps are invisible on an org chart by definition, because the chart draws vertical lines and handovers are horizontal.

Then there is the person everybody routes around. In most small companies there is at least one individual who has quietly become load-bearing: they know the pricing exceptions, they have the login, they remember why the process is odd. On the chart they might sit three levels down with nobody reporting to them. On a process map they appear in nine places out of thirty. That is not a personnel observation, it is a risk assessment, and you cannot make it from the chart.

What a process map shows that a chart cannot

Order. The chart has no concept of sequence, so it cannot show you that a step happens twice, or that approval comes before the information needed to approve it.

Tools. Reporting lines say nothing about software. Map the process instead and you find out that sales, delivery and support are each keeping their own version of the customer record in three separate systems, and that somebody is retyping between them every week.

Time. Not effort, elapsed time. A step can take four minutes of work and sit in a queue for two days. The chart is silent on this. The map makes the waiting visible, and the waiting is usually where the customer experience actually degrades.

Exceptions. Every process has a documented path and a real path, and the difference between them is the workarounds people invented because the documented path did not fit. Those are worth knowing, because they are your team telling you where the design is wrong.

This is the reason we built abi. Clone as a free way to map how your business really runs, rather than another tool for drawing boxes and reporting lines. It takes about ten minutes to build the first version by hand. There is no card, and no requirement to map the whole company before you get anything useful out of it.

Where the org chart wins

It is worth being clear about this, because process mapping gets oversold and it deserves a limit.

If your problem is that nobody knows who decides, a process map will not fix it. Ambiguous authority is an org chart problem, and mapping the workflow in more detail just documents the confusion in higher resolution. Same for accountability after something goes wrong, career progression, compensation banding, and telling a new hire who to ask for a day off. The chart is the right instrument for all of those, and a map is a poor substitute.

There is also a real cost to mapping. It takes attention, it needs to be kept current, and a map that describes how the business ran eight months ago is worse than no map, because people will trust it. If you are a team of three who all sit in one room and can see each other work, you probably do not need one yet. You are the map.

The point at which it starts to pay is roughly when the business stops fitting in one head. Usually that is a first significant hire, a second location, a founder trying to stop being in every decision, or the moment somebody asks a question about how the business works and three people give three different answers.

Start with one process, not the company

The mistake is scope. Somebody decides to map the business, opens a blank canvas, and stops three days later having documented nothing anyone needed.

Pick a single process instead, and pick the one that annoys you most. Quote to cash is a good candidate for most businesses, because it touches sales, delivery and finance, and because it is where money gets delayed. Onboarding a new customer is another. So is anything a customer complains about.

Then write down what actually happens, not what should. Every step. Who does it, what they do it in, what triggers it, what they hand to the next person. Do not clean it up as you go. The odd steps are the interesting ones.

You will find things. A duplicate approval nobody remembers introducing. Two people doing the same check. A form filled in by hand from a system that already holds the data. A step that exists because a customer complained in 2023 and never got removed. Those are the return on the exercise, and they show up in the first hour.

Compare that map to your org chart afterwards. The differences are not errors in either document. They are the list of things your business does that nobody has decided to do.