Hierarchies, maps and symbol libraries
Organization chart
Reporting lines as a tree: units and roles, top down, with names and titles in the boxes.
org.tree@1New DDN source
Why use it?
Escalation paths and span-of-control questions are answered by the shape before anyone reads a name.
When it helps
Onboarding docs, reorg proposals, RACI context (who the letters are).
How to read it
- Each box is a role or unit; the line above is its manager.
- Wide layers are wide spans; deep chains are slow escalations.
What you need
- The roles
- The reporting lines
Things to check
- Do not draw dotted-line influence as a reporting line — mark it differently or omit it.
- A box with two managers is a matrix claim; draw it deliberately.
Scope of this diagram
Declared hierarchy; HR-system accuracy is documented, not synchronised.
Work with the converted example
- Open the viewer and select
org. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.