From Projects to Performance: The Planning Evolution That Drives Strategy Execution
- Ben Chamberlain
- 3 days ago
- 5 min read
Ask most executives what Strategy Execution means and you will get a version of the same answer: it is Program Management on steroids. Deliver projects on time. Hit the milestones. Manage the budgets. These things matter — but they are not the goal. They are the mechanics.
The real goal of Strategy Execution is value realization — maximizing business value and accelerating the speed at which that value reaches the organization. And the gap between that goal and how most organizations actually plan their portfolios is where business value goes to die.
StrategyXF research — The Hidden Economics of Strategy Execution Failure: Quantifying the Business Value at Risk — found that of the total value in a typical organization's portfolio:
34% is unidentified
31% is lost
35% is deferred
That is not a project management problem. That is a strategic planning problem — and it starts long before a single project kicks off.
This page provides an overview of the planning evolution every organization needs to make. For the full exploration — the mechanics, the research, the operating model imperatives, and the practical path forward — read the complete guide (From Projects to Performance: The Planning Evolution that Drives Stratgey Excution) below.
Read the Guide: From Projects to Performance: The Planning Evolution that Drives Strategy Execution
Not a member? Apply to become a member
The Three-Stage Planning Evolution
Based on thirty years of experience and hundreds of conversations with organizations navigating operating model improvement, a clear pattern emerges. Most travel a recognizable path through three distinct planning approaches. The names are irrelevant — call them whatever works. What matters is recognizing the behaviors at each stage, understanding the ceiling each one imposes, and knowing what it takes to move beyond it.
This framing is understandable but dangerously incomplete.
Stage 1 — Project Driven: This is where most organizations start — and where many remain. Strategic objectives are defined, investment proposals flow in from across the business, and prioritization techniques select the best portfolio under budget and resource constraints. It looks like top-down planning. It is not.
Demand is generated bottom-up, independent of strategy. Strategy acts as a filter, not a driver. You never know if you started with the right investments — only that you selected the best from what was proposed. The model is also easy to game: teams quickly learn to overstate their project's strategic contribution to improve funding chances. And once approved, the portfolio is frozen for twelve months regardless of what changes. Set it and forget it — the annual cycle is a structural liability in today's environment.
Stage 2 — Initiative Driven: The Initiative Driven approach fixes two fundamental failures. First, it moves to true top-down derivation — strategy is decomposed, metrics are set at every level, and the initiatives identify themselves from the strategy rather than being proposed from below. You now know you started with the right investments. Second, it replaces the annual freeze with continuous planning — quarterly rebalancing, an eighteen-month rolling forecast, and a live connection between strategic priorities and portfolio decisions.
For many organizations this is genuinely transformative. But it has a critical blind spot: it almost always covers only discretionary investment — the 20–30% of the total budget that funds strategic change. The other 70–80% — operational activity and spend — continues on autopilot, ungoverned and unaligned.
Stage 3 — Enterprise Driven: The Enterprise Driven approach closes that gap. It introduces Business and Enterprise Architecture as a strategic planning essential — not a back-office IT discipline. The organization maps its full operating fabric — products, capabilities, value streams, processes, technology — and defines a target state aligned to strategic objectives. In many organizations that fabric has grown bloated through M&A, technical debt, and years of unrationalized redundancy — quietly consuming budget and impeding execution.
Architecture makes that redundancy visible. StrategyXF research shows that low-performing organizations lose 7.5% of total portfolio value to initiative redundancy alone. Rationalizing the operating fabric doesn't just reduce cost — it releases capital. Those savings, redeployed into growth investment, can increase available discretionary budgets by up to 39%. For the first time, the planning model covers all activity and spend — not just the discretionary slice.
It's Not Either/Or — The Sum is Greater Than the Parts
When these three stages are presented as a progression, the instinct is to treat them as a ladder — each rung replacing the one below. That instinct is wrong.
The Enterprise Driven approach doesn't replace its predecessors. It absorbs them.
Bottom-up project demand doesn't disappear — it gets properly governed, evaluated against both strategic priorities and the architectural blueprint. Top-down strategy derivation and continuous planning remain fully present — now with a second validation layer ensuring the organization has the architectural readiness to deliver. And an entirely new category of investment becomes visible: the initiatives required to close the gap between current and target state architecture — work that was never surfaced before, and was quietly undermining execution from below.
Three sources of demand. Three lenses of evaluation. One integrated planning model.
"Strategic intent without architectural readiness is ambition without foundation."
It Takes a Village
When I ask organizations where they sit on this journey, the most common answer is somewhere between Project Driven and Initiative Driven — with the architecture team quietly working on elements of Enterprise Driven in isolation. That answer perfectly illustrates the core problem. Partial progress across disconnected functions is not a planning operating model.
Mastering Strategy Execution demands a unified operating model — Strategic Portfolio Management, Business and Enterprise Architecture, Financial Planning and Analysis, Project and Program Execution, and Change Management working in concert, not in isolation. At StrategyXF we call this building the village. It requires C-Suite sponsorship, intentional integration, and the organizational will to treat Strategy Execution as the enterprise-wide discipline it truly is.
Ready to Go Deeper?
This page is the overview. The full article explores each of the three planning approaches in detail — the mechanics, the failure modes, the research behind the numbers, the operating model imperatives, and the practical path from where you are to where you need to be.
Read the Guide: From Projects to Performance: The Planning Evolution that Drives Strategy Execution
Not a member? Apply to become a member
The Strategy eXecution Forum (StrategyXF) is an invite-only, no-fee professional community built by and for practitioners who understand the challenges of closing the persistent gap between strategy and results. We believe it requires a collective effort to master strategy execution. StrategyXF brings together senior leaders from across the enterprise: C-suite executives, Strategy & Operations leaders, Transformation Offices, Finance, HR, IT, PMO, Enterprise Risk, Change Management, Portfolio Management, Business Architecture, and more.
Together, we collaborate on real-world challenges, share proven approaches, and shape the future of disciplined and impactful organizational execution. This is not a passive network; it is a practitioner-led community where your experience adds real value. Every discussion is designed to deliver practical ideas you can apply immediately. If you are serious about elevating strategy execution as a mission-critical discipline, we invite you to apply to become a member and help us build something the profession has long needed.
