An org chart is a picture of decision rights. Drawn well, it tells a new hire who to ask, tells finance where headcount actually sits, and tells you, the person drawing it, where the structure is cracking. Here's how to make one that says something true.
| Structure | Organized by | Appears at | Classic failure |
|---|---|---|---|
| Functional | Discipline | 1–200 people | Silos between teams |
| Divisional | Product / region | 200+ | Five marketing teams doing similar work |
| Matrix | Function + project | Agencies, large tech | Two bosses, unclear priority |
| Flat | Nothing much | Under ~30 | Founder as bottleneck |
Most companies overgrow flat into functional, then functional into divisional or matrix as products and locations multiply. The chart should reflect how decisions actually flow, not how you wish they did; if every "cross-functional" decision secretly waits on one VP, draw the line where it truly runs.
The two numbers that make or break a structure:
Too narrow (lots of managers of two) and you've built layers that slow every decision. Too wide (a leader with 18 heterogeneous reports) and coaching quietly stops. When you spot a span outside the range, the chart has done its job: either the span needs help, or the role isn't really management.
Work top-down: leader first, direct reports one level below, their reports below that. One box per person, name plus title, no clip art. If a department runs deep, split it into its own page rather than shrinking the whole chart to fit. Mark open roles as "Open — Role" so the chart doubles as a hiring plan; that's usually the moment leadership starts actually using it.
Type your team as an indented list, get a clean chart you can download.
Open the Org Chart Maker →Real organizations have wrinkles the chart can't hold: dotted-line mentors, project squads, contractors. Don't force them into solid lines. Note the exception in the title if it matters ("Platform team — embedded in squads"), and keep a separate working-relationships map if collaboration is the story. Update the chart the week reporting lines change; a chart that's three reorgs behind is worse than none, because people make decisions with it.
Pair the structure view with a schedule view, a Gantt chart for the quarter's workstreams, and process views like a flowchart for how work moves through the org. Three simple diagrams cover most of what slide decks try to say.
Functional, almost always: one leadership team and discipline-based teams below it. It duplicates nothing, concentrates expertise, and everyone knows where they stand. Divisional structures make sense when products or regions genuinely need their own P&L, which usually starts past a few hundred people.
Shallow enough that any employee is within three or four steps of the top. Each layer adds translation loss between decisions and reality, so depth has a real coordination cost. If your chart has six layers under the CEO and fewer than 200 people, layers are being handed out as titles rather than grouped by real management work.
Whenever reporting lines change, and reviewed quarterly either way. The chart is infrastructure for onboarding, approvals, and planning; a stale chart quietly misroutes both questions and blame. Charts you can regenerate in a minute from a text list stay accurate, which is exactly why we built ours that way.
An org chart shows reporting lines, who answers to whom for performance and career. A team map shows working relationships, who actually collaborates on what, and looks completely different at most companies. You need both; confusing them is how you end up reorganizing reporting lines to fix a collaboration problem.