Chapter 5: Reference Models for Operational Design

Eight words changed the trajectory of Lakeshore's transformation.

Marcus had spent months redesigning the institution's strategy. The business model had been diagnosed and redirected. Capability gaps had been identified and prioritized. Investment was flowing toward employer partnerships, skilled trades expansion, and the Health Sciences model that would be replicated across the institution. By any architectural measure, progress was real.

Then Aisha Okafor, the Student Association President, said: "You've redesigned the engine. Have you redesigned the experience of being a passenger?"

It was not a question about strategy. It was not a question about capabilities. It was a question about what happens when a student actually tries to navigate the institution. And the answer, as Marcus knew immediately, was no.

The student experience at Lakeshore was fragmented. A prospective student encountered one set of processes during recruitment, a different set during admission, another during enrolment, and yet another when seeking academic advice or career guidance. Each process was managed by a different department, with different systems, different handoff points, and different definitions of what "student support" meant. Individual capabilities were adequate. The experience they produced together was not.

This chapter is about the reference model artifact that makes that problem visible: the recipe card. Where the capability model (Chapter 4) shows what the institution must be able to do, the recipe card shows which capabilities must come together to produce a specific outcome for a specific stakeholder. It is the difference between having all the ingredients in the pantry and knowing the recipe.