A student visa cap arrived without warning. An executive team convened. Forty-seven ideas went on the whiteboard, and not one of them was in the five-year plan. The plan had nothing to say about what had just happened.
That's not a failure in execution. It's a design flaw, and the design flaw is in the instrument.
You know this feeling even without that specific crisis. You've been in the offsite. The plan goes into the shared drive. The board signs off and the organisation aligns. Then something shifts (a funding cut, a regulatory change, a competitor moves) and you discover the plan has no mechanism for this. It's not because the analysis was wrong, or because execution was weak. It's because the plan was built to predict a future, and the environment no longer holds still long enough to be predicted.
Strategic planning isn't failing because the wrong people are in the room or because the strategy wasn't clear enough. It's failing because the planning cycle was built for a world that has stopped cooperating with it. The organisations responding well aren't writing better plans. They're replacing the instrument. The ones that haven't are finding out what that costs. The higher education sector makes the failure unusually legible.
The Most Useful Diagnostic First
Before we get into the structural argument, here's a test you can run in your next leadership meeting.
Ask these four questions. Not rhetorically. You're asking to see what evidence exists.
Are we doing the right things? Not "are we busy", but are we genuinely focused on what matters to the people we exist to serve? Evidence means trade-offs are documented: what you chose to focus on, and what you explicitly chose not to.
Are we doing them the right way? Do the capabilities actually exist to deliver what the strategy commits to? Evidence means an honest assessment of capability, not a confidence vote.
Are we getting them done well? Are stakeholders experiencing the value you intend to create? Evidence means there are outcome metrics, not just activity metrics.
Are we getting the benefits? Are the people you exist to serve actually better off? Evidence means actual measurable stakeholder impact, not just project completion.
In most organisations, the most common answer you'll hear to any of these is some version of: "We think so, but we don't have evidence." That answer is the diagnostic you need. It doesn't mean the people are wrong. It means the planning cycle never required evidence in the first place. It only sought alignment.
The Four Ares questions come from governance research developed in the 1990s by John Thorp, who noticed that organisations were consistently approving projects that delivered outputs but not outcomes. The four questions were designed to create accountability across the full arc from strategic intent to stakeholder result. They form the backbone of the Design4 cycle, which we'll return to shortly.
If your team can't answer these questions with evidence, it tells you something about the current planning cycle. The first thing to do is call it out, not as an indictment but as data. What these questions reveal is the gap between what the plan assumed and what's actually true.
Why the Plan Fails Before Execution Begins
Traditional strategic planning operates on the foundational assumption that the future is knowable enough to plan for in advance.
You gather data, model scenarios, build a roadmap. If the analysis is right and execution is strong, the plan delivers. That assumption was reasonable enough when environments changed slowly. It became a structural liability when they started changing faster than organisations could plan or adapt.
The operating environment now moves faster than the planning cycle in most sectors. When this occurs, the consequence is specific. The strategic plan doesn't just become outdated, it becomes a constraint. The organisation has committed resources to a direction, the environment has shifted, and there are now two bad options: maintain a plan that no longer fits, or abandon it and improvise. Most organisations will oscillate between the two, but neither produces the outcome the plan promised.
Four specific failures result.
1. The prediction model is blind. It cannot detect changes in stakeholder needs before they become crises; it can only update when the planning cycle resets it.
2. Choices are locked. The organisation cannot revisit commitments made at the planning offsite when the environment shifts six months later.
3. Capability cannot compound. The organisation assesses readiness once a year at best, rather than building the capability to decide faster with each turn.
4. Strategy is unfunded. In most organisations, the strategic plan and the operating budget are separate instruments. Strategy sets direction, while the annual operating cycle controls resources. Strategic commitments get actioned when funding aligns opportunistically (grants, discretionary budgets, lucky timing) and deferred when it doesn't. The plan looks bold, but the resource flows tell a different story.
This is what structural failure looks like in practice. It's not a plan executed badly. It's a plan that was the wrong instrument for the environment it was supposed to navigate.
The diagnostic question that matters isn't "did we execute the plan?" It's: "Is our planning cycle itself capable of keeping pace with the rate of change in our environment?" For most institutions today, the honest answer is no.
Why Higher Education Makes It Visible
Every sector is experiencing some version of the structural failure we just described. Higher education is experiencing it in a form that is unusually fast, unusually visible, and unusually instructive, because the core product of a university, knowledge and credentialing, has become almost entirely digitisable. When this happens to a product, it can be unbundled, repriced, and scaled by a competitor that carries none of the incumbent's cost structure.
By Q1 2026, Coursera had reached 205 million registered learners, and its late 2025 merger with Udemy created a platform offering credentialing at a fraction of the cost of a traditional degree. These platforms aren't competing with universities on traditional terms. They're redefining what the product is. The World Economic Forum estimates 40% of the global workforce will require significant reskilling by 2030, and students are increasingly treating education as a continuous condition of working life, not a one-time preparation for it.
The planning model itself has constrained the response of most institutions. A 2025 Future Campus analysis of 28 university flagship strategies found that not one of them acknowledged AI as a fundamental threat to the institutional business model. The plans treated it as a technology question, not a structural one. The plan exists. The disruption exists. But the plan has no mechanism for absorbing what it didn't anticipate.
The higher education governance structure compounds the problem. Shared governance (faculty consultation, committee review, broad consensus) was designed for accountability in a stable environment. In a high-velocity one, it functions as a structural brake. Decisions a digital-first competitor makes in days can take months to reach consensus in a traditional institution. That's not a management failure. It's a design consequence.
You don't have to work in higher education to recognise this pattern. Universities are simply a sector where the dysfunction is unusually legible from the outside: everyone understands committee governance, long planning cycles, and the gap between what a five-year plan says and what the institution actually does in a crisis. The mechanism is the same one operating in your organisation. This sector just makes it easy to see.
What Replaces Strategic Planning
The alternative isn't the absence of strategy. It's a different structure for making strategy continuous.
Any successor to strategic planning must do four things the plan cannot, and they map directly to the four failures just named. It must detect changes in stakeholder needs before they become crises. It must produce real choices (not priorities, choices) on a continuous basis. It must build capability into the decision-making cycle itself, so each turn makes the next one faster. And it must connect strategic direction to the resource allocation decisions that actually control what gets done. The Design4 cycle was built to meet exactly those requirements.
Four structural transitions make this concrete.
From prediction to sensing. The planning cycle is a prediction instrument. The Design4 cycle is a sensing instrument. Building the infrastructure to detect changes in stakeholder needs, competitive environment, and capability gaps on a rolling basis doesn't have to be expensive. It has to be continuous. But infrastructure alone isn't enough. The people with the most current intelligence (those in daily contact with students, employers, and competitors) are often structurally excluded from the strategy conversation. Sensing only works if the organisation has also decided whose knowledge it is willing to trust. The test is whether you are finding out about significant shifts before they require emergency responses, or after. For the specific signal categories to watch, see Your Strategy Failed. Your Second One Will Too.
From documents to choices. Most strategic plans contain aspirations and priorities. Few contain real choices, those explicit decisions about what the organisation will not do, what it will stop investing in, and what it will exit. A real choice doesn't just name what you won't do, it also must make a claim about why your chosen path creates more value for the stakeholders you're trying to serve than any alternative available to them. Running the Define phase of the Design4 cycle continuously means the organisation is always making and revisiting its trade-offs, rather than setting them once and leaving them in the shared drive. If you can't name three things your organisation explicitly chose not to do in the past year, the planning cycle has been producing alignment, not strategy. For a diagnostic of which trap that produces, see Three Forces That Make Strategy Fail.
From planning to capability. The most durable outcome of a continuous cycle isn't a better strategy. It's a more capable organisation. By the third or fourth turn, the question your team is asking has shifted from "did we execute the plan?" to "are we the kind of organisation that can respond well when the plan runs out?" For the full argument on why this compounds, and what it means for how your organisation faces the next disruption, see Your Strategy Failed. Your Second One Will Too.
From direction to resource alignment. Most strategic plans set direction without commanding resources. The operating budget is a separate instrument, controlled on a separate cycle, and strategic commitments get funded only when discretionary dollars align, or when someone advocates hard enough. A continuous cycle doesn't just define what to do, rather it creates the discipline of connecting those choices to what actually gets funded. The test isn't whether the strategic plan was approved. It's whether the operating budget reflects it.
The shift isn't conceptual. It's structural. The strategic plan asks: "what direction are we heading over the next three to five years?". The continuous cycle asks: "what's true right now, and are we still oriented to it?". Those are different questions, and they require different instruments.
The Design4 cycle runs four questions in a loop. Discover what stakeholders genuinely need. Define the strategic choices (real ones, with explicit trade-offs). Develop the capabilities the choices actually require. Deliver in a way that stakeholders experience as value. Then feed the evidence from the Deliver phase back into Discover, and run the cycle again.
The first pass through the Design4 cycle takes the most energy. You're establishing purpose for the first time, making choices that have been avoided, assessing capabilities honestly rather than optimistically. It's slower than writing a plan.
But the second pass is faster. You have evidence, and you know your stakeholders better. You've built the muscle of making strategic trade-offs explicitly. By the third pass, something qualitatively different has emerged. It's not just a better strategy, but the organisational capacity to keep producing good decisions as the environment changes. Each cycle makes the next one faster.
One other thing is worth calling out. The first pass through the cycle is the hardest, not just because it requires more energy, but because it surfaces things the strategic plan had been quietly papering over. Gaps in capability, choices the organisation avoided rather than made, and assumptions about stakeholder needs that haven't been tested in years. That's not the cycle failing. That's the cycle working. The discomfort in the first turn is what the strategic plan was costing you all along, but you just couldn't see it.
For a deeper look at where the chain between strategy and execution specifically breaks, and the four connections that need to be maintained, see Strategy to Execution: How to Close the Gap.
What It Looks Like From the Inside
The full story behind that executive team meeting at the start.
One federal policy change wiped out roughly half the international enrolment at a regional polytechnic in a single decision. In revenue terms, this represented a thirty-eight million dollar hole in a hundred-and-eighty million dollar budget.
The executive team convened over two hours. Experienced leadership, a whiteboard, and by the end of the meeting, there were forty-seven ideas on the board. Revenue diversification. Domestic recruitment pivots. New program development. Cost reduction. Partnerships. Each idea was someone's answer. Collectively, they had no mechanism for choosing among them.
The five-year strategic plan, approved eight months earlier, was silent on the scenario. It wasn't a bad plan. It had simply been built on the assumption of continued international enrolment growth. When that assumption was invalidated overnight, the plan had nothing to offer.
The problem wasn't the people in the room, as every one of them was experienced, motivated, and working hard. The problem was structural. The institution had no continuous sensing mechanism for detecting shifts before they became crises. It had no shared, decision-grade purpose filter for evaluating competing responses, and it had no capability map that separated genuine readiness from institutional aspiration. The planning cycle had never required those things, all it had required was alignment.
What changed the outcome wasn't a better plan, rather it was building a better decision-making structure. Over the following months, the institution did four things:
1. Developed a purpose statement that could filter decisions rather than just inspire them
2. Made explicit strategic choices that named what the institution would and wouldn't do.
3. Completed an honest capability assessment that separated where it was ready to move from where it wasn't.
4. Redesigned at least one service starting from what students and employers actually needed, rather than from the org chart.
Eight months later, a two-hundred million dollar clean energy funding announcement arrived with a sixty-day application window. The same team that had spent ninety days on forty-seven ideas made a clear, documented decision in two weeks. Same people. Different structural capacity.
That's the outcome that a continuous cycle produces. Not a better plan, but the ability to respond well when the plan is no longer relevant.
The Institutions Getting It Right
Two higher education institutions offer useful case studies in what structural agility looks like in practice.
Arizona State University in the U.S. built an online learning hub (EdPlus) that scaled to 120,000 students. More significantly, it moved IT from a back-office function into a collaborative driver of institutional strategy, integrating 32 colleges into a single data view via a Salesforce partnership. The result was real-time visibility across the institution, the prerequisite for making informed decisions at speed rather than waiting for the planning cycle to surface what's working. Adaptive courseware introduced through this infrastructure lifted freshman retention from 73% to 85%. This is an example of prediction to sensing made structural. The institution can now detect what's working before a problem compounds, rather than discovering it a year later in the annual review.
Coventry University in the UK didn't improve its planning cycle. It questioned the product the cycle was planning for. The institution replaced its semester model entirely, moving to six-week block delivery modules and running six intake cohorts per year instead of two. Students can now pause and restart their studies without losing an academic year. Student satisfaction reached 93% in 2025, in a sector where satisfaction has been falling. That's an example of "documents to choices" in practice. Rather than optimising the semester model, Coventry asked whether the model itself was the right choice for the stakeholders it was trying to serve, and made the explicit decision to exit it.
What both institutions share isn't a technology investment or a charismatic president. It's a structural decision to treat sensing, deciding, and learning as continuous processes rather than annual events.
What the Course Adds
This pillar post gives you the structural argument and the framework outline. The full course, Closing the Strategy-Execution Gap, gives you the implementation path.
It follows one institution through every turn of the cycle. From the forty-seven-ideas crisis to the clean energy response eight months later. Not as a tidy success story, but as a real institutional arc with governance resistance, capability gaps, leaders who disagreed, and choices that were genuinely uncomfortable. The case study is the curriculum.
If you're carrying this argument into a leadership team that isn't convinced yet, the course gives you the diagnostic tools, the worked examples, and the language to make the case in the room where decisions actually happen.
Frequently Asked Questions
Our institution has tried adaptive planning before and it didn't stick. Why would this be different?
Adaptive planning frameworks usually fail in large institutions because they're applied to the planning process without changing the governance model underneath it. The Design4 cycle isn't a project management methodology. It's a governance structure that changes who asks which questions, when, and on what evidence. If the underlying governance model remains unchanged, adaptive planning produces more documents, not more timely, well-informed decisions.
We have a five-year plan approved by the board. We can't abandon it mid-cycle.
You don't need to. The five-year plan sets strategic direction. The continuous cycle manages the gap between that direction and the current environment: sensing when the environment shifts, surfacing choices the plan didn't anticipate. It's additive, not a replacement.
How do we get leadership buy-in when the board expects an annual plan?
Start with the diagnostic, not the framework. Run the four questions with your senior team and ask for evidence, not confidence. The silence that typically follows is usually sufficient to open the conversation. The board approved the plan. The plan can't answer these questions. That tension is the case for the cycle.
If you're not in a position to run the diagnostic at senior team level, start smaller. Run the four questions on your own area of work. Find the one gap where your team's honest answer is "we think so, but we don't have evidence." Bring that specific gap (documented, not argued) to a sponsor. One real gap is more persuasive than a structural case. Build the mandate one cycle turn at a time.
Isn't this just scenario planning?
Scenario planning asks "what if?" and builds responses to imagined futures. It's still a prediction instrument: it predicts multiple futures instead of one. The Design4 cycle asks "what's true right now?" and builds the capacity to respond to what actually happens. They can coexist. They're solving different problems. Scenario planning manages imagined futures; the cycle manages the distance between your current state and what stakeholders actually need today.
How long before the cycle produces a visible difference?
The first pass through the cycle is the most effortful and the most uncomfortable, particularly in Define where teams have to make and defend real choices. Most institutions see meaningful improvement in decision quality within six to eight months of beginning Discover in earnest. The larger outcome (the organisational capacity to respond well under disruption) takes two to three full cycle turns to become durable and self-reinforcing.
This sounds right for a university. Does it apply in other sectors?
The structural argument applies wherever the environment is moving faster than the planning cycle. Higher education is a useful demonstration because the dysfunction is unusually legible from the outside: committee governance, long planning horizons, and the gap between a plan and a real-time crisis are visible in ways that are harder to see in sectors with less transparent internal dynamics. The mechanism is identical in healthcare, government, professional services, and large corporates. The sector is the example. The structural failure is the pattern.
The Practitioners Who Do This Work
The practitioners who do this work don't become better planners. They become the people their organisations rely on when the environment moves in a direction the plan didn't anticipate.
Before you bring this argument into a leadership meeting, be clear about one thing: the current planning cycle isn't just a planning instrument. It distributes authority: budget control, visibility, credit, accountability. A continuous cycle redistributes those things. For some leaders, the obstacle won't be conceptual. The structural case will land, and they still won't move, not because they don't understand it, but because understanding it and acting on it are different problems when your position is built on the instrument you're being asked to replace. That's the political reality stated plainly. Some resistance is political: the planning cycle is the source of the leader's authority, and they won't trade it. Some is epistemological: they genuinely believe the plan still works. Neither responds to a better argument. Know which situation you're in before you walk into the room. And if you don't have the mandate to act on what the cycle surfaces, decide whether to build it before you start, or to start small enough that you don't need it yet. In some institutions the obstacle is neither political nor epistemological, rather the governance model itself prevents adaptation even when leaders want it. That is a different problem, and naming it clearly is the prerequisite for addressing it.
The discipline that does this work is business architecture. Not in the sense of org charts or governance diagrams, but in the sense defined here: the practice of building the connections between what an organisation decides and what it actually becomes. The Design4 cycle is the operating framework a business architect uses to make strategy continuous rather than periodic. The four transitions this piece describes (from prediction to sensing, from documents to choices, from planning to capability, from direction to resource alignment) are the concrete work of that role. If you're looking at this piece and thinking "we need to build this," a business architect is the practitioner who owns it.
The strategic plan will keep being written. The board will keep expecting it. What changes is what sits alongside it, and who built it.
You already know the next disruption is coming. The question isn't whether your organisation will face one. It's whether you will be the person who built the capability to respond before it arrived. That's what the cycle is. Not a planning tool. A way of becoming the kind of leader your organisation needs when the plan runs out.