What It Really Takes to Build Products That Matter in Africa
Nigerian Product Manager Onyinyechi Eunice Ezeh explains why useful products start long before the first line of code, and why the real work continues long after launch.
Choose your narrator

In short
Building a useful product in Africa starts with understanding the real problem and the local context before building, focusing on the few features that matter most, and continuing to learn from users after launch.
- Desk:
- tech
- Format:
- article
- Author:
- Onyinyechi Eunice Ezeh
The Work Behind the Product: What It Really Takes to Build Something Useful
A product can be well-designed, technically sound and delivered on schedule, yet still fail to make a meaningful difference in the lives of the people it was created for.
That possibility raises an important question: what does it actually take to build something useful?
The answer goes beyond having a promising idea, assembling a capable team or finding the technology to bring a solution to life. It begins with the decisions made before building starts, continues through the choices made during development, and remains important long after a product reaches its users.
As a Product Manager, I have come to appreciate that the work behind a product is often less visible than the product itself. People see the application, platform or service. They may not see the conversations, questions, competing priorities, assumptions and difficult trade-offs that shaped it.
Yet those decisions can determine whether a product becomes genuinely useful or simply becomes another solution looking for a problem.
The problem deserves more attention than the solution
There is an understandable excitement around building. An idea emerges, its potential becomes clear, and attention quickly shifts to what can be developed. Teams begin discussing features, timelines, resources and delivery.
But there is a question worth asking before any of that takes over: do we understand the problem well enough to know what we should build?
A problem can appear obvious from a distance. A business owner may seem to need a digital platform. A customer may appear to need a faster service. An organisation may believe that automating a process is the most effective way to improve it.
However, what appears obvious to the people designing a solution may not reflect the experience of the people expected to use it.
The difference matters.
People do not experience problems in neat product categories. They experience delays, uncertainty, financial pressure, inconvenience, missed opportunities and tasks that take more effort than they should. A useful solution must account for the circumstances in which those problems occur.
This requires more than asking people whether they like an idea. It requires understanding how they currently manage the problem, what they have tried, what prevents them from finding a better alternative and what would make a proposed solution worth adopting.
Without that understanding, teams risk becoming attached to a solution before establishing whether it addresses the right need.
Context changes what usefulness looks like
This question becomes particularly important when building for African markets.
Africa is not one uniform market. Its countries, industries, communities and consumer behaviours differ considerably. Even within one country, the realities of a small business in a major commercial city may be very different from those of a business operating in a smaller town.
The conditions surrounding a product matter: purchasing power, infrastructure, access to reliable internet, digital confidence, existing work practices and the alternatives available to potential users.
Research by the International Finance Corporation (IFC) and the World Bank illustrates why these realities deserve attention. A 2023 study of 3,325 microenterprises across seven African countries, including Nigeria, found that fewer than 7% used smartphones or computers for business. Seventy-one per cent reported that they saw no need for these technologies.
That finding should not be interpreted as evidence that digital tools have no value to these businesses. The research also points to barriers including affordability, digital skills and infrastructure constraints. It does, however, raise a significant question for anyone building products for this segment: are we creating solutions that fit the realities of the businesses we hope to serve?
The IFC’s 2024 research, Digital Opportunities in African Businesses, further highlights the potential for digital upgrades, alongside persistent barriers such as high technology costs, infrastructure limitations and insufficient funding.
These are not peripheral considerations to be addressed after a product has been built. They influence whether the product can be accessed, understood, afforded and used consistently in the first place.
A solution can be impressive in a demonstration and still be impractical in someone’s daily routine. It can offer extensive functionality while asking users to change established behaviours without giving them a compelling reason to do so.
Building for a market therefore requires more than identifying an opportunity. It requires understanding the people within that market and the conditions shaping their decisions.
Evidence should challenge our assumptions
Understanding a problem is not a one-time exercise, and it should not depend solely on the opinions of the people in the room.
Product decisions are stronger when they draw from multiple sources of evidence. Direct conversations with users reveal experiences, motivations and frustrations that may not appear in reports. Existing market research helps establish whether those observations reflect a wider pattern. Product data can show how people behave once they interact with a solution.
Each source offers a different perspective.
Customer conversations can reveal why someone has not adopted a product. Usage data may show where people stop engaging. Market research can help establish the scale of a problem. Together, these sources give teams a more informed basis for deciding what deserves attention. This has been particularly relevant in my work as a Product Manager at WadataHR, a Nigerian people operations and payroll platform. While examining an existing product direction, I found it important to move beyond internal assumptions and bring customer discovery, direct conversations with people and available market data into the discussion. The intention was to help the team consider whether the direction reflected a genuine need, rather than simply what we believed would be useful.
That experience reinforced something I consider essential to product work: decisions should not be made in isolation, and confidence in an idea should never make it immune to scrutiny. A healthy product culture must make room for questions, constructive disagreement and new information. The goal is not for one person to be right. The goal is to make a better decision.
Building is a series of decisions, not a single delivery milestone
Even when a problem is well understood, deciding what to build is another challenge.
Teams rarely have unlimited time, funding or capacity. There will always be more needs to address, more features to consider and more expectations to manage than can reasonably be delivered at once.
This is where prioritisation becomes important.
The question is not simply which feature sounds most attractive or which request came in most recently. It is which problem matters most, which intervention is likely to create meaningful value, and what the team can realistically deliver.
Sometimes the best decision is to build less. A product with fewer, well-executed capabilities may serve its users better than one crowded with features that introduce complexity without addressing their most important needs. Every additional feature carries a cost: development time, maintenance, support, user attention and the possibility of making the overall experience harder to navigate.
These trade-offs require teams to consider more than what is technically possible. They must weigh user needs against business objectives, available resources and the practical realities of delivery.
The Product Manager plays an important role in facilitating these conversations, clarifying requirements, helping teams evaluate priorities and keeping decisions connected to the problem being solved. This is collaborative work. It depends on the perspectives and contributions of design, engineering, business stakeholders and the people the product is intended to serve. A product does not become useful because every stakeholder gets their preferred feature. It becomes useful when the team can align around the right problems and make deliberate choices about how to address them.
The work does not end at launch
There is another assumption worth reconsidering: that launching a product is the point at which the hardest work is complete.
In reality, launch is one of the points at which a team begins receiving a different kind of evidence.
Before launch, decisions are informed by research, conversations, hypotheses and what the team knows about the market. After launch, people interact with the product in ways that may confirm some assumptions and challenge others.
Some users may adopt it quickly. Others may sign up but rarely return. Some may use a particular feature differently from what the team anticipated. Others may encounter difficulties that were not obvious during testing. These behaviours deserve attention.
A registration is not the same as sustained usage. Usage alone does not necessarily mean that a product is delivering the outcome people need. Retention can indicate that users continue to find value, but it must also be understood in context. A person returning to a product because there is no better alternative is not necessarily experiencing the same value as someone returning because the product genuinely makes an important task easier.
Working on an early-stage product such as WadataHR has also reinforced the importance of this ongoing learning. Building for businesses means that understanding their needs cannot stop at the point of discovery. Teams must continue paying attention to how people interact with the product and what those interactions reveal about the value being delivered.
This is why product teams need to keep listening and learning after release.
Feedback, usage patterns, customer conversations and business performance should inform what happens next. Sometimes the evidence points to an improvement. Sometimes it suggests that a feature needs to be reconsidered. And sometimes it reveals that the original understanding of the problem was incomplete.
Being willing to respond to that evidence is not a sign that the team failed. It is part of responsible product development.
The objective is not to build something once and defend every decision that went into it. It is to keep improving the product’s ability to deliver value as people’s needs and circumstances evolve.
What matters is the value that remains
The work behind a product is a continuous exercise in judgement.
It involves knowing when to investigate further, when to challenge an assumption, when to prioritise one need over another and when to accept that an earlier decision should change. It requires teams to balance ambition with context, evidence with experience, and the desire to build with the responsibility to build something that people can actually use.
For African innovators and businesses, the opportunity to create meaningful solutions is significant. But opportunity alone does not guarantee usefulness. The quality of what we build will depend, in part, on how carefully we understand the problems, people and environments we are building for.
Ultimately, the success of a product should not be measured only by the fact that it was launched, the number of features it contains or the sophistication of the technology behind it. We should also ask whether it makes an important task easier, addresses a recurring need, creates a meaningful improvement or helps someone achieve something they previously struggled to do.
Because the real work is not simply bringing an idea to life.
It is making the decisions that give that idea a reason to matter.
- Tech in Africa
- Building products in Africa
- Nigerian product manager
- product management Nigeria
Tip: highlight any line in the story to turn that line into a share card.
Frequently asked
- What is “What It Really Takes to Build Products That Matter in Africa” about?
- Nigerian Product Manager Onyinyechi Eunice Ezeh explains why useful products start long before the first line of code, and why the real work continues long after launch. The Work Behind the Product: What It Really… Nigerian Product Manager Onyinyechi Eunice Ezeh explains why useful products start…
- Who covers tech on PINCHED?
- Onyinyechi Eunice Ezeh reports this piece for the PINCHED tech desk.
- Where can I read “What It Really Takes to Build Products That Matter in Africa”?
- Read it in full at https://staypinched.site/read/what-it-really-takes-to-build-products-that-matter-in-africa.












