Use before every customer-facing presentation. A diagram that kills a deal does so quietly: it overwhelms the non-technical audience, causes the technical audience to debate implementation details instead of strategic decisions, and signals that the architect doesn't know who is in the room.
Gate 1: Executive Readiness (required for any C-suite or VP audience)
- Title states the business outcome, not the technical component (e.g., "Customer Data Platform" not "Azure Synapse Analytics + Purview")
- Fewer than 8 distinct visual elements visible without zooming
- Zero unexplained acronyms in the executive-facing version
- Business outcome is visually prominent (size, position, or color)
- "Before" state is represented to contextualize why this architecture exists
- The diagram can be used by the sponsor to explain the project to their board without additional explanation
Gate 1 result: _____ of 6 checked. Minimum 5 of 6 required for executive presentation. Pass / Revise
Gate 2: Cognitive Load Control
- Total element count is appropriate for the audience (≤8 executive, ≤15 director, ≤25 technical)
- Color is used meaningfully: each color represents a distinct semantic layer (environment, service category, data flow direction)
- No more than 3 typefaces or font sizes used in the diagram
- Lines / arrows are labeled with what flows across them (data, API calls, events)
- No orphaned elements: every component connects to at least one other
- Swimlanes or boundaries have clear ownership labels (Security boundary, Customer network, Microsoft-managed)
- Legend exists if non-standard icons are used
Gate 2 result: _____ of 7 checked. Minimum 5 of 7 required. Pass / Revise
Gate 3: Narrative Alignment
- The diagram tells a story from left-to-right or top-to-bottom (not circular with no entry point)
- The sequence of the diagram matches the verbal narration you will use
- The "moment of value" to the customer is visually distinct in the diagram
- Decision points (if any) are visually differentiated from data flows
- The most controversial architectural decision is not buried in a complex section
Gate 3 result: _____ of 5 checked. Minimum 4 of 5 required. Pass / Revise
Gate 4: Jargon-Free Test (verbal)
Read the 60-second verbal walk-through of this diagram aloud. Count acronyms used. Rate whether a non-technical business leader could follow without clarification.
Acronyms used (list them)
Gate 4 result: Pass (≤5 acronyms) / Revise (6+ acronyms)
Overall Audit Result
| Gate 1: Executive Readiness | Pass / Revise |
| Gate 2: Cognitive Load | Pass / Revise |
| Gate 3: Narrative Alignment | Pass / Revise |
| Gate 4: Jargon-Free | Pass / Revise |
| Cleared for customer presentation? | YES / NO: revisions needed first |
Priority revision before next presentation