myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectMarcus had spent over a year getting to this moment. The crisis. The forty-seven ideas. The Design4 cycle that turned a $38M budget shortfall into a disciplined strategic response. The reference models. The communication practice. All of it built toward a decision. And now the board had approved the Student Experience Transformation unanimously, grounded in architecture evidence, James Firth presenting the three-page business case, Diane asking the Four Ares questions, every answer evidenced. Marcus should have felt satisfaction. What he felt instead was a shift. The question was no longer "What should Lakeshore do?" The new question was: "Will the right thing actually get built?" This chapter is about that transition, from architect-as-designer to architect-on-the-build-site. What changes in your role, your relationships, and your daily work when the blueprints go on the wall and the builders arrive.
By the end of this chapter, you'll be able to:
Marcus Chen had spent over a year getting to this moment.
The crisis. The forty-seven ideas. The Design4 cycle that turned a $38M budget shortfall into a disciplined strategic response. The reference models that gave Lakeshore Polytechnic a shared vocabulary. The communication work that taught Marcus to walk into a room and make architecture useful to the conversation rather than invisible behind a heat map. All of it had been building toward a decision. And now the decision had been made.
The board had approved the Student Experience Transformation.
The vote was not dramatic. It was informed. James Firth walked the board through the business case, grounded in architecture evidence, compressed to three pages with appendices for anyone who wanted the detail. Diane Okoro asked the Four Ares questions: Are we doing the right things? Are we doing them the right way? Are we getting them done well? Will we get the benefits? Each question had a clear, evidence-based response. The capability gaps were defined. The value stream implications were mapped. The investment was justified not by enthusiasm but by structural diagnosis. The board approved unanimously.
Marcus should have felt the satisfaction of architecture work completed. What he felt instead was a shift. Something had changed in the room. The question was no longer "What should Lakeshore do?" That question had been answered. The new question was: "Will the right thing actually get built?"
This is the moment this course is about. The strategic decision has been made. The blueprints are on the wall. And the builders are arriving. Your role as a business architect is about to change. In the earlier courses, you designed. Now you oversee. You do not put down the blueprints. You pick up a hard hat.
This chapter introduces the transition: what changes when the decision to proceed is made, who you will now work with, what your role is (and is not), and how to think about the shift from architect-as-designer to architect-on-the-build-site.
If you haven't completed COR-BA-100, COR-BA-101, and COR-BA-102:
This course builds on three earlier courses in the COR-BA series. Here is what you need to know to follow the material.
The Design4 Framework organizes business architecture into four continuous phases: Discover (anchoring in organizational purpose), Define (making strategic choices), Develop (designing capabilities), and Deliver (operationalizing value). 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: what you learn in Deliver feeds back into the next round of Discover.
Reference models are shared vocabularies that make organizational design repeatable. A Business Model Canvas describes how an organization creates and captures value. A capability model maps everything an organization must be able to do. Recipe cards identify which capabilities must combine to produce a specific outcome. These tools are conversation instruments, not just diagrams.
Communication skills are what make architecture work land with real audiences. The business architect learns to translate architectural findings into language that different stakeholders can hear and act on, to facilitate strategic conversations, to write for decision-makers, and to build a communication rhythm that keeps architecture visible over time.
Lakeshore Polytechnic is a case study that runs through all four courses. Lakeshore is a mid-sized polytechnic that faced a $38M budget crisis when federal visa policy changes cut international enrolment by more than 50%. Under VP Strategy Marcus Chen's leadership, the institution used the Design4 cycle to rediscover its purpose, make hard strategic choices (prioritizing Health Sciences and Skilled Trades, phasing out underperforming programs), identify capability gaps using HERM reference models, and build a communication practice that connected architecture to governance. The board has now approved a Student Experience Transformation: a set of digital and operational changes designed to make the student experience Lakeshore's competitive differentiator.
Key characters: Marcus Chen (VP Strategy, protagonist), 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-103 without the earlier courses, but the full narrative context will reward you if you take them.
Create a free account to access Shaping What Gets Built and start learning.