When the Pilot Works and the National System Never Comes

Almost every national education programme begins the same way: with a pilot. A district, a hundred schools, a single region chosen to prove the idea before the country commits to it. It is a sensible instinct, and it often works — the devices arrive, the teachers engage, the results come back encouraging enough to justify going further. And then, more often than anyone likes to admit, the national system the pilot was supposed to unlock never quite arrives.

The failure is rarely the one everyone braced for. The technology worked; that was the whole point of the pilot. What breaks is the assumption that a system built to succeed in one carefully chosen place can simply be copied outward to the rest of the country. A pilot is usually run where conditions are good and attention is high — reliable power, a supported cohort, a vendor team on call. None of those travel. The moment the same system is asked to run in a school four hours past the last cell tower, with a teacher who was never in the launch and no one to phone, the pilot's quiet assumptions surface all at once.

A pilot is a claim about the future, and most claims are too small

The deeper problem is what a pilot is designed to prove. Too many are built to demonstrate that the idea can work somewhere, when the only question that matters for a ministry is whether it can work everywhere the ministry is responsible for. Those are different systems, and a pilot built to answer the first will not answer the second. It produces a good photograph and a poor foundation — a bespoke showcase that has to be substantially rebuilt the day it meets the real country, at which point the cost and the timeline everyone agreed to are both gone.

Design the pilot as the first province, not the demo

The alternative is to treat the pilot as the first slice of the real system rather than a separate proof of concept. That means the pilot runs on the same architecture the national system will — integrated rather than a bundle of apps stitched together for the occasion, offline-first from the very first school rather than as an upgrade promised later, and owned by the country rather than hosted on terms that change at scale. A pilot built this way proves the thing that actually needs proving: not that the idea can shine in ideal conditions, but that the system holds its standard as it travels.

It also means choosing the pilot schools honestly. A pilot made only of the easiest schools proves the easiest case, and the easiest case is not the one a national programme lives or dies on. Including the hard schools from the start — the ones with no signal, the ones whose teachers turn over, the ones at the end of the road — is uncomfortable, because it makes the early numbers look less tidy. It is also the only way to learn, while the stakes are still small, what the system will have to survive when the stakes are the whole country.

“A pilot built to be admired proves nothing a ministry can build on. A pilot built to be extended proves the only thing that matters.”

This is the standard NDX is built to hold from the first school rather than the hundredth: one integrated, nationally-owned, offline-first platform that runs the same way in the pilot as it will at national scale, so the pilot is a first instalment of the real system and not a prototype to be thrown away. The difference is invisible on launch day, when every pilot looks impressive. It becomes visible eighteen months later, in whether the country is running a national system or explaining why the successful pilot never became one.

If you are about to commission a pilot, the most valuable question to ask is not whether it will work. It is what happens to it when it succeeds — whether what you are proving can become the system you actually need, or whether you are funding a demonstration you will later have to rebuild. That is the conversation NDX is built for. See how it works, or start that conversation, at ndx.education.