Why 80% of African E-Government Projects Fail Before Launch

There is a specific kind of failure that haunts African government digitisation projects. It is not the dramatic collapse — the system that crashes on launch day, the app that citizens mock on social media. That failure at least produces a lesson.

The more common failure is quieter and more expensive. It is the project that never quite launches. The platform procured, configured, and installed — but never actually used. The digital permit system that runs parallel to the paper process for three years because no one made the call to switch. The e-procurement portal that exists in the server room but not in the workflow of a single procurement officer.

Across Africa, governments have spent billions on digital transformation initiatives since 2010. The results, measured honestly, are mixed at best. According to research by the Mo Ibrahim Foundation and corroborated by multiple World Bank assessments, fewer than one in five African e-government initiatives achieves sustained operational use at scale within five years of launch.

The question is why. And the answer, almost without exception, is not technology.

The Technology Is Rarely the Problem

This is the first thing every digital government practitioner learns — and the last thing most procurement committees believe. By the time a government has selected a vendor, negotiated a contract, and received a working system, the technology is generally functional. SAP works. Oracle works. The custom-built citizen portal works in the testing environment. The problem begins the moment the system meets the institution.

What follows is a familiar sequence. The vendor hands over the system and departs. The IT department is responsible for maintenance but was not consulted during procurement. The frontline staff who must use it daily received a half-day training session six months ago. The senior official who championed the project has been reassigned. And nobody has formal authority to make the system mandatory — so nobody does.

This is not a technology failure. It is a delivery failure.

The Four Real Reasons Projects Stall

After examining digital government rollouts across Nigeria, Kenya, Ghana, Tanzania, Rwanda and South Africa, four structural causes appear consistently:

1. No single owner with authority and accountability. Digital projects in government are typically owned by a committee. Committees do not implement — they discuss. Successful digital rollouts have one named individual with the authority to make decisions, override resistance, and be held accountable for the outcome. In most African government structures, this person either does not exist or has the responsibility without the authority.

2. Procurement designed for acquisition, not delivery. Government procurement frameworks are built to acquire technology, not to deliver outcomes. A contract that specifies server specifications and software licences says nothing about user adoption rates, process integration, or what happens when the system conflicts with existing workflows. The contract ends at handover. The real work begins at handover.

3. Change resistance that was never mapped. Every digital transformation displaces someone. It removes discretionary power from officials who currently control paper-based processes. It makes previously invisible transactions transparent. It threatens the income streams — formal and informal — of people who have built careers around the current system. None of this is surprising. All of it is predictable. Almost none of it is accounted for in the implementation plan.

4. Political momentum without institutional continuity. African government digital projects frequently launch on the energy of a single political champion — a minister, a governor, a reform-minded DG. When that individual moves on, the project loses its protection. Without institutional embedding — standard operating procedures, trained staff, mandatory use policies — the project exists only as long as its champion does.

What the Successful Ones Do Differently

The minority of digital government projects that do succeed share a common pattern. They start smaller than the ambition. They identify a single high-friction, high-visibility process — permit applications, payroll verification, procurement approvals — and digitise that one thing completely before expanding. They name a delivery owner. They map the resistance and address it directly. And they build the mandatory use policy before the technology arrives, not after.

Germany's approach to public sector digitisation — particularly at municipal level — offers instructive contrast. German local authorities typically run parallel digital and paper systems for a defined, time-limited transition period with a published end date for the paper process. The end date is what drives adoption. Without an end date, paper never dies.

The Governance Question Nobody Asks

The most important question in any digital government project is not "which system should we procure?" It is "who is responsible for making this work, and what happens to them if it doesn't?"

Until African governments build delivery accountability into digital transformation governance — not just procurement governance — the pattern will continue. The systems will be acquired. The servers will be installed. The ribbon will be cut. And three years later, the paper forms will still be in the tray.

The technology is ready. The institutions are the project.