Match the diagram to the grammar of the message, not to what looks impressive. If the message is "X depends on Y and Z," use a matrix. If it's "X leads to Y leads to Z," use a process flow. If it's "X contains Y contains Z," use a pyramid or hierarchy. If it's "X repeats," use a cycle. State the slide's or exhibit's message as one sentence before opening a deck or document tool, then use the decision table below to pick the container. Diagram type is not decoration. The wrong family for the message misleads a reader as reliably as a wrong number would.
A client deliverable goes wrong in the same handful of ways every time, and the diagram choice is usually one of them. An analyst has a real finding, three ranked remediation options with a clear favorite, and reaches for a 2x2 matrix because that shape reads as strategic. A matrix implies two independent variables and genuine trade-offs across four quadrants. Three ranked options with a favorite is a different message, and it belongs in a different container. The reader spends thirty seconds hunting for the second axis before giving up, and the finding lands softer than it should have.
This happens constantly in compliance-consulting work specifically: assessment reports, audit-findings decks, gap-analysis summaries, board packs. The analysis underneath is usually sound. The container the analysis gets forced into is not. This is a reference page, not a narrative one: eleven diagram families, the kind of message each one is built to carry, and the anti-pattern that shows up when the wrong family gets used anyway.
State the message before you pick the container
Every diagram family below answers a different sentence shape. Before opening a slide or a document tool, write the exhibit's message as one sentence, then check which shape it matches.
- "X depends on Y and Z" is a matrix.
- "X leads to Y leads to Z" is a process flow.
- "X contains Y contains Z" is a pyramid or hierarchy.
- "X repeats" is a cycle.
If the message doesn't fit one of those four shapes, it usually isn't a message yet. It's a topic label, and no diagram fixes that. This is a per-slide rule for picking a container, not the deck-level discipline for ordering the whole argument. How the individual slides add up into one argument is a separate skill, covered in the Pyramid Principle for consulting communication. The FAQ below covers how that pyramid differs from the diagram called a pyramid, row four of the table.
The message-to-diagram decision table
| The message you're making | Diagram family | Anti-pattern to avoid |
|---|---|---|
| "These two things trade off against each other; here's where options land" | Matrix (2x2 or N×N grid) | Using a matrix when there's no real second axis. A matrix with one filled quadrant is a bar chart wearing a costume. |
| "This is a repeating process with no fixed end" | Cycle | Drawing a cycle for a process that actually terminates. A cycle claims "this repeats forever," which is a statement, not decoration. |
| "This happens in sequence, step 1 through N, with direction" | Process flow / arrows | Including every step the team actually took instead of every step the reader needs to act on. |
| "This is a hierarchy, a maturity ladder, or an escalation path" | Pyramid / staircase / tiered levels | Using a pyramid to rank options rather than show real structure. Ranked options belong in a list or bar chart. |
| "Compare several discrete items on the same criteria" | Column / comparison grid | Past five or six columns the grid stops being scannable. Split into two exhibits before shrinking the font. |
| "This is a specific, named business or strategy framework" | Framework-specific canonical shape (SWOT's four-box, Porter's five-force ring, the Ansoff growth grid) | Inventing a new diagram for a framework that already has a recognized shape. Readers pattern-match on the shape faster than the label. |
| "Here's the underlying data" | Chart (bar, line, pie, waterfall, scatter) | Treating "chart" as the whole decision. Which mark, axis, and color scale to use is a separate step once a chart is the right container. |
| "Show relative timing or resourcing across workstreams" | Gantt / timeline | A Gantt with no dependency marking is a decorative calendar, not a plan. |
| "Show where two or three groups overlap" | Venn diagram | Past three circles a Venn stops being readable. Use an overlap table instead. |
| "3D block, tower, or cube visual comparison" | 3D metaphor shapes | Use sparingly. The lowest information-density family here; if a 2D matrix carries the same message, use the 2D matrix. |
| Not a message at all; it's deck plumbing | Tables, legends, disclaimers, org charts, exhibit titles | Treating deck furniture as a per-slide decision. Pick one format for the whole deliverable and leave it alone. |
The highest-value habit in this table is the anti-pattern column. Most deliverables don't fail because someone picked an ugly diagram. They fail because someone picked a defensible-looking diagram for the wrong message, and the misdirection stays invisible until a reader tries to actually use the slide.
Five families worth a second look
The matrix: where trade-offs actually live
A matrix earns its place only when there are two genuinely independent variables, and the finding is where multiple items sit relative to both. Risk likelihood against risk impact is a real matrix. Cost against implementation difficulty for a set of remediation options is a real matrix. What isn't a matrix: a single ranked list of options with one clear leader, a scored checklist with only one dimension, or an ordinal risk rating (low, moderate, high) dressed up as a quadrant so it looks more analytical than a scale. If more than three quadrants sit empty, the matrix is decoration, not analysis.
Process flow: the family that gets overloaded most
The most common defect in this family is including every step the team actually performed instead of every step the reader needs to act on. A five-phase engagement runs through dozens of real tasks; the flow diagram that represents it to a client should carry the phases the client needs to track, not the internal task list. See the five phases of a consulting engagement for the canonical shape a lifecycle process flow should take.
Pyramid and hierarchy: not the Pyramid Principle
This is the row that causes the most confusion, because "pyramid" names two unrelated things in consulting work. The diagram family in row four of the table above is a structural shape: a maturity ladder, an escalation path, a level of assurance, something with a genuine top-to-bottom containment relationship. The Pyramid Principle is a different thing entirely, an argument-ordering rule that puts the conclusion first, then the supporting structure, then the evidence, with nothing to do with drawing a triangle on a slide. A deliverable can use the Pyramid Principle from end to end and never draw a single pyramid diagram, or draw a pyramid diagram on one slide while the deliverable's actual argument runs in a different order. Keep the two separate. The Pyramid Principle for consulting communication covers the argument-ordering discipline; this page covers the shape.
The comparison grid: the five-or-six-column ceiling
A column comparison works when you're weighing a fixed, small set of options against the same criteria: vendor shortlists, control-framework alternatives, remediation-approach options. Past five or six columns, the grid stops being something a reader can actually scan in a live meeting, no matter how small the font gets. Split into two exhibits along a logical seam, cost criteria on one and coverage criteria on the other, rather than compress a seven-column table until it's unreadable on a shared screen.
Chart: a different decision, once you're here
Choosing "chart" answers whether the message is a number or a trend rather than a structural relationship. It doesn't answer which chart. Bar, line, waterfall, and scatter each carry their own encoding decision, their own color logic, and their own axis choice. That work is downstream once the family is settled, and it's a distinct discipline from diagram selection. Get the family right first, then decide the mark.
The family to use sparingly: 3D metaphor shapes
Cubes, towers, spirals, and other 3D visual metaphors are the lowest information-density family in this list. They read as visually striking and are rarely the right container for an analytical point, because the third dimension almost never carries real data. It's decoration wrapped around a message a flat matrix or bar chart would communicate faster. If a 2D shape would carry the same message as a 3D one, use the 2D shape. The rare legitimate exception is a genuinely three-dimensional relationship, such as a true capability-maturity-over-time cube, where all three axes carry independent information a 2D diagram can't hold at once.
Where this goes wrong in a compliance-consulting deliverable
- An ordinal risk rating forced into a 2x2 matrix so it looks more analytical than a simple scale. If there's really one axis, use a scale or a color-coded list, not a quadrant.
- A remediation timeline built as a bulleted list with dates attached, presented as if it were a Gantt. A true Gantt shows dependencies, what can't start until something else finishes. A list with dates is not that.
- A root-cause analysis presented as a fishbone diagram when the underlying work was actually a hierarchy of causes with genuine structure. The two look similar and answer different questions. See 8D vs. 5 Whys vs. fishbone for the distinction between the technique and the diagram that represents it.
- A gap-to-remediation sequence forced into a cycle because the template only has a cycle shape available. Most gap-analysis work terminates; it doesn't repeat. See AML program gap analysis for the underlying method a gap-analysis exhibit should represent.
- A corrective action plan rendered as a flowchart with no owner or date on any step. The diagram family was right; the content that belongs in it was missing. See how to write a corrective action plan for the fields a CAPA exhibit actually needs.
- One diagram trying to carry independence clearance, scoping, and staffing because "it's all planning." Different messages, even inside one phase, still need different containers. See how to plan a compliance audit engagement for how those stages actually separate.
A worked example: assigning families to an audit-findings deck
Five slides, five different messages, five different containers. Naming the message first is what keeps the deck from defaulting to whatever shape the template happens to open with.
| Slide's message | Diagram family | Why |
|---|---|---|
| Findings cluster into three severities, and each severity maps to a different remediation timeline | Matrix | Two independent variables, severity and timeline, with a real trade-off across the grid. |
| Remediation runs in four phases, each gated on the prior phase closing | Process flow | Sequential, with a direction the reader has to follow. |
| The control-maturity model runs from ad hoc to optimized, and this program sits at level 2 of 5 | Pyramid / staircase | A genuine structural hierarchy, not a ranked list of options. |
| Three vendors' proposed remediation approaches, compared on cost, timeline, and coverage | Comparison grid | A small, fixed set of discrete items on the same criteria. |
| Finding volume by category across the last three exam cycles | Chart (bar) | The point is a trend over time, not a structural relationship. |
Primary sources
- Gene Zelazny, Say It With Charts: The Executive's Guide to Visual Communication, 4th ed. (McGraw-Hill, 2001): the standard reference for matching a chart type to the message it needs to carry.
- Edward R. Tufte, The Visual Display of Quantitative Information, 2nd ed. (Graphics Press, 2001): the canonical source on information density and the misleading use of decorative dimensions in a chart.
- Barbara Minto, The Pyramid Principle: Logic in Writing, Thinking, and Problem Solving (Minto International, 1996): the origin of the argument-ordering rule that gives the pyramid diagram its name, and the source for distinguishing the two.
- International Organization for Standardization, ISO 5807:1985, Information processing — Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts: the standards body reference for process-flow symbology.
- Cole Nussbaumer Knaflic, Storytelling with Data: A Data Visualization Guide for Business Professionals (Wiley, 2015): a modern practitioner treatment of chart selection and the failure modes covered in the Chart row above.