The missing discipline in Strategy Execution

Outcome Management Series – 5 of 5
Executive Summary
Project Delivery isn’t the issue — Strategic Drift is
As the Head of Strategy Execution your mandate is explicit: translate strategy into initiatives that can be funded and executed with confidence. You’re expected to give executives and the board a credible strategy → portfolio → outcomes story, not a catalogue of “busy”.
You’re usually drowning in it: decks, pillars, themes, target states, roadmaps, initiatives, dependencies, governance rhythms, status packs. The problem isn’t the absence of intent. It’s that intent doesn’t stay intact long enough to organise cohesive action.
As the pattern persists, strategies that look coherent and cohesive at the top tend to drift as they cascade down. Activity continues to pick up pace, intent erodes, ambiguity spreads, and the portfolio keeps moving without a stable definition of success.
This is how Strategic Drift takes hold.
Projects still run. Meetings occur. Work still gets delivered. Yet you always end up asking yourself the most familiar question in your role: Are we actually executing the strategy, or just running projects? Somewhere between “strategy” and “delivery” meaning decays.
Outcome Management is the missing discipline that answers that question. Not because it adds another layer of artefacts — but because it changes how leaders behave when strategy meets complexity.
The GPS analogy: direction without a destination
Imagine navigating with GPS, but without a real destination.
You don’t enter an exact address. You enter something like a suburb name, a landmark, a vague intent. The system still gives you an ETA. You still start moving. Progress feels real because motion is real.
Then you arrive… in the neighbouring suburb.
Close enough that people can claim success. Far enough that the purpose wasn’t achieved. And because the destination was never precise, you can’t prove misalignment — you can only debate it.
That’s what strategy execution looks like when intent isn’t made explicit and durable
For a Strategy/Transformation Director, this becomes your daily bind. You’re accountable for outcomes, sitting between executive intent and delivery reality — absorbing the cost of ambiguity that no artefact can fully resolve once work is underway.
Now imagine the same journey — but this time you have the exact address.
The roads are still complex. Traffic still changes. You might still miss a turn. But the system becomes fundamentally more useful because the destination is unambiguous.
Like a GPS, it course-corrects without drama. If congestion builds, it reroutes. If you drift, it steers you back. If you change vehicles — car to train to walking — it recalculates the route while preserving the destination.
It shows trade-offs clearly: fastest versus simplest, tolls versus distance. And it gives everyone a shared reference point so multiple drivers can take different routes and still converge.

That is what Outcome Management enables in strategy execution.
It doesn’t simplify complexity. It makes complexity navigable.
With intent held steady and explicit, the portfolio can adapt method without losing coherence. You can detect drift early rather than discovering it in the rear-view mirror. You can make trade-offs deliberately rather than accidentally. And you can tell a credible story to the CEO and Board: not “we ran projects,” but “we pursued these outcomes, learned, and course-corrected as reality changed.”
Outcome Management is the leadership discipline that makes the destination real — and keeps the organisation oriented to it as conditions evolve.
The Strategy Director’s job sits in a leadership chasm
A Strategy Director sits in the middle of smart people and strong opinions. On paper, their job is to set initiatives up so they’re investment-ready before delivery starts. Not because delivery lacks capability—but because if ambiguity survives mobilisation, delivery will pay for it for the next 12–24 months in rework, conflict, and late surprises.
So, the Strategy Director does what good Strategy Directors do: convenes stakeholders, pushes for definitions, tries to land the “what” and “why” before anyone commits to the “how”. Outcomes, benefits, dependencies, trade-offs—made explicit.
But the unspoken problem is structural: there is no shared method for eliminating ambiguity. No common language for what must be locked down, by when, and by whom. No reliable mechanism for turning “things people said” into “things the organisation has actually decided”. Meetings create motion, not resolution. People nod, then leave with different interpretations that harden into parallel realities.
Then time does what it does: it erodes truth. Agreements dissolve into selective memory. Artefacts exist, but they are not authoritative. The Strategy Director ends up trying to govern an invisible contract.
And eventually the vacuum gets filled. A Sponsor reaches the point where ambiguity feels intolerable and says, effectively: “Enough. Let’s just get on with it.” Not recklessness—organisational gravity. Progress is rewarded; pause is punished. The decks turn green. The machinery spins.
Months later the costs arrive: mismatched expectations, re-litigation of decisions that were never truly decided, and delivery blamed for underperformance—despite never being set up for success.
That is the strategy execution leadership gap.
Outcome Management exists to close it.
The five Outcome Management leadership disciplines
If Outcome Management is a leadership capability, what do leaders have to do differently?
Not in theory. In practice — in the moments where strategy either stays intact or fractures.
5.1 Eliminate Ambiguity in Sequence
Strategy execution rarely fails in delivery — it fails in the order leaders seek clarity.
When under pressure to move, organisations converge early on solution and delivery: plans are set, teams mobilised, timelines committed. It feels like progress, but it locks in motion before intent is clear. When the Problem and Outcome remain unresolved, execution becomes precise but misdirected — and drift is inevitable.
Leaders need to enforce a different sequence: problem and outcome first.
Before anything, first disambiguate what we are solving and what success looks like; only then define how to achieve it. Speed follows clarity — not the other way around.
5.2 Hold Intent Under Pressure
Outcome Management requires leaders to hold intent steady as circumstances evolve.
In complex environments, there is a persistent pull toward premature convergence — moving quickly to solutions, locking in methods, or treating early hypotheses as commitments. Outcome Management requires leaders to resist this impulse long enough for intent to be clearly articulated, shared, and understood.
This does not imply indecision. It reflects an understanding that clarity of purpose is the foundation for effective action, particularly when conditions are fluid. This balance — openness to emergence paired with firmness of intent — is a defining leadership capability in outcome-oriented systems.
3) Maintain Conversational Discipline
Outcome Management elevates conversation from communication to coordination.
In many organisations, “alignment” is attempted through artefacts: decks, documents, RAG reports, briefing packs. These help, but they don’t create shared meaning. Shared meaning is created conversationally — through how leaders:
– clarify language
– surface assumptions
– test interpretations
– resolve conflicting definitions
– make decisions explicit and repeatable
Without this discipline, ambiguity is driven underground. And then it re-emerges later as misalignment, rework, or conflict — usually at the worst possible time.
For Strategy Directors, this is one of the highest-leverage shifts available: making leadership conversation the primary mechanism of alignment, rather than treating it as commentary on delivery.
4) Hold Authority over Outcomes, not Solutions
Outcome Management separates authority over outcomes from ownership of solutions.
Leaders define and steward the “what.” They do not monopolise the “how.”
This matters because the Strategy Director’s portfolio is rarely executable through central control. Delivery is distributed — across BUs, PMOs, vendors, product lines, operational teams. If leaders insist on owning the method, the system becomes brittle. It slows down. It optimises locally. It escalates constantly.
Authority anchored in outcomes legitimises decentralised decision-making while preserving coherence. You get adaptive execution without strategic drift. In GPS terms: you don’t need everyone to take the same streets. You need everyone to arrive at the same destination — and to be able to explain how their chosen route still serves the intent.
5) Preserve Coherence as Outcomes Cascade
Portfolio execution is not a single decision. It is a chain of translations.
– Strategy becomes strategic outcomes.
– Outcomes become initiative intent.
– Initiative intent becomes work packages.
– Work packages become delivery choices.
At every translation point, meaning can be lost.
Outcome Management places leaders in the role of stewards of coherence at each cascaded level.
Not specifying actions. Not enforcing uniformity.
Stewarding the logic:
– outcomes remain logically connected across levels
– intent is preserved as it cascades
– meaning is not lost across organisational boundaries
As organisational complexity increases, this stewardship role becomes central.
Without it, the organisation becomes a set of busy projects with no coherent strategic vector.
What changes for Strategy & Transformation Directors?
If you adopt Outcome Management as a leadership discipline — not a technical overlay — a different set of things becomes possible in your role.
You get portfolio visibility that isn’t cosmetic
Instead of initiatives “claiming alignment,” you can see and test linkage:
- Which initiatives actually support which strategic outcomes?
- Where are we over-invested or under-invested relative to intent?
- Which work is busy but strategically irrelevant?
- What outcomes can we credibly claim this year — and why?
This is visibility rooted in meaning, not reporting.
You get decision forums that talk about the right thing
Many governance forums default to project health: delivery milestones, spend, risk logs, status colours. Outcome Management shifts the centre of gravity.
The critical questions become:
- Are we still pursuing the intended outcome, or have we drifted?
- What have we learned about whether our approach is working?
- Where do we need to course-correct to preserve intent?
- What trade-offs are we making — and are they consistent with strategy?
That is governance that can actually steer.
You get a board-safe narrative that doesn’t rely on optimism
The aspiration in your role is not more data. It’s a story you can stand behind:
Here’s the strategy. Here’s the portfolio. Here’s what we’re achieving.
Outcome Management makes that narrative credible because you can speak with evidence about outcomes — not just activity. And you can explain course-corrections as discipline, not as failure.
In Summary:
Keep the destination stable. Let the route adapt.
In complex environments, the task is not to simplify complexity. It is to make complexity navigable.
GPS works because it combines two things:
- a clear destination
- continuous course-correction as conditions change
Outcome Management is the organisational equivalent.
Without it, strategy execution is a convoy of well-intentioned drivers heading “roughly north,” each confident they’re on track — until you compare arrival points and realise you’re spread across neighbouring suburbs.
With it, leaders hold the destination steady, tolerate uncertainty in the route, and course-correct deliberately — so the organisation can adapt without losing coherence.
