Org chart encodes values as parent-child placement of nodes in a tree. Daniel McCallum’s 1854 New York & Erie railroad diagram.
In reports, ads and assignments it fits reporting lines, committee structure, project roles. Skip it when work actually flows sideways across a matrix.
Parts
- Mark — The core mark of Org chart is parent-child placement of nodes in a tree.
- Scale — The scale must show zero (or a declared break) and units.
- Axis — Axis titles name the variable, not a mood.
- Legend — A legend is weaker than a direct label. Write beside the mark when you can.
- Label — Numbers are optional. If comparison is the job, label the ends only.
- Grid — Keep the grid faint. Data should own the ink.
- Annotation — One annotation sentence. Date the source.
- Frame — A thin frame. Never a 3-D box.
Variants
- Organigram — Variant 1 of Org chart. Same encoding, different layout.
- Reporting tree — Variant 2 of Org chart. Same encoding, different layout.
- Hierarchy map — Variant 3 of Org chart. Same encoding, different layout.
- Org chart 4 — Variant 4 of Org chart. Same encoding, different layout.
Labels
- Axis — On Org chart, make Mark readable.
- Legend — On Org chart, make Scale readable.
- Label — On Org chart, make Axis readable.
- Grid — On Org chart, make Legend readable.
- Annotation — On Org chart, make Label readable.
Org chart: honour parent-child placement of nodes in a tree, and switch when work actually flows sideways across a matrix.