The execution gap: Africa's real development bottleneck
Why the continent's hardest problem is not a shortage of strategy, and what it takes to close the distance between policy and delivery.
Spend a week in any capital on the continent and you will not run short of strategy. National development plans run to hundreds of pages. Sector roadmaps are detailed, costed, and frequently excellent. Donors arrive with frameworks; ministries publish visions; consultants leave behind slide decks that diagnose the problem with real precision. The ambition is rarely the issue. The bottleneck is what happens after the plan is signed.
We call this the execution gap: the widening distance between what a government has decided to do and what actually reaches a citizen, a clinic, a farm, or a school. It is the least glamorous part of development and, in our experience, the most decisive.
The gap is not where we keep looking
Most development effort is concentrated at the two ends of the journey: the strategy at the start and the evaluation at the end. We are good at deciding what should happen and good, eventually, at measuring whether it did. The long middle, where decisions are converted into coordinated action across dozens of agencies, contractors, and front-line workers, receives a fraction of the attention and almost none of the prestige.
Yet that middle is where programmes are won or lost. A fertiliser subsidy is not a policy document; it is ten thousand logistical events that either happen on time or do not. A vaccination campaign is not a target; it is a cold chain, a roster, and a supply line that hold together or break. When these fail, they rarely fail loudly. They fail quietly, in ways that are invisible until the results come in below expectation and everyone reaches, again, for a new strategy.
“The continent does not have an ideas problem. It has an execution infrastructure problem.”
What the execution gap actually looks like
On the ground, the gap is mundane and specific. It is the district officer who cannot see whether the funds released in the capital ever arrived. It is the four agencies running four spreadsheets that never reconcile. It is the contractor paid against a milestone that no one independently verified, and the programme manager who learns of a stalled site three months too late to intervene.
None of this is a failure of intelligence or commitment. It is a failure of visibility and coordination, the connective tissue that lets a large public effort behave as one system rather than a hundred disconnected ones. Where that tissue is missing, even well-funded, well-designed programmes degrade into a series of hopeful hand-offs.
Why strategy keeps outrunning delivery
There are structural reasons the gap persists. Strategy is cheap to produce and politically rewarding; delivery is expensive, slow, and rarely credited. A new plan signals action. The patient work of making the last plan function does not make headlines. So the incentive, repeated across cycles, is to re-strategise rather than to finish.
There is also a tooling problem. The systems that govern public delivery are often a patchwork: a donor-funded portal here, a legacy database there, a great deal of paper and WhatsApp in between. Each was built for one programme, by one team, for one moment. None of them talk to each other, and none of them outlive the funding that created them. The result is that every new initiative rebuilds its own plumbing from scratch, and institutional memory leaks away with each transition.
Closing the distance
Closing the execution gap is not a matter of more ambition or another framework. It is a matter of building the infrastructure that delivery actually runs on, and treating that infrastructure as a long-lived public asset rather than a project deliverable. In practice, that means three things.
Make delivery visible. Before anything can be held accountable, it has to be seen. A single, trusted view of what is happening across a programme (what has been released, what has arrived, what remains) is the precondition for every other improvement.
Coordinate across the seams. The hardest failures live at the boundaries between agencies. Systems that let separate institutions share a common operating picture, without surrendering their autonomy, turn a hundred disconnected efforts into something that moves together.
Build to last. Infrastructure that disappears when the funding ends was never infrastructure. The systems that matter are the ones a ministry can own, staff, and run on its own terms long after the original partner has gone.
The continent's next decade will not be decided by the quality of its plans. It will be decided by whether those plans can be carried, reliably, visibly, and at scale, into the lives they were written for. That is the work of execution, and it is the work we believe matters most.
