People often assume a product designer's job is to make things look nice, choose good colours, pick a clean font, arrange things neatly on a screen. That is a small part of it. The real job is making sure a person who has never used your product before can open it, understand what it wants from them, and complete what they came to do, without needing anyone to explain it to them first. In a country as varied as Nigeria, where users range from a university student on a new iPhone to a trader on an older Android with limited data literacy, that is a genuinely difficult problem, and it has almost nothing to do with how pretty a screen looks.
Colour is not decoration here, it is communication
In fintech and crypto products especially, colour carries real meaning that users read instinctively. Green tends to signal money moving in or a successful action. Red signals danger, a failed transaction, or something that needs urgent attention. Using those colours carelessly, or inconsistently across a product, quietly erodes a user's ability to trust their own eyes. We treat colour choices as functional decisions with real consequences, not just brand preferences, especially anywhere money or security is involved.
We design the confusing moments, not just the pretty ones
The screens that matter most in a design file are rarely the beautiful landing page. They are the moment a transaction fails, the moment a user has to wait for something to process, the empty screen a new user sees before they have any data yet. These are the moments people are most anxious, and most likely to give up entirely. We spend deliberate time designing exactly what a user sees and is told in those uncomfortable moments, because a product that handles its worst moments gracefully earns far more trust than one that only looks good when everything is going right.
"If a design only makes sense to the person who made it, it is not finished yet. It is just familiar to them."
We test with real Nigerian users before engineering starts
Before a single screen goes to the engineering team, we put early versions in front of people who match the actual target audience, not colleagues who already understand the product's logic. Watching someone hesitate over a button, misread a label, or tap the wrong thing entirely tells us more in ten minutes than a week of internal debate about what looks better. It is humbling, occasionally, to watch a design you were proud of confuse someone completely. It is also the fastest, cheapest way to fix a problem, before it has been coded, tested, and shipped to thousands of people.
Good design and good engineering are the same conversation
None of this works if design happens in isolation and hands a finished file to engineering with no further discussion. The best products come out of design and frontend engineering treating each screen as a shared problem, not a handoff. When a design decision would be expensive or slow to build well, we want to know that before it is finalised, not after. That close collaboration is, honestly, the real definition of good product design in this market: not how a screen looks in isolation, but how well it actually serves the person using it, on their phone, on their network, in their own everyday life.