The Delivery Readiness Review

Where the strategy stopped

The structural reading. Authorship, budget and ownership, traced backwards from the outcomes the strategy promised.

The situation

An international organisation had approved a new institutional strategy, and the document itself was sound. So the open question was whether the organisation could actually deliver what it had signed off.

Like many organisations of its kind, its planning system had been built for donors rather than for delivery, which meant that annual workplans recorded activities and results frameworks reported upward.

Both did exactly what they had been designed to do, but they could not fix the gap senior management identified: everyone held a workplan full of activities, but at the end of the year it was not clear who was accountable or responsible for which specific result.

What was really going on

The first process I reviewed was the performance appraisal system, because that is what tells you what staff are actually rewarded for, and people will prioritise whatever their career depends on.

From there I started with the outcomes the strategy had promised to the stakeholders it serves, and worked backwards through the medium-term outcomes and the outputs that would have to exist to produce them. Once I mapped all of that against the workplans of key staff, they did not fully meet. The activities people had committed to on paper would not produce the outputs the strategy needed.

There were three reasons for it, none of them anybody's failing: job descriptions were not revised after the strategy was approved, workplans were built from current projects rather than from the new direction, and where the two happened to overlap that was coincidence rather than design.

Underneath all of this sat a common funding structure: staff charged their time to projects and the strategy had no charge code of its own, meaning when it came to prioritising, projects won every time.

The same pattern showed up in ownership, where each strategic pillar had a named leader but nobody one layer down was accountable for the components, and the teams themselves had no clear view of what they were supposed to produce.

None of these three would have stopped the strategy on its own, but together they left the delivering teams without an incentive to act on it or a clear idea of what acting on it actually meant.

What changed

Planning was then connected across all layers. Corporate priorities drove unit plans and unit plans drove individual objectives, with each level carrying what the level above it actually needed.

The result

Every member of staff covered by the appraisal system ended up with objectives tied to a strategic outcome, and for the first time the organisation held a set of corporate priorities with KPIs that were measured and cascaded down to units and to individuals.

The test came sooner than expected, when the sector's funding environment changed sharply and a corporate target was missed, and what mattered then was that the organisation could see the miss and name its cause, and could tell an external shock apart from a failure of its own delivery.

In a nutshell, more often than not, the strategy isn't the problem. The system it lands in is.

Where the team stopped short

Belief against evidence. What people believed was blocking it, set against what the evidence showed.

The situation

A digital transformation strategy had been approved, and the open question was whether we held the capabilities to deliver it. I commissioned the review myself, in a period when AI is changing how digital work gets delivered, and my own expectation going in was that we did not. The point was not to prove a gap but to establish whether gaps existed and where they sat. That would let us reskill where it mattered and bring in what was missing, while getting assurance on the parts that were already secure.

What was really going on

The capability was largely there, and what the review found instead was something I was not expecting.

We ran a sailboat exercise: the wind that drives you forward, the anchor that holds you back, the rocks that catch you off guard, the island you are trying to reach. Answers were collected from people individually and only then brought together in small groups, which is why the divergence between them survived long enough to be read.

The constraint people named was resources, and the team believed it was too small and too tightly restricted to deliver what the strategy was asking of it. Several of the other constraints named alongside that were real, but real for other parts of the organisation rather than for this team. The organisation's anchors had become the team's anchors, borrowed rather than earned, which meant the team was carrying weight that was not its own to carry.

The evidence said otherwise. The funding available to the team had increased significantly, and it was available for investing in the strategy rather than for keeping day-to-day operations running. The team had grown over the same period and had acquired capabilities it did not hold before, but the belief had not moved with any of it.

A short hackathon run during the work made the point better than the figures did. Members of the team solved problems that had been assumed unsolvable, using tools that had been available to them for a long time, and without drawing on any of the new money. Those items had stayed pending because people expected them to cost effort, time and money that they did not in fact require.

What corrected it was showing people the facts and then letting them prove the rest to themselves. A team told it has more room than it thinks will argue, and a team that has just used that room will not.

What the review produced

The issue was not that the team lacked capability, it was that the team had misread its own constraints and was underusing what it already had. That is a cheaper problem than the one I had expected to find, and a faster one to correct. What had to change was not the budget or the headcount but what the team believed it was free to attempt.

By the end the team had watched its own constraint be tested and give way, and it went back to the strategy holding a different view of what it could take on. The right capabilities matter, but what a team believes is holding it back decides how much of them it will use.

An obstacle borrowed from another part of the organisation is the hardest kind to put down, because nobody in the room can remember picking it up.