Marcus had the right answer. Eight months into Lakeshore's transformation, he had a validated purpose, a clear strategic direction, a capability model, and a reference model framework that gave every conversation a shared vocabulary. Then he walked into the board meeting. He opened with the capability heat map. Board chair Helen Marchetti was checking her phone by slide three. James Firth was flipping to the budget number. Diane caught Marcus's eye and gave a small shake of her head. The diagnosis was right. The communication was failing. This chapter names the models-to-meaning gap, the reason architecturally sound work routinely fails to influence decisions, and introduces the orientation that closes it: audience-first thinking. Not what you know. What the room needs to hear.
By the end of this chapter, you'll be able to:
Marcus Chen had the right answer. He just couldn't get anyone to listen.
Eight months into Lakeshore Polytechnic's transformation, Marcus had something most organizations never achieve: a validated purpose, a clear strategic direction, a capability model that revealed exactly where the institution needed to invest, and a reference model framework that gave every conversation a shared vocabulary. The Design4 cycle had worked. The Four Ares governance questions had cut through political noise. The HERM reference models had turned vague disagreements into precise, structural diagnoses. By any measure, the architecture was sound.
Then he walked into the board meeting.
Marcus opened with the capability heat map. He explained how the HERM Business Capability Model had been adapted for Lakeshore, how the colour coding reflected maturity gaps, how the enabling capabilities in the bottom row were the ones constraining the institution's ability to execute its new strategic direction. He was thorough. He was accurate. He was organized.
He was also losing the room. Board chair Helen Marchetti was checking her phone by slide three. James Firth, the VP Finance, was flipping ahead in the deck looking for the budget number. Two external board members were exchanging glances that said: "I don't know what I'm looking at." Diane Okoro, the board member who had catalysed the entire transformation, caught Marcus's eye and gave a small shake of her head. Something was wrong.
The diagnosis was right. The communication was failing.
This chapter is about why that happens and what to do about it. Not in general terms. Specifically for business architects: people who have done the cross-boundary synthesis, who have the evidence, who can see the organizational picture more clearly than almost anyone in the room, and who routinely fail to translate that clarity into influence.
Curriculum Connection: If you completed Building the Common Language (COR-BA-101), you saw the 47 Ideas meeting from the vocabulary side: a room full of smart people with no shared framework for organizing their thinking. Here you see it from the communication side: Marcus had the shared framework, but could not get anyone to listen. The architecture was sound. The communication had not been designed. This course teaches the discipline that closes that gap.
If you haven't completed Closing the Strategy to Execution Gap (COR-BA-100) and Building the Common Language (COR-BA-101):
This course builds on two earlier courses in the COR-BA series. Here is what you need to know to follow the material:
The Design4 Framework organizes business architecture into four continuous phases: Discover (anchoring in organizational purpose), Define (making strategic choices through Roger Martin's Strategic Choice Cascade: Winning Aspiration, Where to Play, How to Win, Capabilities Required, and Management Systems), Develop (designing capabilities), and Deliver (operationalizing value). Each phase is governed by one of the Four Ares questions: Are we getting the benefits? Are we doing the right things? Are we doing them the right way? Are we getting them done well? The cycle is continuous, not linear.
Reference models are shared vocabularies that make organizational design repeatable and transferable. A Business Model Canvas describes how an organization creates and captures value. A capability model maps everything an organization must be able to do, organized into value chains and enabling capabilities. Recipe cards identify which capabilities need to combine to produce a specific outcome. These tools are conversation instruments, not just diagrams.
Lakeshore Polytechnic is a case study that runs through all three courses. Lakeshore is a mid-sized polytechnic that faced a $38M budget crisis when federal visa policy changes cut international enrolment by more than 50%. Under VP Strategy Marcus Chen's leadership, the institution used the Design4 cycle to rediscover its purpose, make hard strategic choices (prioritizing Health Sciences and Skilled Trades, phasing out underperforming programs), identify capability gaps, and redesign its approach to student experience. The institution later adopted the HERM reference models as its shared vocabulary, which revealed structural gaps that had previously been invisible.
Key characters: Marcus Chen (VP Strategy, protagonist), Diane Okoro (external board member, mentor), James Firth (VP Finance), Sandra Mwangi (VP Academic), Tom Beaulieu (Dean of Health Sciences), Priya Sharma (Director of International Education), Aisha Okafor (Student Association President).
You can follow COR-BA-102 without the earlier courses, but the full narrative context will reward you if you take them.
Create a free account to access Communicating Business Architecture and start learning.