Chapter 7: Building and Sustaining Reference Models

The Lakeshore story has a moment that most transformation narratives skip. It is not the crisis, or the intervention, or the breakthrough. It is the morning after.

Marcus has guided the institution through a Design4 cycle. The business model has been redesigned. Capabilities have been mapped and gaps prioritized. The clean energy pilot has demonstrated that the shared vocabulary works under pressure. The leadership team has practiced using reference models as governance tools. By every measure, the hard part is done.

And then someone asks: "Who maintains this?"

It is not a glamorous question. It does not appear in strategy presentations or board reports. But it is the question that determines whether everything Lakeshore built persists or decays. And it raises a deeper question, one that should organize everything you learn in this chapter: What is the minimum viable governance that sustains the competitive advantage of shared vocabulary without consuming more organizational energy than it produces?

Reference models are living artifacts. The institution's strategy will evolve. New capabilities will be needed. Old ones will become irrelevant. The external environment will shift. If nobody is responsible for keeping the reference models current, they will gradually drift from reality. Within a year, the BMC will describe a business model the institution no longer operates. Within two years, the capability model will list capabilities that have been reorganized beyond recognition. Within three years, the shared vocabulary that made the transformation possible will be an artifact in a folder that nobody opens.

There is a test that runs through everything in this chapter: Would the leadership team notice if the reference model disappeared? If the answer is yes, the shared vocabulary is alive. It is shaping conversations, informing decisions, changing how people think. If the answer is no, the reference model has become a repository artifact, maintained out of obligation rather than used out of need. Every governance decision in this chapter should be evaluated against that test.

A Tension Worth Naming

This chapter also creates a tension the course should be honest about. Chapters 1 through 6 position reference models as conversation tools. They succeed through use and fail through repository storage. The whole ethos of this course is that reference models are valuable when they live in the room where decisions are made, not in a document management system.

Now, Chapter 7 teaches governance infrastructure: formal versioning, review cadence, role definitions, change management frameworks. These are the mechanisms that keep reference models alive over time. But they are also exactly the kind of institutional overhead that can kill the conversational quality that makes reference models work.

The principle is this. The test is always the same. Is the governance serving the conversation, or has the conversation been replaced by the governance? If the reference model is maintained perfectly but nobody uses it in a meeting, the governance has failed. If the reference model is used in every meeting but never updated, the conversation is living on borrowed time. Healthy governance is the minimum structure needed to keep the conversation honest and current. Nothing more.

This chapter is about finding that minimum. It addresses the roles required, the governance cadence that keeps reference models alive, the bootstrapping challenge of getting started, and the organizational conditions that determine whether reference models will be adopted or ignored. At every point, the question is the same: does this serve the conversation, or does it replace it?