Ideas into Impact, Ep. 01: Strategy that ships

The first episode of the series takes a question that most people working in institutions in this region have lived through: why does so much approved strategy never happen? The episode's argument is that the failure is almost never in the analysis. It is at the seam where a strategy meets a budget cycle, a procurement process, and a staffing table that were designed before the strategy existed and are not going to be redesigned because of it.

What the episode discusses

The conversation works through the practical mechanics of that seam. A strategy that assumes spending in the first quarter of a financial year, in a system where procurement takes two, has already failed on paper. A strategy that requires a capability nobody in the institution holds has made a hiring decision without saying so. A strategy with fifteen priorities has made no decision at all, since the institution will simply do the ones that were already underway.

It also covers the political economy of the seam, which is usually left out of these conversations. A strategy reallocates attention and budget, and the people who lose out by it are generally still in post when delivery begins. A plan that has not accounted for them has not accounted for the main reason plans stall. The episode looks at what it means to negotiate a strategy through an institution rather than to announce it, and why the version that emerges from that process, though less elegant, is usually the one that gets done.

The argument

The case put in the episode is that strategy should be written against the delivery constraints from the outset rather than translated into them afterwards. That means costing a plan in the institution's own budget lines rather than in abstract totals, sequencing it against the procurement calendar that actually applies, naming the person accountable for each commitment, and cutting the plan down to the number of things the institution can genuinely run in parallel.

It also means treating the implementation plan as part of the strategy rather than as a follow-on document produced by someone else later. In our experience the separation between the two is where most of the loss occurs: the people who wrote the strategy understood the trade-offs, and the people who inherit it receive only the conclusions. A commitment arrives at the desk of the person who has to execute it stripped of the reasoning that made it sensible, and when conditions change, as they do, that person has nothing to reason from.

The episode closes on what it would mean to hold a strategy to this standard in practice: a quarterly review that asks what has actually moved rather than what has been reported, a willingness to drop commitments openly instead of carrying them forward unfunded, and an acceptance that a plan with four things in it that happen is worth more than one with twenty that are described.

Who it is for

The episode is aimed at people responsible for making a plan happen: senior officials in ministries and agencies, programme directors, and executives in companies that have just completed a planning exercise and are wondering why the organisation has not visibly changed. It will also be useful to advisers who write strategies for others, since a share of the responsibility for undeliverable plans sits with us.

Status

The Veynuus podcast is in production. No episode has been released, and the description above sets out the intended content of the first episode rather than a summary of a recorded conversation. To be notified when the series launches, or to propose a guest or a subject, write to [email protected].