ClientSokoto State Government
Population4.2M citizens
StackDjango · PostgreSQL · Vue.js · Ubuntu
RoleLead Architect & Delivery Lead

The Problem

Sokoto State's governance operations were running on a combination of paper processes, disconnected spreadsheets, and legacy systems that didn't talk to each other. Civil service records were unreliable. Public service requests had no tracking. The state government had visibility into almost none of its own processes in real time.

The brief was ambitious: build an integrated governance platform that would connect civil service management, public service delivery, and state administration into a coherent system — without disrupting operations that 4.2 million citizens depend on.

The Challenge

State government digital transformation projects fail for a predictable set of reasons: staff resistance, inadequate infrastructure, procurement that prioritises vendors over outcomes, and leadership transitions that kill momentum mid-project. Sokoto presented all of these.

The technical infrastructure was unreliable — intermittent power and connectivity in key offices. The civil service had legitimate concerns about a system that would make individual performance more visible. And the project timeline spanned an election cycle, which meant the political sponsorship could evaporate at any point.

The Approach

We designed for constraint from the start. Offline-first architecture with sync capabilities meant that offices with unreliable connectivity could continue working and sync when connectivity restored. The system was designed to run on modest hardware — no cloud dependency in daily operation.

On the human side, we embedded in the civil service for the first three months — not to extract requirements, but to build genuine relationships with the staff who would ultimately determine whether the system was used. We designed the civil service management module with input from civil servants, not just their supervisors. The resulting system felt less threatening because staff had shaped it.

We delivered in phases: civil service records first (highest internal demand), then public service tracking (highest citizen visibility), then the administrative intelligence layer that gave leadership the cross-departmental view they had originally requested.

The Outcome

The platform went live across key state ministries and has been operational through a leadership transition — the most important test of institutional durability. Civil service records for over 12,000 state employees are now digitised and actively maintained. Public service request tracking has reduced average resolution time and created accountability that didn't previously exist.

The local IT team can administer and extend the system without external support. That was the goal.

"Designing for offline-first isn't a workaround — it's the correct architecture for this environment."
— Funso Oyebami, Architect