Most products fail not because of bad technology, but because of bad assumptions. Assumptions about what users need, how they behave, what constraints they operate under, and what they will actually adopt and sustain. Human-centered design (HCD) exists to replace those assumptions with evidence — and to ensure that the people a product is meant to serve are present, visible, and heard throughout the design process.
This is not a new idea. But in a world where digital products are proliferating faster than ever — and where the gap between products that work and products that sit unused remains stubbornly wide — human-centered design methodology has never been more important. Particularly in Africa, where diverse contexts, infrastructure constraints, and underrepresented user groups make assumptions especially dangerous, HCD is not a nice-to-have. It is the foundation of effective design.
This article sets out what human-centered design is, how the process works, and what it looks like in practice — drawing on both established examples and our own work as an HCD consultancy across Africa.
Most products fail not because of bad technology, but because of bad assumptions. Human-centered design replaces assumptions with evidence.
What is Human-Centered Design?
Human-centered design is an approach to creating products, services, and experiences that places the needs, behaviours, and realities of users at the centre of every design decision. Rather than starting with a solution and working backwards, HCD starts with deep understanding of the people being designed for — and works forward from there.
The premise is straightforward: products designed around real user needs are more likely to be adopted, more likely to be effective, and more likely to create lasting change than products designed around assumptions, internal priorities, or technological capability alone.
As a UX design process, HCD is iterative rather than linear. It is not a checklist to be completed once, but a continuous cycle of learning, testing, and improving. It brings together researchers, designers, developers, and — critically — the communities being served, and it treats the gap between what a product does and what users actually need as a problem to be solved, not a compromise to be accepted.
The Human-Centered Design Process
The HCD process moves through four core phases. In practice these phases are rarely sequential — good design teams move back and forth between them as they learn — but they provide a useful framework for understanding how human-centered design methodology works.
1. Discovery: Understanding Before Designing
The discovery phase is about building a deep, evidence-based understanding of the people you are designing for before any solution is conceived. This requires going into the field — conducting interviews, running focus groups, undertaking observational research, and spending time in the contexts where users actually live and work.
Discovery is where assumptions go to be tested. It is where design teams learn that users don't behave the way they expected, that the problem they came to solve is not the problem users actually have, or that the solution they had in mind would fail for reasons they hadn't anticipated. Getting this wrong is expensive; discovering it early is invaluable.
Common discovery methods include in-depth user interviews, ethnographic observation, diary studies, stakeholder mapping, and the development of user personas — composite portraits of real user groups, grounded in research, that help design teams maintain a consistent picture of who they are building for as the work progresses.
2. Ideation: Generating Solutions Worth Testing
With a grounded understanding of user needs, the ideation phase turns insight into possibility. The goal is not to arrive at the right solution immediately, but to generate a wide range of candidate solutions — and to do so collaboratively, drawing on the perspectives of designers, developers, researchers, and users themselves.
Effective ideation techniques include structured brainstorming, mind mapping, design sprints, 'How Might We' framing, and co-creation workshops with the communities being served. The emphasis is on breadth first — generating many ideas before narrowing — and on suspending judgment long enough to explore unconventional possibilities.
The output of ideation is not a final solution but a set of hypotheses: ideas worth testing. The quality of those hypotheses depends directly on the quality of the discovery work that preceded them.
3. Prototyping: Making Ideas Tangible
Prototyping is the process of turning a hypothesis into something testable. Prototypes can range from rough paper sketches to fully interactive digital mockups, depending on what needs to be tested and at what stage of development the team is at.
Low-fidelity prototypes — paper mockups, cardboard models, wireframe sketches — are fast and cheap to produce, and ideal for testing fundamental assumptions about how a product works before any significant development investment has been made. High-fidelity prototypes, which more closely resemble the finished product, are appropriate later in the process when the core concept is established and the team is testing usability and experience details.
The discipline of prototyping forces clarity. It is one thing to describe a solution in a meeting; it is another to put something in front of a user and watch what happens. Prototypes make ideas concrete enough to be challenged, and fragile enough to be discarded without loss.
4. Testing: Learning from Real Users
Testing closes the loop between design intent and user reality. It involves putting prototypes in front of real users — ideally in their actual environments — observing how they interact with them, and gathering structured feedback to inform the next iteration.
Effective user testing is not about proving that a design works. It is about discovering where it doesn't — and why. A test that surfaces problems is more valuable than one that confirms assumptions. The findings from testing feed directly back into the discovery and ideation phases, making the process genuinely iterative rather than nominally so.
Across Made by People's work in Africa, user testing in the field has consistently surfaced insights that would not have emerged in a studio or a boardroom: the interface that seemed intuitive to designers but confused first-time smartphone users; the feature that the research team thought was peripheral but that users identified as the most important; the context — intermittent connectivity, shared devices, noisy environments — that changed what the product needed to do entirely.
HCD in Practice: Case Studies
The value of human-centered design methodology is best understood through real projects. The following examples — two from Made by People's own work, two from other organisations — illustrate what HCD looks like when applied rigorously to complex problems.
Made by People — Case Study
War Child Holland — Designing for Children Affected by Conflict
In Malakal, South Sudan — one of the most difficult operating environments on the continent — Made by People worked with War Child Holland to design a digital tool for children affected by armed conflict. What made this project unusual, and unusually rigorous, was that field deployment wasn't limited to the research and design phase. Our designers went first: conducting discovery work in Malakal itself, building an understanding of how children and their caregivers used technology, what devices and connectivity they had access to, and what emotional and practical needs the tool needed to address. Then our developers followed — travelling to Malakal to test what they had built against the actual conditions on the ground. Not a simulation of those conditions, not a best guess from Nairobi, but the real thing: the hardware available, the connectivity (or lack of it), the environment in which the product would actually be used. Only once the product had been tested and refined in the field was it handed over to War Child Holland. That end-to-end commitment to proximity — designers and developers both grounded in the same reality as the users — is what the HCD process demands, and what this project delivered.
Made by People — Case Study
BRAC — Delivering Financial Literacy Where Infrastructure Ends
BRAC, one of the world's largest development organisations, engaged Made by People to conduct user research and design work across Kenya, Rwanda, and Sierra Leone. The Sierra Leone component brought the team face to face with one of the most demanding design challenges we have encountered: delivering financial literacy tools to communities in remote villages where there was no reliable electricity and no internet access whatsoever. The question was not how to optimise a digital product for low connectivity — it was whether a digital product was the right answer at all, and if so, what it would need to do entirely offline, on a single charge, in a context where charging infrastructure might be a day's travel away. Answering that question required being in those villages, with those communities, understanding their daily routines and constraints at a level of specificity that no desk research could produce. The work across all three countries reinforced something we see consistently: the greater the adversity of the environment, the more essential human-centered research becomes. Assumptions that hold in one context collapse in another. Only field proximity reveals the difference — and only designs built around that reality have a chance of working.
Example
Redesigning a Hospital Waiting Room
A design team tasked with improving the patient experience at a hospital began not with furniture catalogues or architectural plans, but with observation. Spending time in the waiting room with patients and their families, they identified three friction points that interior design conventions had consistently overlooked: inadequate privacy for sensitive conversations, seating that was uncomfortable for patients with mobility issues, and lighting that made the environment feel clinical and anxiety-inducing rather than calm. The redesign addressed each of these directly — private seating alcoves, ergonomic chairs, warmer ambient lighting — and produced measurable improvements in patient satisfaction. None of these interventions would have been identified without the observation work that preceded them.
Example
Simplifying a Mobile Banking Application
A financial services team noticed that user drop-off rates on their mobile banking app were highest during onboarding and at the payment confirmation step — but didn't know why. Usability testing with real users, conducted in the environments where they actually used the app (on public transport, in markets, with background noise and intermittent connectivity), revealed two specific issues: navigation labels that made sense to the product team but were opaque to users, and a confirmation screen that required too many steps under time pressure. Targeted redesign of these two elements reduced drop-off significantly. The fix was straightforward once the problem was properly understood — and impossible to identify without testing with real users in real conditions.
Implementing Human-Centered Design in Your Organisation
Adopting HCD as an organisational practice requires more than sending a team to a design thinking workshop. It requires a shift in how decisions are made, whose voices are centred, and how success is measured. Based on our experience as an HCD consultancy working across Africa, the following conditions are foundational:
Build empathy into your process, not just your values
Organisations frequently articulate user-centricity as a value without building the structures that make it operational. Empathy in HCD is not an attitude — it is a practice. It requires dedicated time for user research at the beginning of every project, mechanisms for bringing user feedback into design decisions throughout, and a culture that treats time spent with users as investment rather than delay.
Involve the right people from the start
Human-centered design produces better outcomes when the full range of relevant perspectives — designers, developers, researchers, programme staff, business leads, and most importantly the communities being served — are involved from the discovery phase, not consulted at the end. Co-design is more demanding than consultation. It is also more likely to produce solutions that last.
Treat iteration as a feature, not a failure
In organisations accustomed to linear project delivery, the iterative nature of HCD can feel like instability. It isn't. Discovering that a design needs to change in response to user testing at week four is not a setback — it is the process working correctly. The alternative is discovering the same problem at launch, at far greater cost.
Invest in design capability
Human-centered design requires skilled practitioners — in user research, facilitation, UX design, and synthesis. Organisations that treat design as a finish applied at the end of a process, rather than a discipline embedded throughout, consistently produce weaker outcomes. Investment in design capability pays for itself in reduced rework, higher adoption rates, and products that actually work for the people they are meant to serve.
Measure what matters to users, not just to the organisation
HCD projects should be evaluated not only against organisational KPIs but against user outcomes: Is the product being used? Is it solving the problem it was designed to solve? Are users able to accomplish what they came to do? Evaluation methods — user feedback, usability testing, analytics, and direct observation — should be built into the project from the outset, not appended as an afterthought.
Why HCD Matters More in Africa
In any context, human-centered design produces better outcomes than assumption-led design. In Africa, the stakes are higher and the margin for error is narrower.
Africa's user populations are among the most diverse and least represented in global design practice. The contexts in which products need to work — variable connectivity, multilingual households, shared devices, low digital literacy in some communities and high in others, infrastructure constraints that render standard solutions unworkable — cannot be designed for from a distance. They require proximity.
At Made by People, we have conducted HCD research across more than 18 African countries — in informal settlements, in rural farming communities, in active conflict zones, and in dense urban markets. Each context has taught us something that assumptions would have missed. That is the value of the methodology: not the framework itself, but the discipline of going to find out.
Africa's user populations are among the most diverse and least represented in global design practice. You cannot design for these contexts from a distance. You have to go and find out.
Conclusion
Human-centered design is the most reliable approach we have to building products and services that work — not in theory, not in presentations, but in the hands of the people they are meant to serve. The process is demanding. It requires time, skill, and a genuine willingness to let user evidence override internal assumptions. But the alternative — designing without it — is more expensive, less effective, and ultimately less honest about whose needs are being centred.
If you are building something for communities across Africa, we'd be glad to talk about how human-centered design can make it better.