myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectThe week after her board meeting, Fiona asked Marcus Chen how he had got Lakeshore's clean energy bid through. He opened two files. With fourteen days to bid for the government's Clean Energy Skills funding, his first draft had read like an architecture report: sixteen thorough, precise, unreadable pages. The second told a story. It opened with the question the ministry evaluator was already asking, set Lakeshore against the criteria that question implied, and ran to three pages. Lakeshore got the funding. This chapter teaches the difference between those two drafts. Architecture produces insight. Narrative makes that insight travel. You will learn the four-part structure that builds toward a decision: the tension the audience already feels, the reframe, the evidence and the action. And the discipline that runs through everything: lead with the question the audience is already asking, not the framework you used to find the answer.
By the end of this chapter, you'll be able to:
The week after her board meeting, Fiona asked Marcus how he had got the clean energy bid through, months before she arrived. He didn't explain. He opened two files.
When Lakeshore submitted its bid for the government Clean Energy Skills funding, Marcus had fourteen days to produce the document that would determine whether the institution received a share of $200M. He had the architecture: a capability model that showed exactly where Lakeshore was ready and where it was not, a Four Ares assessment that distinguished what the institution could deliver from what it would need to build, and a reference model framework that made the analysis traceable and credible.
He also had a choice about how to present it.
The first draft read like an architecture report. It opened with Lakeshore's strategic framework, described the capability assessment methodology, presented the findings in tabular format, and concluded with a recommendation. It was thorough, precise, and sixteen pages long. Marcus read it through and realised that a provincial ministry official with forty applications on their desk would never reach page three.
The second draft told a story. It opened with a question: "What does the Province need in a clean energy training partner?" It answered that question in three paragraphs: an institution with existing trades infrastructure, demonstrated employer partnerships, and the institutional agility to launch a new micro-credential within six months. Then it presented Lakeshore against those criteria: strong in trades capability, with proven employer partnerships in Health Sciences and a plan to extend them to the trades, honest about needing to build clean energy subject matter expertise, and proposing a phased approach that launched with what was ready while building what was not. The evidence was the same evidence from the capability model. The story made it readable, credible, and actionable. The brief was three pages.
Lakeshore got the funding.
Fiona read both drafts twice. The first one looked like her board deck.
The difference between those two drafts is the subject of this chapter. Architecture produces insight. Narrative makes that insight travel. The synthesis gives you the evidence. The story gives the evidence a structure that the audience can follow, remember, and act on. This chapter teaches you how to build that structure.
Curriculum Connection: In Closing the Strategy-Execution Gap (COR-BA-100), you first encountered Diane's question: "Why does this institution exist?" At that point, it was a strategic move that reframed a crisis. Here you can see the communication skill behind it. Diane did not ask a random question. She opened a narrative arc: an institution in crisis, a question that reframes the crisis, a journey toward an answer. The purpose question was the beginning of a story. This chapter teaches you how to build that structure deliberately.
Create a free account to access Communicating Business Architecture and start learning.