Org Chart

At ten people, who owns what lives in everyone's head. Look at the next desk and you know; if you don't, you ask. There's no reason to draw a diagram in that state.

At forty-five it stops working. Someone new finds a problem on the checkout screen, doesn't know where to send it, and posts in the all-company channel. Twenty people read it and nobody answers, because nobody can be certain it's theirs. Decisions run the same way: not knowing who decides, a person asks three people separately, and three different answers put them back at the start.

The cost of that state isn't time — it's that decisions stall. If finding somewhere to ask takes two days, nothing moves for two days, and the person who waited learns to stop asking. That last part is the expensive half, because it never shows up in any report.

An org chart is the document that puts what was in people's heads outside them. Drawn as boxes and lines, the answer can be found without asking anyone.

Boxes and lines. A box is a person or a position, a line is a reporting relationship. Four more things turn that into a document worth having.

1. What's in the box. A name alone doesn't say what the person does, so it takes a name, a job title, and a team together. What someone hunting for the checkout owner needs isn't the name; it's the title printed next to it.
2. What the line means. The reporting line — who reports to whom — is what these lines are. Leave that undefined and friendships and collaboration relationships get drawn in as lines too, and the diagram becomes a net. One line type carrying one meaning is what keeps it readable.
3. Team boundaries. Draw a border around groups of boxes. Whether this is a functional organization, grouped by discipline, or grouped by mission reads directly off those borders.
4. Open positions. Draw roles being hired for as dotted boxes. Leave them out and the fact that a team is running one person short disappears from the diagram entirely. That absence matters most to whoever is deciding where the next hire goes.
5. Second lines. In a matrix organization, where a discipline manager and a project manager both exist, a person carries two lines. Split them into solid and dotted to show which one owns evaluation and compensation. Without that distinction, there's no basis for resolving two managers assigning different work at once.
6. The date it was updated. This document goes stale quickly, and with no date on it someone reads a six-month-old diagram as the current state. A wrong chart routes questions to people who no longer own them.

One value gets read off the drawing without calculating anything: span of control, the number of people one manager holds. Twelve boxes hanging off a single box makes it visible that a weekly one-on-one with each of them is physically impossible.

The person who writes it is in HR or is the CEO. Whoever made the decision to change the structure has to draw it, because that's how the intent lands in the diagram. Decide at the top and draw at the bottom and the box arrangement drifts from the actual intent — and to everyone reading, that drift is the structure.

Four people read it.

The first is someone new. It's the document they open most in their first week, and what they get from it isn't a list of names but somewhere to direct a question. Names come later; routing is what a first week actually needs.

The second is anyone blocked and looking for an owner. Where to send an issue and who to get a decision from both come from here.

The third is whoever plans hiring and budget. This is where the open-position boxes earn their place; which team needs the next person shows up faster in a diagram than in a list.

The fourth is outside. It goes into investor material, and enterprise customers sometimes ask for it during pre-contract review, checking through the structure who can reach customer data. That request is what keeps many teams' charts current at all.

Since the readers split between inside and outside, keep two versions. The internal one carries open positions and dotted relationships; the external one drops personal details and any reorganization that hasn't been announced.

Staleness gets handled with process. Updating this document belongs inside the procedure that runs when someone joins, leaves, or changes teams. Fixing it once a quarter means spending the three months in between handing people a document that's wrong.

"The chart hasn't changed in six months and the teams have reorganized twice."

The document no longer points at the current state.

"This box has a name and nothing about what the person does."

Readers can't find the thing they came for.

"Twelve people under one person — is that sustainable?"

Span of control surfaced in the drawing and turned into a question about the structure.

At Pagedeck, Grace redrew the chart once headcount passed thirty. Up to that point asking was fine; what triggered it was the same question appearing in the all-company channel five times in one month. She drew it from the decisions she had actually made rather than from the seating plan, which moved two boxes.

Sofia built a separate version for enterprise pre-contract review. The internal one carried roles being hired and dotted reporting lines; the outgoing one dropped both and kept only teams and headcounts.

The most common mistake is treating the chart as the structure. You open the diagram to see the structure, so they feel like the same thing. But the diagram is a representation and the structure is how work and authority are actually divided. Miss the distinction and redrawing the diagram gets mistaken for changing the organization. Move the boxes, announce it, and if decision rights and who evaluates whom stayed put, two months later the work runs exactly as it did. The diagram changed and nothing that produces behavior did.

The second is expecting work to flow along the lines. Lines are drawn, so flow seems to follow them. But what this document draws is reporting and accountability, and work also runs along lines that aren't in it. A designer and an engineer trading messages twenty times a day appear as no line between any two boxes. Read the chart as a map of how work flows and you start trying to shut down the lines that aren't on it — which is the point where the diagram begins obstructing the collaboration it never described.