Chapter 4: Making Architecture Visible**
Marcus brought the full capability heat map to the board: twenty-seven capabilities, five faculties, 135 colour-coded cells, no annotation. The board saw a wall of colour that communicated nothing. Two weeks later, he presented the same data to Academic Council: six capabilities, five columns, one annotation line across the top. The audience saw the gap immediately, before Marcus said a word. Same data. One was an architecture artifact designed for architects. The other was a communication tool designed for a decision. This chapter teaches you to make that translation -- from comprehensive to clear, from artifact to instrument -- without distorting the insight. You will see both versions of the heat map the way James Firth would: quickly, with twelve other items on the agenda.
What You'll Be Able To Do
By the end of this chapter, you'll be able to:
- Simplify any complex architecture visual for a specific audience without distorting the insight it needs to carry.
- Organize a visual so the most important finding is visible first, and the audience's eye follows a logical path to the decision.
- Annotate an architecture visual so that a reader without architecture training can extract the key insight without you in the room to explain it.
Sign In to Access This Course
Create a free account to access Communicating Business Architecture and start learning.