visual-communicationlisted

# Visual Communication A diagram is not decoration — it is compression. If three paragraphs describe the same flow a diagram shows in 20 seconds, the diagram wins. If a diagram takes ten minutes to read, the paragraphs won. ## When a diagram beats prose | Signal | Diagram | |---|---| | The reader needs to understand a process with branches | Flowchart | | The reader needs to see *who talks to whom and when* | Sequence diagram | | The reader needs to understand state transitions | State diagram | | The reader needs to see *what depends on what* | Component / dependency diagram | | The reader needs the data model | ER diagram | | The reader needs the big picture of a system | C4 diagram | | The reader needs a 2×2 trade-off / matrix | Quadrant / matrix | When a diagram does NOT beat prose: - Simple linear sequences (1 → 2 → 3) — a list is clearer. - Content-heavy ideas — diagrams force compression that loses nuance. - When the diagram would have 30+ nodes — split or describe. - When the reader needs exact values — a table beats a chart. ## Picking the right diagram ``` Flow-oriented (what happens in what order)? ├── With branches/decisions → flowchart ├── Between actors/components over time → sequence diagram └── With explicit states → state diagram Structure-oriented (how is it organized)? ├── Data → ER diagram ├── Code → class diagram ├── System at high level → C4 diagram └── Components + dependencies → dependency graph Comparison-oriented? ├── 2 dimensions, 4 quadran