Chapter 1: The Problem Reference Models Solve

Fiona Lavoie started at Lakeshore Polytechnic on a Monday, twelve months after the crisis. Her title was Director, Business Architecture, a role that hadn't existed until Marcus Chen, Vice-President of Strategy and Institutional Planning, wrote the posting. Marcus spent her first morning walking her through the year.

You already know most of what he told her. You watched Marcus walk into an emergency meeting and walk out with forty-seven ideas and no direction. You followed the institution through a Design4 cycle that moved it from paralysis to adaptive capacity. And you watched him realise, at the end of it, that he had been holding two seats: the strategist who chose Lakeshore's direction, and the architect who was supposed to check it. Fiona was there to take the second.

She listened for an hour and asked few questions. Then she said something Marcus hadn't expected. "Every time you got stuck, it was the same problem. You didn't have the words."

She meant something specific. At every critical moment, the team had been slowed by the same invisible problem: they did not have a shared vocabulary for describing what their institution was, what it did, and what it needed to be great at.

When Marcus asked "Why does this institution exist?" he got five different answers. Some of that was real disagreement, and some was five leaders describing the same institution in five private vocabularies, with no way to tell which was which. A shared vocabulary makes the disagreement visible; it doesn't settle it. Settling it is the purpose work of COR-BA-100's Discover phase. Purpose in business architecture is not a preamble or a motivational statement. It is an active architectural element: tested through evidence, validated against stakeholder outcomes, and treated as a constraint on every subsequent choice. Without shared vocabulary, that testing cannot happen, and purpose remains aspirational rather than operational. When Marcus noticed that Health Sciences had embedded employer partnerships while Business Programs held an advisory meeting twice a year, he was observing a capability gap he had no shared language for naming or measuring. When Aisha Okafor challenged him on the student experience, she was describing an integration gap between siloed capabilities, but neither of them had a vocabulary for tracing which capabilities needed to come together.

The Design4 cycle worked. But it worked harder than it needed to, because every conversation required building vocabulary from scratch. Every workshop started with "What do we mean by...?" Every handoff required translating one group's language into another's.

Fiona had seen the alternative. She had spent six years at an Australian university while it adopted the Higher Education Reference Models, and she had watched a shared vocabulary turn arguments about words into arguments about choices. She had also watched one fail, and she knew why.

This chapter is about that invisible problem: the cost of not having a common language. And it introduces the solution: reference models, the shared vocabulary that makes strategic design repeatable, transferable, and governable. The course follows Fiona's first six months, as she brings that vocabulary to Lakeshore.

If You Haven't Taken COR-BA-100

This course builds directly on Closing the Strategy-Execution Gap (COR-BA-100). If you haven't completed it, here is what you need to know.

The Design4 framework organises business architecture around four phases that form a continuous cycle:

• Discover: Anchor in purpose. Ask Are we getting the benefits?
• Define: Make strategic choices. Ask Are we doing the right things?
• Develop: Design capabilities. Ask Are we doing them the right way?
• Deliver: Operationalise value. Ask Are we getting them done well?

These four governance questions are called the Four Ares. Together they assess alignment from purpose through to operations.

Strategic choices in the Define phase follow the Strategic Choice Cascade: five explicit decisions (Winning Aspiration, Where to Play, How to Win, Capabilities Required, Management Systems) that move strategy from aspiration to structure.

Lakeshore Polytechnic is the case study that runs through both courses. Marcus Chen, Vice-President of Strategy and Institutional Planning, faces a $38M budget shortfall after a federal cap on international student visas. An emergency leadership meeting produces forty-seven disconnected ideas and no plan. Board member Diane Okoro reframes the crisis as a design problem, not a resource problem, and guides Marcus through the Design4 cycle. Key characters include James Firth (VP Finance), Sandra Mwangi (VP Academic), Priya Sharma (Director of International Education), Tom Beaulieu (Dean of Health Sciences), and Aisha Okafor (Student Association President).

By the end of COR-BA-100, Lakeshore has defined its authentic purpose, made explicit strategic choices about where to play and where not to play, identified and begun closing critical capability gaps, and demonstrated adaptive capacity when a new opportunity (provincial clean energy funding) arrived on a 60-day deadline.

Three more facts carry into this course. Sandra chairs a standing quarterly forum that answers Are we getting the benefits?, and the board, through Diane, reviews the review. The Downtown Centre, a $4.2M-a-year lease that no longer fits the strategy, is in a phased exit decided on the record, with two floors sublet to employers for a clean energy micro-credential pilot still in design. And Marcus, seeing that he had been both the strategist and the architect checking his own strategy, posted a new role: Director, Business Architecture. This course opens on the morning the Director starts.

If any of this is unfamiliar, you will be able to follow this course, but you will get more from it if you complete Closing the Strategy-Execution Gap (COR-BA-100) first.