When an institution cannot see itself — cannot measure its own operations, track its own outputs, account for its own resources — it cannot improve. It can only react. Problems surface as crises. Decisions get made on instinct. Resources disappear into opacity. The institution drifts.
This is the condition of most of Africa's public institutions today. Not because the people inside them are incompetent. But because they have been operating without the instruments that would let them see.
What "seeing" actually means
There is a tendency, when discussing institutional technology, to reach immediately for the glamorous — dashboards, AI, predictive analytics. But the problem Africa's institutions face is more fundamental than that. Most of them do not have a reliable answer to basic questions:
- How many customers does this water utility serve?
- Of those, how many paid last month?
- Of those who didn't pay, how many have been disconnected?
- How many reconnections are pending?
- What is the average time between a reported fault and its resolution?
These are not sophisticated questions. They are the operational basics — the floor of institutional visibility. And in most African utilities, constituency offices, and community health structures, they are unanswerable without significant manual effort, if they are answerable at all.
This is the gap. Not AI. The gap is structured data about what the institution actually does, updated in real time, accessible to the people who need to act on it.
"I cannot tell you how many connections we have right now. I would have to go through the ledgers manually. That would take days. The number changes daily." <span slot="attribution">— Operations Manager, mid-sized Kenyan water utility, 2023</span>
When we first started working with water utilities in Kenya as part of the research that became AccessWASH, we expected to find outdated technology. We found something more surprising: no technology at all, in the sense that mattered. Billing was done in spreadsheets emailed between departments. Fault reports came in on WhatsApp. Reconnection orders were handwritten and physically delivered to field teams. Asset records — the map of the network, the location of each valve and meter — existed in one engineer's mental model, occasionally committed to paper.
This is not a technology problem in the sense that "they need better software." It is an instrumentation problem. The institution has not been equipped with the instruments that let it observe itself.
What changes when you can see
When an institution gains operational visibility — when it can finally see itself — three things happen in sequence:
First, problems become legible. Before visibility, a water utility that loses 40% of treated water to non-revenue losses simply experiences that loss as a vague pressure: revenue doesn't add up, the numbers don't balance, there is a feeling of scarcity. After visibility, non-revenue water becomes a number — 38.4%, measured weekly. It has a location. It has a pattern. It becomes something that can be acted on.
Second, accountability becomes possible. This is the uncomfortable change, and the one that generates the most institutional resistance. When performance is measured, performance can be evaluated. The constituency office that processes applications in fourteen days instead of the mandated three is now visible. The field team that closes fault reports without actually visiting the site is now visible. Visibility redistributes power. It shifts information from being held by individuals to being held by the institution.
Third, learning becomes structural. An institution that can see itself can compare this month to last month. It can run an experiment — change a process, measure the effect. It can train new staff against documented procedures rather than tribal knowledge. Institutional knowledge stops being locked inside individual heads where it disappears when staff leave. It becomes embedded in systems where it compounds.
| Metric | Before (manual) | After (AccessWASH) | Change |
|---|---|---|---|
| Revenue collection rate | 54% | 78% | +24 pp |
| Average fault resolution time | 11.3 days | 4.1 days | −64% |
| Non-revenue water (NRW) tracked | Not measured | 38.4% (weekly) | Newly visible |
| Customer ledger accuracy | ~60% (est.) | 97% | +37 pp |
| Time to generate monthly report | 3–5 days | < 1 hour | −95% |
| Disconnection notice cycle | 14 days | 3 days | −79% |
Selected operational metrics: before and after digital instrumentation at a Kenyan water utility, 2021–2023
These numbers are not hypothetical. They are drawn from the first wave of AccessWASH deployments at Kenyan water utilities between 2021 and 2023. The gains are significant — but what is more significant is the mechanism. None of these improvements required new investment, new staff, or new physical infrastructure. They required the institution to be able to see what it was already doing.
Why visibility is so hard to achieve
If the gains are so clear, why don't all institutions invest in operational visibility? The barriers are real.
The data collection problem. Building the instruments requires knowing what to measure. This sounds obvious, but in practice it requires deep sectoral knowledge. Water utilities and constituency offices are not generic organisations — they have specific workflows, specific constraints, specific failure modes. Generic software (imported enterprise systems designed for European municipalities) rarely fits. The instrumentation has to be built for the specific institution.
The connectivity problem. Many of the operations that need to be tracked — field service, meter reading, community health visits — happen in places with unreliable or no internet access. An instrumentation system that requires constant connectivity will fail exactly when it is most needed. Offline-first architecture is not an optional feature. It is a prerequisite.
The adoption problem. An institution that has operated on manual processes for decades has a deeply embedded workflow. The forms, the ledgers, the WhatsApp groups — these are not just tools. They are the way things are done. Replacing them requires training, and training requires sustained engagement. A software deployment that ends with a handover and a manual does not change how an institution operates. Institutions change through practice, not documentation.
The trust problem. In many African public institutions, data visibility has historically been associated with external audit and accountability mechanisms — donors, regulators, oversight bodies. To the institution's own staff, being made visible feels like being watched. Building trust that operational data serves the institution's own interests, not a surveillance agenda, takes time and intentional communication.
The translation layer
What we have learned, building AccessWASH and BungeConnect, is that the gap between "the technology exists" and "the institution can see itself" is not a technical gap. The technology does exist. The gap is translation.
Translation means understanding the institution's actual workflow before proposing to change it. It means knowing that the field technician in Nakuru who records faults on paper does so because the mobile app crashes when the network drops — and building offline-first before expecting adoption. It means recognising that the constituency office manager who keeps constituent records in a physical ledger does so because every digital system previously deployed has disappeared when the project funding ended — and building for sustainability before expecting trust.
Translation is expensive. It requires being inside the context, not outside it. It requires sustained presence — not a deployment visit, but an embedded relationship over years. It is the thing that most technology interventions in African institutions skip, because it is hard to invoice and hard to put in a slide deck.
It is also the only thing that makes the technology work.
What comes next
The first generation of digital instrumentation for African institutions is underway. The utilities that have deployed AccessWASH can now see themselves. The constituency offices piloting BungeConnect can track constituent requests from intake to resolution. These are early deployments — but they demonstrate that the vision is achievable.
What comes next is harder: making these systems self-sustaining, building the institutional capacity to maintain and evolve them without external technical support, and proving the model across enough deployments that it becomes the default rather than the exception.
The technology exists. The translation work is the work. Visibility is the first step — and the step that makes everything else possible.
— Ken Ruto
