myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectSix months after the crisis that nearly shut them down, the leadership team gets another disruption. This time, instead of panic and forty-seven ideas, they ask four questions and make a decision in two weeks. The environment did not get easier. The organisation got better at responding to it. This chapter shows you how the four phases reinforce each other, what breaks the cycle, and how repeated practice builds the adaptive capacity that separates organisations that survive disruption from those that grow stronger through it.
By the end of this chapter, you'll be able to:
Eight months into the Design4 process, Lakeshore Polytechnic was moving. Not fast, not without friction, but moving. The purpose was clear. The strategic choices were made. Capability development was underway: Phase 1 was producing results as Skilled Trades programs adopted the employer partnership model, and the Labour Market Pulse report had become a fixture in program planning conversations. The student experience working group was piloting the "career launchpad" prototype with graduating Health Sciences students. The Regional Campus, once marked for closure, was being studied as a delivery model worth replicating.
Two weeks earlier, Ridgemont College, a neighbouring institution that had maintained a broad program portfolio through the crisis, announced it was closing its business and IT programs entirely. The programs Lakeshore had chosen not to invest in were the same ones a competitor had been forced to shut down. Sandra Mwangi brought the news to the leadership meeting with a quiet observation: "That could have been us. It would have been us, if we'd tried to keep everything running." It was a sober validation of the "where not to play" choices the team had made six months earlier.
Then Marcus got a call from the provost's office on a Tuesday morning.
The provincial government had just announced $200 million in new funding for post-secondary institutions, but with conditions. The funding was earmarked for programs in skilled trades, healthcare, and clean energy technology, with a requirement that funded programs demonstrate employer co-design and guaranteed work-integrated learning placements. Applications were due in sixty days.
James Firth's first reaction was relief: "This is exactly the funding we need." Sandra Mwangi's first reaction was concern: "Sixty days. We don't have a clean energy program. Do we try to build one?" Tom and Priya split the pragmatic response between them: existing Health Sciences and Trades programs already met the criteria and could be applied for immediately, but the employers they'd been talking to in skilled trades were also asking about clean energy workforce training. The funding might catalyze the micro-credential idea that had emerged from the feedback loop.
Marcus looked at the whiteboard where Lakeshore's strategic definition was posted. Purpose: prepare people for careers in fields where the region has unmet needs. Where to Play: programs with documented employer demand and demonstrated institutional capability. How to Win: employer-integrated program design.
The funding announcement aligned with Lakeshore's purpose. Clean energy was an emerging field where the region had growing employer demand. But Lakeshore had no clean energy program and no capability to deliver one in sixty days.
Six months earlier, this situation would have produced a panic meeting and another forty-seven ideas. This time, Marcus knew exactly which questions to ask.
"Let's run the Four Ares," he said.
You've now walked through all four phases of the Design4 Framework: Discover, Define, Develop, Deliver. If this were a traditional planning methodology, we'd be done. The plan is complete. Go execute.
But Design4 isn't a planning methodology. It's a design discipline, and design is never done.
Think about what happens in practice. You discover your purpose and map your stakeholders. You define your strategic choices. You develop capabilities. You deliver value. And then the environment shifts. Stakeholder needs evolve. A new competitor emerges. Technology changes what's possible. A regulatory shift redraws the playing field. A government announces new funding with conditions that didn't exist when your strategy was written. The assumptions that underpinned your strategy six months ago may no longer hold.
If the organisation treats Design4 as a one-time exercise (plan it, build it, run it), the plan becomes obsolete while the organisation continues executing it. The gap between intent and reality widens, and the careful work of Discover, Define, Develop, and Deliver gradually loses its connection to the world the organisation actually operates in.
The alternative is to treat the four phases not as a sequence you complete, but as a flywheel you keep spinning (borrowing Jim Collins's metaphor for compounding organisational momentum). Each turn of the cycle builds on the last. Operational insights from Deliver feed back into Discover. Shifting stakeholder needs trigger strategic reassessment in Define. Evolving strategy drives capability evolution in Develop. And improved capabilities enable better operational designs in Deliver. The cycle continues, and each revolution makes the organisation more capable, more aligned, and more adaptive.
This is the flywheel effect: the initial turn requires the most energy, but each subsequent turn builds momentum. The organisation that has cycled through Design4 three times doesn't just have better strategy than one that planned once. It has a fundamentally different capability. It knows how to sense, choose, design, and deliver. It knows how to learn from each cycle and apply those lessons to the next. It has adaptive capacity.
This chapter examines how the complete cycle operates as an integrated system: how the phases connect, what governance keeps the flywheel spinning true, what traps can break the cycle, and how sustained cycling builds the meta-learning capability that is the ultimate source of organisational advantage.
In Practice: The funding announcement was Lakeshore's first real test of the flywheel: a strategic decision under time pressure using the framework it had built. The old Lakeshore would have produced a frantic brainstorming session and applied for everything it could reach. The new Lakeshore had a framework for asking: Does this align with our purpose? Do we have the capability? Can we deliver well? Those questions would determine whether Lakeshore applied cautiously or reached ambitiously.
Create a free account to access Closing the Strategy to Execution Gap and start learning.