Earlier this month, we were back in Denver with a client we’ve worked with for some time now. We’d already got their OKRs aligned and outcome-focused. We’d already run the squad kick-off. But OKRs on a page are only as good as the strategy execution system underneath them — the rhythms, the roles, the decisions, the discipline. So we went back for a week to do the harder, less glamorous work: defining what great execution actually looks like, in their context, in their language, with their PMO in the room.
The week had three parts. We joined the quarterly executive OKR check-in, where the senior team interrogated progress against the company’s strategic bets. We then ran a two-day PMO workshop for the team that holds the engine room of strategy execution — portfolio managers, programme managers, business leads, BL delegates, digital product managers. And weaving through it all, an extended conversation on AI transformation and what an ambitious-but-grounded path looks like for them over the next twelve months.
This post is what we took away. The eight execution principles the team committed to, a deeper look at the three that we see show up most often across the clients we work with, and an exercise you can steal and run with your own team next week.
(And a small bit of cosmic irony — on the way home, Heathrow gave me a very practical lesson in what happens when execution breaks down. The baggage system failed mid-transfer in Terminal 5. I made it home to Manchester. My suitcase did not. I’d spent the week helping a leadership team tighten their delivery rhythms, only to land back in the UK without a toothbrush. The universe enjoys a metaphor.)
What we actually mean by “strategy execution”
Before we get into the principles, a definition — because this term gets thrown around with a lot of looseness.
Strategy execution is the discipline of turning a chosen direction into reality. It assumes the strategy is set. The work is to translate that strategy into the objectives, behaviours, decisions, cadences and outcomes that move the organisation in the chosen direction — quickly, repeatedly, across functions, and without losing the thread under pressure. It is a discipline of delivery. Cadences, governance, capability, OKRs, the works.
OKRs are part of strategy execution. They are not the whole of it. OKRs are the instrument. The system around them — the PMO, the operating rhythms, the decision rights, the AI — is what turns that instrument into music. We wrote more about strategy execution as an emerging discipline after the OKR Mentors gathering in Barcelona this month, and the Denver workshop was a live test of the same ideas with one client.
The eight strategy execution principles the team committed to
The output the PMO landed on by the end of day two was a set of eight principles that would shape how the team executes against the company’s strategic bets for the rest of the year. Not posters. Not values theatre. A set of working rules they would test their behaviour against in every weekly check-in, every steering committee, every decision review.
Here they are. The three marked with a red border are the ones we’ll go deeper on — because they are the ones we see come up across almost every strategy execution engagement we run.
Eight is intentional. Fewer than five, and you lose nuance. More than ten, and nobody can hold them in their head when the pressure’s on. Eight is the number that fits on a single slide and on a single human’s mental model in a hot meeting.
Principle 01 — Flow to outcomes
Measure progress by what you deliver, not how busy you are. Every initiative ties to a measurable outcome.
This is the principle that almost every leadership team agrees with intellectually and almost every PMO violates in practice. The default rhythm of most organisations — status reports, RAG ratings, milestone trackers — is built around activity. We held 14 workshops. We shipped 27 epics. We closed 412 tickets. That tells you the team is moving. It tells you almost nothing about whether the strategy is.
The fix is not to abolish activity tracking. The fix is to demote it. The lead measure in every status review should be the movement in the outcome — the OKR, the customer metric, the financial signal — and the activity should be presented underneath as evidence, not as the headline. The conversation in the room changes the moment you do that. The first question stops being “are we on plan?” and starts being “is the plan working?”.
Principle 02 — Short loops, real learning
Prefer short iterations with frequent check-ins over big-bang delivery. Learn and adapt continuously.
This is the principle borrowed straight from agile and translated into strategy execution. The bet here is that the cost of being wrong is small if you find out fast, and catastrophic if you find out late. Most strategic failures are not failures of intent — they are failures of tempo. The strategy stopped working three months ago and nobody noticed because the next check-in was at the half-year review.
In practice, this means three things in a PMO. Shorten the planning unit — quarterly OKRs reviewed weekly, not annual plans reviewed quarterly. Decouple delivery from review — the team delivering should not be the only voice telling leadership how delivery is going. And build in cheap experiments — if you’re about to bet a year and a million dollars on a single approach, find a way to spend a fortnight and ten thousand testing the riskiest assumption first.
The trap to avoid is mistaking more meetings for faster feedback. The Denver team had no shortage of meetings. They had a shortage of meetings that ended with a clear, written, time-bound decision. Fast feedback only works if the loop closes.
Principle 03 — Push decisions to the edge
Push decisions to the people closest to the work. Escalate only what genuinely needs senior input.
This is the principle the room argued about most — and the one most directly connected to the work the PMO is there to do. Every conversation we had about role clarity, about sponsor engagement, about portfolio governance, eventually came back to the same question: who actually decides this?
The pattern we see, in Denver and elsewhere, is decision drift — small decisions floating upward because nobody at the working level wants to own them, large decisions floating downward because senior leaders are too busy to engage. Both directions hurt execution. The fix is a deliberate, written set of decision rights, mapped against the actual roles in the organisation. Sponsors. Portfolio managers. Business leads. Programme managers. Product managers. Every contested scenario tested against the question: who is accountable, who is consulted, who is informed, and crucially, who is doing the deciding?
We ran a “who decides?” rapid-fire exercise in the workshop — twelve scenarios pulled from the team’s actual portfolio. The room agreed on the answer in fewer than half of them on first pass. That gap — the gap between “we know how we work” and “we actually agree on how we work” — is one of the most common, and most fixable, drags on strategy execution we encounter.
The deeper truth: knowing is not doing
Every leadership team I’ve ever sat with reads these three principles and nods. Of course flow to outcomes. Of course short loops and real learning. Of course push decisions to the edge. We know this.
But here’s the uncomfortable bit. Understanding what good execution looks like, and actually building an organisation in which it consistently happens, are completely different problems. It’s the “backwards bicycle” effect — the engineer who built a bike whose handlebars steer the opposite way, then took six months of daily practice to learn to ride it, despite knowing exactly how it worked from day one. Knowledge does not equal capability. Capability does not equal system.
This is the framing we keep coming back to with clients. Strategy execution is a dual operating system. There is the capability layer — the trained champions, the coached leaders, the people who can hold the practice in the room. And there is the system layer — the cadences, the tooling, the dashboards, the governance. You need both, and treating them as a choice is one of the reasons so many programmes stall.
You can build a beautiful capability layer and watch it atrophy the moment your trained people get pulled onto something else. You can install a slick system and watch it become a beautifully instrumented theatre of activity that doesn’t change a single decision. The two have to be designed to reinforce each other. The capability makes the system human. The system makes the capability stick.
The PMO is, in our view, the natural owner of that dual operating system. Which is why the work in Denver mattered — the principles only become real when the people who run the operating system can name them, defend them, and apply them under pressure.
The AI thread — transformation as BAU
One of the recurring threads through both days was AI — and specifically, what an honest, ambitious-but-credible AI transformation looks like for a PMO whose day job is strategy execution.
The framing we used: AI is changing the rhythm of strategy execution. Strategy cycles are compressing. Transformation has stopped being a discrete programme with a start and end date and become continuous — transformation is now BAU. Without help, the human bandwidth simply isn’t there to run the operating model and the transformation in parallel. AI, used well, gives that bandwidth back.
The most useful conversations we had in Denver were not about “what AI tools should we buy?” They were about three quieter, harder questions:
- Where is the routine work we can credibly automate? Status synthesis, blocker detection across initiatives, OKR progress reporting against the underlying systems of work. The places where the team is generating slides instead of acting on signal.
- Where is the complex work we can credibly accelerate? Strategy drafting, scenario modelling, retrospective analysis. The places where AI sharpens the conversation, not replaces it.
- Where is the human judgement we should protect? The hardest one. The places where speed is the wrong objective and depth is the right one.
The principle the team landed on — AI as Co-Pilot — deliberately puts the human at the centre. Augment, accelerate, amplify. We’re building this into the engagement with a roadmap of pilots tied to the practical pains of the PMO, not a generic “AI strategy” deck. We wrote a longer view on what good looks like in AI agents for OKR execution and our OKR Execution Engine for anyone interested in the deeper architecture.
What the PMO walked out with
By the end of day two, the PMO had moved from a set of frustrations posted on sticky notes to a working artefact set. The shape of what they left with:
- A shared mission statement the whole team endorsed — partnering with stakeholders to deliver organisational transformation, connecting strategy to execution, governed by a consistent risk and accountability framework.
- A strategy canvas with prioritised focus areas — role clarity and governance, sponsor engagement, AI enablement, leadership buy-in, and effective communication with autonomy.
- A decision rights matrix for the contested scenarios — written, debated, and owned.
- A 90-day action plan — quick wins in weeks one and two, embedding the practices through weeks three and four, measuring outcomes against targets in months two and three.
- A personal commitment from every team member — specific, observable, time-bound, and paired with a named accountability partner.
That last one matters more than people often realise. Strategy execution is a team sport, but the change happens at the level of the individual habits people commit to in front of their peers. We finished the workshop in a circle, with everyone reading their commitment aloud. It is a small ritual that does a lot of quiet work.
An exercise you can run with your team
If you want to test the strategy execution gap in your own team, here’s the exercise we run as a warm-up. It takes about an hour. Run it at your next leadership offsite, your next PMO stand-up, or in the back half of a quarterly review when energy is still up.
The strategy execution gap exercise
Pick one of these three principles: flow to outcomes, short loops with real learning, or push decisions to the edge. Then work through these four steps as a team.
- Get specific about what it means in your world. Not the dictionary definition — what would you actually see? A real meeting, a real decision, a real conversation. Write down three concrete examples.
- Decide how you’d know it’s happening. What would you measure to spot it, week to week? The measure has to be observable without a special report. If it needs a special report, it’s the wrong measure.
- Ask the honest question. Are we actually doing this consistently right now? Or is it patchwork across the org — great in some pockets, absent in others? Be specific about where.
- Name the gap. The space between what you want and what’s actually happening — that’s your strategy execution problem. Write it down, in one sentence, on a single piece of paper.
The output is one sentence. That sentence is the most useful thing you’ll write all quarter.
Where we go from here
Denver was foundation work. The principles are agreed. The mission, canvas, decision rights and 90-day plan are on the wall. The real engagement — the coaching of initiative teams, the embedding of the practices, the AI pilots that earn their place — starts now.
This is the work we do. We partner with leadership teams whose strategy is set and whose challenge is execution. We don’t sell decks. We don’t sell frameworks. We sell the discipline of turning intent into outcomes — built with you, owned by your people, sustained after we’re gone.
If anything here resonates — whether you’re wrestling with a PMO that’s drowning in status reporting, a leadership team that can’t agree who decides, an AI transformation that doesn’t know where to start, or an OKR programme that’s drifting from the strategy that spawned it — we’d love to talk.
A good place to start is our free Strategy Execution Assessment. It takes about ten minutes and gives you an honest read on where you stand, with no follow-up commitment. Or book a free consultation if you’d rather talk it through.
Strategy execution is a practice. The teams that get it right don’t do anything magical — they just hold themselves, week after week, to principles like the ones we worked through in Denver. That’s the work. That’s where the leverage is.
