The AI Strategy Gap: Why National AI Plans Need Delivery Institutions
National AI plans fail when they lack budgets, owners, delivery institutions, capability-building, and review cycles. Strategy is the easy part. Delivery is where ambition meets the state.
National AI plans fail when they lack budgets, owners, delivery institutions, capability-building, and review cycles. Strategy is the easy part. Delivery is where ambition meets the state.
Article9 min read
National AI Strategy
Delivery
Public Institutions
Implementation
Publication Details
How to read this insight
CentPol Insights are written as public-facing research and strategy pieces: concise enough to read quickly, structured enough to cite, and practical enough to inform institutional decisions.
Format
Insight article
Reading time
9 min read
Primary theme
National AI Strategy
Publisher
CentPol
Suggested citation
CentPol, "The AI Strategy Gap: Why National AI Plans Need Delivery Institutions," CentPol Insights.
Audience
Policy leaders, ministries, development agencies, strategy sprint participants
Evidence Base
References
Selected sources that informed the article and give readers a path into the underlying research conversation.
In the last few years almost every government has acquired an artificial intelligence strategy. Far fewer have acquired the means to deliver one. The documents are often impressive: they describe national ambitions, ethical principles, priority sectors, and headline targets. But a strategy is a statement of intent, not a system of execution. The countries that will benefit from AI are not the ones with the most polished plans. They are the ones that build the institutions, budgets, and feedback loops needed to turn a plan into sustained public value.
This is the AI strategy gap. It is the distance between a published national vision and the everyday machinery — owners, financing, procurement, data, talent, and review cycles — that would make the vision real. The gap is not a drafting problem that better consultants can fix. It is an institutional problem, and it is now the central weakness in most national AI efforts.
CentPol's position is direct. A national AI strategy should be treated less like a manifesto and more like an operating plan for the state. That reframing changes the question leaders should ask. The question is not "What should our AI strategy say?" It is "What delivery system will carry it, and who is accountable when it stalls?"
Strategy is not delivery
Many countries have AI strategies, ethical principles, or high-level digital ambitions. Fewer have the institutions, budgets, procurement systems, data infrastructure, and talent pipelines needed to execute them. The result is a familiar pattern: a launch event, a wave of attention, and then a slow loss of momentum as the work meets the realities of government.
The gap between aspiration and delivery becomes visible in predictable ways. Pilots remain isolated and never connect to core systems. Ministries compete for ownership rather than coordinating. Funding arrives as a one-off announcement instead of a multi-year budget line. Public agencies are asked to govern AI adoption without the technical capability to do so. None of these failures are about the quality of the strategy. They are about the absence of a delivery system behind it.
The OECD has documented how implementation challenges — fragmented mandates, weak data foundations, procurement constraints, and scarce skills — repeatedly prevent governments from using AI strategically, even where the political will exists.2 Boston Consulting Group's work on national AI playbooks makes a parallel argument: value depends on coordinated implementation capacity, not on the ambition of the strategy alone.1
What a delivery institution actually does
Effective AI strategy needs a delivery engine: a capable office or mission structure with the authority to coordinate ministries, mobilize financing, support sector pilots, build talent, and report progress honestly. In CentPol's country work this recurring structure has a consistent shape — a lean delivery unit, not a large new bureaucracy. Across digital-economy frameworks for Kenya, Rwanda, and Uganda, the same answer emerges: a small, credible coordinating institution anchored in an existing leadership structure, with a mandate to solve the coordination failures that slow execution.
A delivery institution is defined by its functions, not its org chart. At minimum it should:
- Hold the national pipeline. Maintain a single, prioritized portfolio of AI initiatives across ministries, with owners, milestones, and dependencies — so the country has one view of what it is actually delivering. - Mobilize and sequence financing. Coordinate blended finance from government, development partners, employers, and private investors, using public money for coordination, inclusion, standards, and shared infrastructure rather than crowding out commercial capital. - Standardize procurement and vendor governance. Build reusable, AI-specific procurement so agencies are not each negotiating data rights, auditability, and exit terms from scratch. - Build capability. Invest in the technical and institutional skills that let agencies specify, deploy, and oversee AI responsibly. - Report progress. Publish a quarterly dashboard reviewed by the coordinating institutions and used for policy correction, donor reporting, and investor confidence.
The most important design principle is restraint. As CentPol's frameworks repeatedly stress, the delivery unit's purpose is not to replace existing agencies but to connect them around a shared pipeline, shared metrics, and a shared delivery discipline. The failure mode to avoid is a slow new bureaucracy that adds a layer of approval without adding capacity.
Five things every delivery system needs
National AI plans fail when they are missing one or more of five concrete ingredients. A strategy can be intellectually excellent and still fail if any of these is absent.
These ingredients reinforce each other. A budget without an owner is spent without accountability. An owner without authority cannot coordinate ministries. Capability without review becomes obsolete. The delivery institution is the structure that holds the other four together.
Connect, don't replace
The hardest part of national AI delivery is coordination. AI cuts across boundaries that governments manage separately: technology sits with one ministry, data protection with another, finance with a third, sector delivery with many more. Left alone, each acts rationally and the whole fails to cohere. Training providers run cohorts, investors speak to multiple agencies, ministries write policy without market feedback, and partners fund projects with incompatible metrics.
This is why CentPol's frameworks consistently propose a coordinating institution rather than a new super-ministry. A delivery unit anchored in the existing leadership structure — and designed to coordinate across ministries, regulators, sub-national governments, utilities, operators, investors, and development partners — can resolve the practical blockers that stall delivery: procurement, standards, data sharing, financing packaging, and performance monitoring. It earns authority by removing friction, not by accumulating control.
CentPol view
A national AI strategy is only as strong as the delivery system behind it. The goal is not a bigger plan or a bigger agency, but a smaller, sharper institution that makes the rest of government able to deliver.
The same logic appears at the regional level. The African Union's Continental AI Strategy is, in effect, a coordination instrument: shared framing and priorities that align national strategies without forcing full legal harmonization.4 Whether continental or national, the pattern holds — delivery is a coordination achievement before it is a technology achievement.
Prepare, execute, sustain
CentPol's view is that national AI strategy should be treated as a lifecycle rather than a one-time launch. Countries must prepare the ecosystem, execute through focused delivery mechanisms, and sustain progress through feedback, evaluation, capability-building, and revision.
Prepare means putting the foundations in place before scaling: data infrastructure and governance, baseline talent, legal clarity, and a credible delivery institution with a mandate. Regulatory sandboxes belong here — they let governments learn how to oversee AI under real conditions before writing rules they cannot enforce.
Execute means resisting the temptation to do everything at once. The delivery unit should sequence a small number of high-value sector initiatives, connect them to financing and procurement, and prove the operating model on workflows that matter but are not catastrophic if they stumble.
Sustain means building the feedback machinery that keeps a strategy alive: defined metrics, quarterly review cycles, public dashboards, a risk register, and explicit course-correction mechanisms. Because AI capabilities and risks change quickly, a plan without a revision rhythm is obsolete the moment it is published.
Procurement, data, and compute are delivery problems
It is tempting to treat procurement, data, and compute as technical prerequisites that someone else will handle. In practice they are where most strategies quietly fail, and they belong squarely inside the delivery institution's remit.
On procurement, the instinct to buy one large national platform should be resisted. As CentPol has argued in its public-service frameworks, that approach is expensive, risky, and tends to lock a country into a vendor-driven architecture. The better path is a modular operating layer: shared standards, reusable tools, secure infrastructure, approved vendors, and agency-level implementation teams coordinated by a central unit that measures performance.
On data, AI delivery depends on records that are accessible, governed, and trustworthy. Fragmented data, unclear rights, and missing infrastructure will limit even the best models. On compute, access must be planned deliberately and connected to national priorities rather than left to chance. None of these are side issues. They are the substance of delivery, and a strategy that does not name an owner for each of them has not yet become a plan.
What leaders should do next
Leaders who want to close the AI strategy gap can take a small number of decisive steps. First, name an owner and stand up a lean delivery institution with a clear mandate, anchored in the existing leadership structure rather than bolted on beside it. Authority should come from a Cabinet-recognized coordination role, not from headcount.
Second, attach a multi-year budget to the strategy's priorities. A target without financing is a wish. The delivery institution should publish how money maps to initiatives and what each is expected to produce.
Third, build a national pipeline and a public dashboard from day one. A single prioritized view of initiatives — with owners, milestones, and quarterly progress — turns a strategy into something that can be managed, corrected, and defended.
Fourth, invest in the unglamorous layer. Data governance, procurement templates, capability-building, evaluation methods, and coordination machinery rarely make headlines, but they determine whether anything scales. Funding isolated pilots produces case studies; funding shared foundations produces capacity.
Finally, institutionalize review. Set metrics, schedule quarterly reviews, maintain a risk register, and commit publicly to revising the strategy as evidence accumulates. A strategy that cannot learn cannot survive contact with a fast-moving technology.
Conclusion: delivery is the strategy
The next phase of national AI competition will not be won by the countries with the boldest documents. It will be won by the countries that can deliver — that can finance, coordinate, procure, build capability, and adjust as conditions change. AI will reward states that treat strategy as an operating discipline and punish those that treat it as a communications exercise.
For CentPol, this is the strategic message to every government drafting or refreshing an AI strategy: the plan is the easy part. Build the delivery institution, attach the budget, name the owners, connect the ministries, and create the review cycles. The strategy gap closes not when the vision improves, but when the state becomes able to deliver it.
