Strategic Architect Framework: Microsoft CSA Training Program

Module 03: Visual Communication Workbook

Cognitive Load & Visual Communication
The core question: Does your diagram create clarity or kill deals? This workbook takes you through the five visual communication principles and applies them to a real architecture diagram you are currently using in a customer engagement.
Customer / Engagement
Diagram under review

Section A: Diagram Audit

Print or display the diagram you plan to show this customer. Answer each question honestly before modifying anything.

Audit QuestionYes / Partially / NoEvidence or Note
Can a non-technical executive understand the business outcome in 30 seconds?
Is there a clear visual hierarchy: the most important element stands out?
Are there fewer than 12 distinct elements or components?
Is every acronym or technical term either explained or absent?
Does the diagram have a title that states the business outcome?
Is the color usage meaningful (not decorative)?
Are all lines and arrows directional and labeled?
Is there a "before" state that contextualizes the "after"?
Could this diagram be used by the customer to explain the project internally?

Section B: Cognitive Load Assessment

Based on Mayer's Cognitive Theory of Multimedia Learning, high cognitive load diagrams cause audiences to stop processing and start defending. Measure your diagram's load.

Element Count

Count every distinct element in your diagram (boxes, icons, labels, lines, swimlanes).

Total element count
Target: ≤12 for executive audience, ≤20 for technical audience

Acronym Count

List every acronym visible in the diagram. Then list which ones a CFO or business sponsor would not know.

Hierarchy Test

If you cover the title and legend, can someone identify the single most important element in 10 seconds? (Size, position, or color should communicate primacy.)

Section C: Audience Versions

A single diagram is rarely right for all audiences. Document which version you have and which you need to create.

AudienceVersion NeededDo you have it?Key Difference from Current Version
C-Suite / BoardBusiness outcome diagram (3–5 elements)
VP / DirectorStrategic architecture (8–12 elements)
Engineering teamTechnical deep dive (full detail)
Procurement / LegalSecurity and compliance view

Section D: The Jargon-Free Narration

Write the 60-second verbal narration you would use to walk a non-technical executive through the diagram. No jargon. Start with the business outcome. End with what changes for the customer's customers.

Section E: Before / After Redesign Notes

List the specific changes you will make to the current diagram based on this audit. Be specific: "remove the NSG icons from the executive view" not "simplify."

Current ElementChangeReason