The morning after the board meeting, Fiona sat with two versions of the same finding. The capability heat map: technically excellent, ten minutes of explanation, no traction. The sentence Diane had pulled out of her: "Only one of the three faculties our strategy depends on has structured employer partnerships, and our entire strategy depends on industry-connected graduates." Same insight. The sentence did in ten seconds what the heat map had failed to do in ten minutes. Fiona then listed the audiences who needed this finding: the board, Sandra's academic team, Tom Beaulieu, Priya's international recruitment team, frontline advisors, three employer associations. Identical evidence. Six fundamentally different conversations. This chapter gives you the tool for managing that complexity: the stakeholder communication map, which tells you who needs what, in what register, in what format, and at what moment in the Design4 cycle.
By the end of this chapter, you'll be able to:

The morning after the board meeting, Fiona sat in her office with two versions of the same finding open on her screen.
The first was the capability heat map she had presented to the board. It showed, with structural precision, that Lakeshore's enabling capability "Engagement & Relationship Management" was assessed at maturity level 4 in Health Sciences, level 2 in Skilled Trades, level 3 in Community Services (resting on the personal networks of three long-tenured staff), and level 1 in Business Programs and Arts & Design. The reference model made the gap visible, measurable, and traceable to the institution's strategic direction. As architecture, it was excellent work.
The second was the sentence Diane had pulled out of her when the board's attention was failing: "Only one of the three faculties our strategy depends on has structured employer partnerships, and our entire strategy depends on industry-connected graduates."
Same insight. One sentence versus one heat map. And the sentence had done in ten seconds what the heat map had failed to do in ten minutes.
Fiona started making a list. Before the board's next meeting, she needed to communicate this same finding to six different audiences: the board (for investment approval), Sandra Mwangi's academic leadership team (for faculty cooperation), Tom Beaulieu (for mentorship of other faculties), Priya Sharma's international recruitment team (for revised value propositions to partner institutions), frontline advising staff (for student communication), and three external employer associations (for partnership development). Four months into the job, she knew two of those audiences barely at all: she had never met Priya's team, and the employer associations knew Lakeshore through Tom, not through her. The architecture evidence was identical in every case. But Fiona was beginning to realise that identical evidence required six fundamentally different conversations.
Marcus read the list over her shoulder mid-morning. "Sandra's team will hear the heat map as a verdict," he said. "Business Programs most of all. That faculty is red because we chose to teach it out, and it will still feel like a grade in front of their peers. Talk to its chair before anyone sees a colour." Fiona hadn't known the chair, or that the teach-out still stung. She added a line to Sandra's row.
This chapter gives you the tool for managing that complexity. It is called a stakeholder communication map, and it is the most useful preparation step an architect can take before any communication effort. If Chapter 1 taught you that audience-first thinking is the orientation, this chapter teaches you how to operationalise it.
Create a free account to access Communicating Business Architecture and start learning.