myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectIf the previous chapter named the problem, this chapter introduces the method. You will see the Design4 Framework in full: four interconnected phases that operate like gears, not sequential steps. You will learn the governance questions that keep each phase honest, the twelve artifacts that make alignment visible and debatable, and why the organisations that pull ahead are not the ones with the best plans but the ones that have learned how to learn.
By the end of this chapter, you'll be able to:
Two weeks after the 47 Ideas meeting, Marcus Chen was no closer to a path forward. The ideas had been sorted into categories, assigned to working groups, and loaded into a project tracking spreadsheet. None of that had made them more coherent. The board wanted a recovery plan by the end of the quarter. The faculty union was demanding transparency on potential layoffs. And the "Revenue Diversification Task Force" had added three more ideas to the list, bringing the total to fifty.
It was Diane Okoro who changed the conversation.
Diane was an external board member, recently retired after leading a regional health authority through its own transformation a decade earlier. She had watched the 47 Ideas meeting from the boardroom video feed, and she'd asked Marcus for coffee afterward. He'd expected sympathy. What he got was a question.
"You have fifty ideas," she said. "How many of them have you tested against the question of why Lakeshore exists?"
Marcus paused. "We know why we exist. We're a polytechnic. We educate students and prepare them for careers."
"That's what you do," Diane said. "I asked why you exist. Those are different questions. And until you can answer the second one with something specific enough to choose among your fifty ideas, you're going to keep adding to the list."
She pulled a napkin from the dispenser and drew four circles, each one feeding into the next. "When I took over the health authority, we had a version of your problem. Too many priorities, not enough focus, and a budget that couldn't support all of them. A colleague introduced me to a way of thinking that changed how I approached the whole thing. Four questions. That's it."
She wrote them around the circles:
"Every organisation I've seen struggle," Diane said, "has at least one of those questions it can't answer. Most have two or three. The ones in real trouble can't answer any of them."
Marcus looked at the napkin. "And Lakeshore?"
"I watched your meeting, Marcus. You have fifty ideas and zero answers to any of those four questions. That's not a planning problem. That's a design problem."
Diane's napkin sketch, rough as it was, captured something essential. When most people hear "Business Architecture", they picture diagrams: org charts, process flows, systems maps with colour-coded boxes and arrows. Architecture, in the popular imagination, is something IT people do with modeling tools. Technical, abstract, and disconnected from the real decisions that drive an organisation.
This course takes a fundamentally different view.
Business Architecture, as we'll practice it, is a strategic management discipline. Its job isn't to produce diagrams for their own sake. It's to ensure that business investments deliver optimal value at an acceptable level of risk. It connects the dots between what the organisation exists to do (its purpose), what it chooses to focus on (its strategy), what it needs to be great at (its capabilities), and how it actually delivers value every day (its operations).
In Chapter 1, you saw the gap between strategy and execution, and why that gap persists. You saw how four specific disconnects break the chain from purpose to operations, and how the Four Ares governance questions can diagnose misalignment. Now it's time to move from diagnosis to design.
This chapter introduces the Design4 Framework that organises Business Architecture into a practical, repeatable discipline. You'll see how four interconnected phases create a continuous cycle of alignment, and you'll get your first look at the specific artifacts that make the "Big Picture" visible and actionable.
A fair question at this point is, "hasn't this ground been covered?" The Strategic Choice Cascade structures strategic decisions. The Business Model Canvas maps how value is created and captured. Capability mapping reveals organisational readiness. Each of these frameworks is powerful in its own domain, and Design4 draws on all of them. But none of them, on its own, solves the problem Diane identified on that napkin. What Design4 contributes is the integration architecture, the continuous cycle that connects purpose to strategy to capabilities to operations. It also provides the four-gaps diagnostic that identifies where those connections break, and the Four Ares governance that keeps the connections alive through ongoing practice. Individual frameworks are lenses. Design4's distinctive move is treating integration itself as a discipline, not a byproduct of good intentions.
Create a free account to access Closing the Strategy to Execution Gap and start learning.