How to Design Citizen-Centred Digital Services

Share Post:

Table of Contents

How to Design Citizen-Centred Digital Services

Short Answer: Citizen-centred digital service design starts with deep understanding of citizen needs, contexts, and capabilities—then designs services around that understanding rather than around internal government processes. The core practices are: research with diverse users, co-design with citizens, iterative prototyping, accessibility testing across devices and languages, and continuous feedback loops after launch.

Citizen-centred digital services are the gold standard that African governments should aspire to—and the standard most current government digital services fall significantly short of. The gap is not primarily technical. It is methodological: most government digital services are designed by IT teams and policy officials with minimal input from the citizens who must actually use them.

This post outlines the practices and principles of citizen-centred service design as they apply to African government contexts—practical guidance for teams and leaders who want to build services that work for people, not just for administrators.

The Citizen-Centred Design Principles

Start With the User Need, Not the Government Process

The fundamental reorientation of citizen-centred design is moving from “how do we digitise our current process?” to “what does a citizen need to accomplish, and what is the simplest way to help them do it?” These are different questions. The answer to the first leads to digitised bureaucracy. The answer to the second leads to services that citizens actually use.

Research With Real Users

Effective user research is not a survey sent to agency mailing lists. It is direct observation of how citizens currently navigate services, structured interviews that probe frustrations and workarounds, and testing with users across the full demographic range—including those with low digital literacy, limited connectivity, and feature phones.

Design for the Hardest Case First

If a service works for the citizen with the lowest digital literacy, the poorest connectivity, and the most limited device, it will work for everyone. Designing for the easiest case—the urban, educated, smartphone user—and then trying to retrofit accessibility produces services that never quite work for those who need them most.

Iterate Based on Evidence

No digital service design is perfect the first time. Build prototypes, test them with real users, identify what fails, improve, test again. This iterative approach is standard practice in private sector product development but remains unusual in government, where the temptation is to design comprehensively in advance and deploy fully. The agile alternative produces better outcomes with less wasted investment.

Build Feedback Mechanisms In

Services that do not collect ongoing user feedback cannot improve. Every government digital service should include a simple, accessible feedback mechanism—a short satisfaction rating, a comment channel, an escalation path—that gives citizens a voice after their service interaction and gives service managers ongoing insight into service quality.

Practical Steps for African Government Agencies

  1. Map the current citizen journey for the service you are digitising—from the citizen’s perspective, not the agency’s.
  2. Conduct user research with a representative sample of citizens—including rural users, non-English speakers, and feature phone users.
  3. Define success metrics in citizen terms: completion rate, satisfaction score, time saved compared to the physical alternative.
  4. Build a prototype and test it with 10–20 users before committing to full development.
  5. Launch in beta with a subset of users before full rollout.
  6. Publish performance data publicly to drive accountability and continuous improvement.

Key Takeaways

  • Citizen-centred design starts with understanding user needs, not digitising existing government processes.
  • Research with real users—across the full demographic range—is non-negotiable for services that work for everyone.
  • Designing for the hardest case first produces services that are genuinely inclusive.
  • Iterative prototyping and testing produces better outcomes than comprehensive upfront design.
  • Built-in feedback mechanisms enable continuous improvement and sustain citizen trust.

Frequently Asked Questions

How much does citizen-centred design cost compared to traditional government IT procurement?

Citizen-centred design adds cost at the research and prototyping stage—but reduces cost overall by identifying what does not work before expensive development is complete. The savings from avoiding failed systems far outweigh the investment in user research and iterative design.

How can government agencies reach low-digital-literacy citizens for user research?

Partner with community organisations, local government officers, and civil society groups that have existing relationships with low-connectivity, low-literacy populations. Mobile field research teams can conduct in-person research in communities where digital survey methods would miss the target population.

About the Author

Suleiman Isah is the Director General of NSITDEA and a champion of citizen-centred public service design in Niger State. Read more.

Related: GovTech Pillar Page | Digital Inclusion and Skills