Write the Ten-Year Strategy as Ten Fundable Chapters

A ten-year transformation strategy rarely fails because the ambition was wrong. It fails because the ambition was written on one clock and funded on another. The strategy runs on a decade. The money runs on a year. The audit runs on a year. The sponsor runs until the next reorganisation.

The mismatch nobody plans for

Most long-horizon national plans are written as a single document with a single end state, then handed to an organisation that has to justify spend every twelve months. Year one is usually fine, because the document is new and the sponsor signed it. Year three is where the trouble starts. A new decision maker asks a reasonable question: what did last year's budget actually deliver? If the answer is "we are on track to a 2034 target", the plan has already lost.

The fix is structural, not motivational. Write the decade as a series of annual chapters that can each be funded, reported and defended on their own, while all pointing in the same direction. The direction is the strategy. The chapter is the funding unit.

Three tests for a fundable chapter

Defensible scope

Each year needs a funded scope, a measurable outcome and a named owner. If a commitment cannot be described in one paragraph and pinned to one accountable person, it is not a chapter, it is an aspiration waiting for someone else's budget. In my view, this is where most transformation roadmaps quietly fail: not a data problem, not an AI problem, an ownership problem.

Benchmarks that do not move

Guidance on building national digital strategies is blunt about this: objectives need to be measurable so that progress can be assessed continuously against the same benchmarks for the whole life of the strategy, and resourcing should be estimated against what is actually available rather than assumed (digitalregulation.org). Fixed benchmarks are what make year seven comparable to year two. Changing the measures every time leadership changes is how a decade of work becomes unprovable.

Resourcing checked against reality

A chapter that assumes capacity nobody has is a chapter that fails an audit twice: once for the delivery gap, once for the planning quality. Honest capacity numbers make the annual conversation about sequencing rather than credibility.

What other governments actually do

Australia offers the clearest published version of the nested model. Its Data and Digital Government Strategy runs to 2030, and inside it sits a published 2025 Implementation Plan that is explicitly the annual mechanism operationalising the longer strategy (finance.gov.au). The long document sets direction. The annual plan is what people are held to.

The UK's blueprint for modern digital government makes a related funding argument. It says government should move:

from funding one-off digital projects to funding persistent product teams, and from long discovery projects to delivering value early.

That sits in the published blueprint (a blueprint for modern digital government). It matters for chapter writing, because a persistent team funded annually can carry a ten-year direction across sponsors. A project funded once cannot.

The UK also ran Transforming for a Digital Future from 2022 to 2025, a three-year roadmap nested inside longer digital ambitions rather than one unbroken ten-year funding line (summary of government digital transformation programmes). Ireland has taken a different route, updating its National Digital Strategy through ongoing stakeholder consultation rather than issuing one fixed long-term document (Open Access Government). Nested annual plan, short funded cycle, continuous consultation: three shapes, one instinct. Nobody credible is betting a decade on a document that never reopens.

A view from national-scale government delivery

This is not a theoretical preference for me. Inside a UAE federal government entity, a 10-year national digital transformation strategy was co-developed, in an environment where 130+ services were automated and 20+ services moved onto smart apps over the course of the wider modernisation effort. Sovereign and on-premises constraints were real, not preferences. Audits were real: internal, external and programme level.

What that environment teaches is simple. The strategy documents people remember are the ones that could be read as commitments this year. Anything defensible only as a 2030 story eventually gets re-scoped by someone who was not in the room when it was written, and there is nothing dishonest about that. They are doing their job with the evidence available to them. The job of the strategy author is to leave better evidence behind.

The objections worth taking seriously

Annual chapters can dilute the ambition

This is the strongest objection. Break a decade into twelve-month funding units and you can end up with a series of disconnected short projects and no coherent end state. The guard is to keep the end state written down, visible in every chapter, and re-tested at least annually against the fixed benchmarks. Chapters are funding units. They are not permission to renegotiate the destination every budget season.

The real risk is leadership turnover, not budget

Partly true. A governance analysis of national digital transformation is framed exactly around sponsor and political turnover, under the title "Governance of National Digital Transformation: Cultivating Resilience Amidst Changing Political Environments" (Network Readiness Index). No funding structure saves a strategy that loses its executive sponsor outright. But annual chapters change what a new sponsor inherits. Inheriting audited outcomes and a funded next chapter is a very different proposition from inheriting a slide deck promising results in year eight.

There is no proven template

Correct, and worth saying plainly. Australia, the UK and Ireland each use a different structure, and none of the published sources sets out a single validated model for nesting a decade inside annual budgets. What they share is the pattern, not the template. Treat the chapter model as a design principle to adapt to your own budget and audit calendar, not a blueprint to copy.

Where this leaves digital transformation leads

If you are writing or inheriting a long-horizon strategy, the most useful test is a small one. Take any single year of the plan and ask whether it could stand alone in a budget committee: funded scope, named owner, measurable outcome against benchmarks that will not move, resourcing checked against real capacity. If the year cannot stand alone, the decade will not either.

The direction should be ambitious enough to need ten years. The commitments should be concrete enough to survive one.

When your current strategy reaches its next budget cycle, will it be read as a promise or as a chapter that can be funded on its own?