By Arinze Chiama

A product team I could describe from a dozen different companies is sitting in a room with an ambitious growth target on the wall. Customer requests have piled up over the quarter. A competitor has just shipped something shiny. The feeling is that the product is falling behind, and the obvious cure is to build more. It almost always feels like the responsible thing to do. What I have learned watching these rooms across fintech, healthcare, legal services, education and recruitment is that more functionality is rarely what a struggling product actually needs. What it needs is a clearer answer to a much older question. What problem are we here to solve, and for whom.

Complexity almost never arrives through bad intent. It arrives one reasonable yes at a time. Each feature is defensible on its own. Someone important asked for it, a big customer hinted they might leave without it, a rival has it and the sales team is tired of explaining its absence. Added together, those sensible decisions produce a product that is harder to build, harder to maintain and harder to use. The evidence for this is older than most startups. In a 2006 Harvard Business Review piece on feature fatigue, researchers found that customers ask for more capabilities before they buy, then feel overwhelmed and less satisfied once they live with the product. We request more and are happier with less.

What gets missed is that every yes is also a no somewhere else. Engineering time is finite. A week spent building for a handful of loud users is a week not spent on what most of your customers quietly struggle with. This is opportunity cost, and it stays invisible precisely because the thing you did not build never appears in a standup or a release note. Prioritisation done well is not a ranked list of everything the team could do. It is a series of deliberate trade offs about where limited attention actually goes, made in full knowledge of what is being given up.

Which is why the most useful word in product strategy is often no, and why saying it is so hard. No can feel like a lack of ambition, like resistance, like telling a colleague their idea is not good enough. In practice the opposite is true. Michael Porter put it plainly years ago when he wrote that the essence of strategy is choosing what not to do. Saying no is how a team protects the one or two things it has decided matter most. It looks like declining a feature that serves a thin slice of users. It looks like delaying an attractive idea until there is evidence someone wants it, rather than a hunch that they might. It looks like refusing to copy a competitor move that never fitted your customer anyway. It looks like narrowing who you are for, instead of stretching to serve everyone and serving no one especially well. The people who do this best are not short of ideas. They refuse to let a good idea distract them from the most important one.

This is not a Silicon Valley luxury. It matters more in markets where capital is tighter and every wasted month costs something. Paystack spent roughly a decade doing one unglamorous thing, helping African businesses accept payments, before building much on top, and that narrowness is a large part of why it became infrastructure rather than a feature. African product leaders tend to talk about this instinctively. Chidi Afulezi has written about how building in Africa forces you to prioritise under real constraints, and Oluwatobi Otokiti, who trains product managers across the continent, treats prioritisation as the core craft rather than an afterthought. Constraint turns out to be a good teacher of focus.

None of this means every request should be rejected, or that simplicity is always right, or that customers never know what they need. Context and evidence still decide each case, and reasonable teams will disagree. But the strongest products I have seen were not the ones that did the most. They were the ones whose makers kept returning to a small set of questions. What matters most. What problem are we really solving. What will we choose, on purpose, not to build. Every product is a record of the decisions behind it, and the ones that last usually belong to teams with the discipline to say no far more often than they said yes. So it is worth asking, honestly, before the roadmap fills up again. If we could build only one thing that truly mattered to our customers, what would it be.

Arinze Chiama is a Nigerian Senior Product Designer and UX/UI Designer based in Abuja, with around a decade of experience in product design, user experience, and digital consulting. He has worked on web and mobile products across sectors including fintech, healthcare, legal services, education, and recruitment.