Chapter 4: Define (Architecting Strategy)

Marcus had expected the Discover phase to be the hard part. It wasn't. Asking "Why do we exist?" was uncomfortable, but the team had leaned into it. The stakeholder mapping had been eye-opening. The STEEPL scan had been sobering but clarifying. By the time he presented the discovery synthesis to the board, there was genuine alignment around Lakeshore's purpose: the institution existed to prepare people for careers in fields where the region had unmet needs, to provide a post-secondary pathway for communities that would otherwise have none, and to serve as the talent pipeline that kept skilled workers local.

The hard part came next. Because purpose, however clear, doesn't tell you what to do. It tells you why. The "how" requires choices. And choices require saying no.

The first test came during a leadership retreat two weeks after the board presentation. Marcus structured the day around a single question: "Given what we now know about our purpose, our stakeholders, and our environment, where should Lakeshore focus?"

The conversation started well. Everyone agreed that Health Sciences and Skilled Trades were core: strong employer demand, clear stakeholder outcomes, purpose alignment, resilient enrolment. Community Services at the Regional Campus was similar: modest scale, but deeply connected to purpose and community need.

Then the conversation reached the Downtown Centre.

James Firth laid out the numbers. The Centre's lease cost $4.2 million per year for another twelve years. It had been designed for business and IT programs serving international students. With international enrolment down by more than half, the Centre was running at 35% capacity. The programs offered there had weak employer demand, no distinctive advantage over competitors, and no clear connection to the purpose the team had just defined.

Sandra Mwangi pushed back. "If we walk away from those programs, we're laying off faculty. These are real people with families."

"I know," Marcus said. "But the question isn't whether it's painful. The question is whether those programs are the right things for Lakeshore to be doing, given who we exist to serve."

The room went quiet. That was the Define question in action: Are we doing the right things?

The meeting broke twenty minutes later, and people filed out in small clusters, talking in low voices. Marcus stayed behind, gathering his notes without reading them.

Sandra caught him in the hallway. She wasn't angry, not exactly, but her voice had a weight that Marcus hadn't heard before. "You know David Chen has been teaching in that program for fourteen years. His daughter just started high school. And Miriam Baptiste is two years from her pension." She paused. "I'm not saying you're wrong. I'm saying that 'strategic focus' has a face, and it's people I eat lunch with."

Marcus didn't try to soften it. "I know."

"Good," Sandra said. "Because the moment you stop knowing that, you're just a spreadsheet with a title." She turned and walked towards the stairs, her heels clicking evenly on the tile. Not storming off. Just carrying something heavy and choosing to keep walking.

Marcus stood in the empty hallway for a long time after that. He'd said the right thing in the meeting. He believed it. But saying the right thing and feeling right about it were not the same experience, and he suspected they never would be. The question "Are we doing the right things?" was clean on a whiteboard. In a hallway where someone just told you the names of the people your strategy would displace, it was something else entirely.

---

In Discover, you anchored the organisation in purpose, mapped the stakeholder ecosystem, and scanned the environment. You now have a clear picture of why the organisation exists, who it serves, what those stakeholders need, and what external forces shape the playing field.

That's essential, but it's not enough. Understanding doesn't create action. Purpose without choices is just aspiration. And aspiration without focus is how organisations end up trying to do everything for everyone, doing nothing particularly well.

The Define phase is where understanding becomes commitment. Its governance question, "Are we doing the right things?", demands that the organisation move from insight to choice: Which stakeholders will we prioritize? Which markets will we serve? What value will we create that others can't or won't? And, just as importantly, what will we choose not to do?

This is the hardest phase for most organisations. Discover feels expansive and inclusive: you're learning, listening, mapping. Define feels like closing doors. And it is. Strategy, at its core, is the discipline of choosing what to focus on and what to sacrifice. If you aren't saying "no" to some opportunities, you don't have a strategy. You have a wish list.

The output of Define isn't a strategic plan in the traditional sense (a thick document full of goals, timelines, and initiatives that becomes obsolete the moment the environment shifts). It's a set of integrated choices and testable hypotheses about where the organisation will compete and how it will win. These choices become the blueprint for everything that follows: the capabilities you'll build in Develop and the operations you'll design in Deliver.

In Practice: Lakeshore's initial crisis response was a wish list, not a strategy. It included everything from "launch a corporate training division" to "partner with universities on degree pathways" to "invest in online program delivery." Each proposal had merit in isolation. None had been evaluated against the question "Is this the right thing for Lakeshore to be doing, given our purpose?" The Define phase was where that evaluation happened, and where some of those proposals were set aside.