From Strategy Document to Delivery System

01

The document is not the strategy

Many strategy processes culminate in a polished narrative and a long list of initiatives. The organization may understand the ambition yet remain uncertain about the few choices that should govern trade-offs. When everything is strategic, the operating model has no basis for saying no.

The first shift is to express strategy as a set of choices: where the institution will focus, what it will do differently, which capabilities matter most, and what it will deprioritize. These choices create the logic for execution.

02

Build a portfolio, not a catalogue

Initiatives should form a connected portfolio with a visible contribution to strategic outcomes. That means testing duplication, dependencies, capacity demands, and the combined burden of change on the institution.

A disciplined portfolio is usually smaller than the original catalogue. Each initiative has a defined outcome, accountable owner, meaningful milestones, and an explicit relationship to other work.

• Outcome before activity
• Sequencing before simultaneous launch
• Dependencies before isolated plans
• Capacity before aspiration

03

Govern the decisions that move delivery

Transformation governance often becomes a forum for status updates. A delivery system instead organizes the conversations around decisions: what is off track, why it matters, what support is needed, and who can resolve the barrier.

The cadence should distinguish operational problem-solving from executive intervention. Teams need room to manage; leaders need a concise view of the choices only they can make.

04

Treat capability as part of the outcome

External support can add pace and structure, but the institution must own the strategy. Initiative design, review routines, and portfolio tools should be built with internal teams and progressively transferred.

The real test is whether the organization can continue making good trade-offs after the initial transformation program has ended.