Chapter 1: The Communication Challenge

Fiona Lavoie had the right answer. She just couldn't get anyone to listen.

Sixteen months after the crisis began, and four months into her post as Lakeshore Polytechnic's Director, Business Architecture, Fiona had something most organisations never achieve. The institution had a validated purpose and a clear strategic direction: the work Marcus Chen had led in the first year. And it now had what she had built since arriving: the HERM reference models adapted as Lakeshore's shared vocabulary, and a capability gap assessment that showed exactly where the institution needed to invest. The Design4 cycle had worked. The Four Ares governance questions had cut through political noise. The reference models had turned vague disagreements into precise, structural diagnoses. By any measure, the architecture was sound.

Then she walked into the board meeting.

Fiona opened with the capability heat map. She explained how the HERM's 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. She was thorough. She was accurate. She was organised. She had asked herself, as she always did, which decision the work informed, and she knew the answer. She had trusted the heat map to make the case for her. Weeks earlier, Diane and Sandra had made her walk James Firth through one red cell before a meeting. She had taken the lesson as being about James.

She 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." Across the table, Marcus, there as the VP Strategy and not as the presenter, recognised the silence. He had stood on the other side of it. Diane Okoro, the board member who had catalysed the entire transformation, caught Fiona'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 organisational 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 watched Fiona arrive, bring the HERM, and run the gap assessment this board meeting is about. In that course she learned who needs to hear a finding first, when Diane and Sandra set the conditions for her session with James Firth, and she left with a question: who needs to hear it, and how? This course is the how. The architecture was sound. The communication had not been designed. This course teaches the discipline that closes that gap.

If You Haven't Taken the Earlier Courses: This course builds on Closing the Strategy-Execution Gap (COR-BA-100) and Building the Common Language (COR-BA-101). Here is what you need to know to follow the material:

The Design4 framework organises business architecture into four continuous phases: Discover (anchoring in organisational purpose), Define (making strategic choices through Lafley and Martin's Strategic Choice Cascade: Winning Aspiration, Where to Play, How to Win, Capabilities Required, and Management Systems), Develop (designing capabilities), and Deliver (running services that produce results, with the evidence of whether stakeholders are better off flowing back to Discover). 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 organisational design repeatable and transferable. A Business Model Canvas describes how an organisation creates and captures value. A capability model maps everything an organisation must be able to do: strategic, core 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 the series. Lakeshore is a mid-sized polytechnic that faced a $38M budget crisis when federal visa policy changes cut international enrolment by roughly half. Under the leadership of Marcus Chen, Vice-President of Strategy and Institutional Planning, the institution used the Design4 cycle to rediscover its purpose, make hard strategic choices (prioritising Health Sciences, Skilled Trades and Community Services, and phasing out general business and IT programs), identify capability gaps, and redesign its approach to student experience. Nine months in, Marcus posted a new role, and three months later Fiona Lavoie became Lakeshore's first Director, Business Architecture. She adapted the HERM reference models as the institution's shared vocabulary and ran a gap assessment that revealed structural gaps that had previously been invisible. Marcus now holds the strategist's seat.

Key characters: Fiona Lavoie (Director, Business Architecture, protagonist), Marcus Chen (Vice-President of Strategy and Institutional Planning), 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.