The execution management system

You would not let a delivery team work without coordination. Yet that is close to how most organisations execute strategy: each function running its own portfolio of change, each one confident it is doing the right thing, and no shared view of how it all fits together.

An integrated execution view is not a dashboard. It is a mandate. It can sit with a role, a small team, or a collective of leaders, but someone has to be accountable for seeing across silos, connecting the strategy to the daily work, and keeping the organisation moving as one.

The purpose is not control. Control is what organisations reach for when they cannot see. The purpose is connection and orchestration: knowing what is in flight, what depends on what, where capacity is genuinely constrained, and what should stop so something more valuable can start.

The test is simple. Name the person or forum that holds the all-of-organisation view of execution right now. If you cannot, the view does not exist, and every prioritisation conversation you have is being made on partial information.

Portfolio management disciplines, including the frameworks published by PMI and Axelos, give organisations oversight of projects and programmes aligned to strategy. Execution management extends the scope: not just projects and programmes, but all the work that executes the strategy.

Most organisations do not have a goal system. They have a collection of disconnected measures that were set in a planning cycle and reviewed when someone asked for a report.

A working goal system does three things. Every team can see how their work contributes to enterprise outcomes. Resources and decisions stay focused on what creates value. Progress is visible, shared and open to adjustment.

The design flaw I see most often is that goals follow the org chart rather than the value chain. Goals get cascaded down reporting lines and performance is assessed individually, but real execution flows across functions. When goals do not reflect that, you get misaligned effort, clunky handovers and gaps in accountability that nobody owns.

The second flaw is measurement that only looks backwards. Results, revenue and output volumes are lagging indicators, and managing by them alone is managing the past. Balanced systems pair every lag measure with a leading indicator that predicts it: percentage of milestones tracking to plan, decision lead time, adoption rates. Together they show trajectory, not just destination.

And culture decides how goals are interpreted, whatever the strategy says. In harmony-driven cultures, stretch goals get quietly softened to protect relationships. In competitive ones, goals fracture into silos. If you do not calibrate for culture, you will set goals nobody is willing to challenge, or goals everyone competes to deliver in isolation.

Cameron and Quinn’s competing values framework is useful here. It maps the cultural orientations that shape how organisations behave, and it explains why the same goal-setting method produces very different behaviour in a collaborative culture than it does in a competitive one.

Your goal system sets the outcomes you are aiming for. Benefits management proves whether the work actually created them. You need both, working together.

The pattern that costs organisations the most is retrofitting. Scope gets defined, the business case gets written, and then benefits get reverse-engineered to justify the work. You want the opposite sequence: strategic outcomes shape the benefits, benefits shape the scope, and benefits inform the phasing and sequencing of delivery.

Ownership is where it usually falls over. Not joint ownership, not the programme team, not “the business”. One named benefit owner, with cross-functional enablers around them, because value rarely lives entirely inside one function.

And benefits do not land at go-live. A system that works differentiates between immediate benefits in the first three months, near-term benefits over three to twelve months, and long-term benefits beyond a year. That clarity is what lets leaders set realistic expectations and hold investment discipline through the quiet period after delivery.

John Ward and Elizabeth Daniel’s work on benefits management makes the same argument from a different direction: benefits do not arrive as a by-product of delivery. They have to be specified, owned and actively managed as a discipline in their own right, before, during and long after the technology or the project lands.

Flow is how information, decisions, priorities and feedback move through an organisation. It is the rhythm that keeps work alive, and it is the single biggest determinant of execution pace that almost nobody manages deliberately.

When pace dips, the instinct is to add structure. More reporting, more checkpoints, more forums. It feels like control. What it actually does is slow the movement of information and decisions, which is the thing that was already the constraint.

Most delays are not caused by bad decisions. They are caused by decisions travelling too far up the organisation. Unclear ownership creates hesitation, too many approvals stall movement, and execution lifts the moment decision rights are explicit and trusted locally.

The same is true between teams. Most delay happens in the gaps, not inside them: misaligned priorities, unclear handovers, different definitions of done. Flow improves when teams share a common view of value and agree where work starts and finishes.

And you cannot execute a bold strategy on slow organisational rhythms. Annual planning cycles and lagging reporting break flow before the work even starts. Cadence has to match ambition.

Sull, Homkes and Sull’s research in Harvard Business Review found the fault line in execution sits horizontally rather than vertically. Commitments up and down the line hold. Commitments across functions are the ones that quietly fail, and organisations rarely have a mechanism for repairing them.

What is moving faster in your organisation: the pace of change, or the pace of learning?

The pattern I keep seeing is leadership teams investing in delivery capability, uplifting governance frameworks and tightening processes, and execution performance still not moving to where they want it. When I interviewed senior executives for my research, everyone described similar success factors. The ones actually seeing results had prioritised something the others had not. They invested in systems that helped them learn fast enough to keep up.

By learning architecture I do not mean training programmes or workshops. I mean the everyday mechanisms that help teams reflect, challenge their assumptions, test hypotheses and adjust in light of reality. The retros. The insight sharing. The small experiments. The space for truth telling.

The high performers treated learning as a performance system rather than an HR initiative. They designed learning loops into how they planned, led, governed and delivered. Learning was structured, continuous, fast and embedded, not left to chance, and the impact showed up everywhere: sharper decisions, less rework, earlier corrections, stronger strategic integrity.

This connects directly back to Lever 1. You cannot build this without leaders who create space for curiosity, honesty and shared insight. People only tell the truth when the truth is welcomed.

So the question is whether your organisation has a deliberate architecture that converts experience into performance, or whether learning is something you hope happens. If you cannot answer with a confident yes, that is probably where execution is starting to slip.

Steven Bartlett argues for rewarding failure precisely because it accelerates learning. Most organisations do not have that cultural muscle, and without it, execution quietly slows.