Selected Work
Selected Work
Selected Work
Work I'm proud of (and would do again)
Work I'm proud of (and would do again)
Sole Product Designer
Scope: Mobile app, web, admin, design systems
Lead Product Designer (Sole Designer)
Scope: Mobile app, web, admin, design system
Impact
Improved app rating from 3.6 to 4.8
Multi-market research
Stronger trust & security with PINs and biometrics advocacy
Stronger trust & security with PINs and biometrics advocacy
Design system adoption and enforcement
Better onboarding & KYC completion
Weekly metrics ownership tracked and acted on
UX Designer
Scope: Consumer apps, merchant tools, internal platforms
Product Designer
Scope: Consumer apps, merchant tools, internal platforms
Impact
Internal search platform that saves $75k+/year (0 → 1)
Revenue uplift from improved checkout & KongaNow UX
Merchant Inventory management tool design (0 → 1)
Merchant inventory management tool design (0 → 1)
Affiliate portal redesign
KongaPay website redesign
Improved usability across web & mobile surfaces
Seller HQ redesign
Side project for Josplay
Scope: Discovery, structure, and access
What I explored
User needs & mental models
Information architecture
Low-fidelity flows for discovery and cataloging
Side project
Scope: Discovery, structure, and access
Design Process
Design Process
Design Process
It is a loop, not a line. Each phase changes what I believe about the last one.
It is a loop, not a line. Each phase changes what I believe about the last one.
- 01
Question the brief
The request is almost always “redesign this screen”. The job is working out what is actually failing. At Afriex that reframe turned a visual refresh into three years of reducing uncertainty at the moments money moves.
The stated problem · business goals · existing flows · what support keeps hearing
- 02
Find the pattern under the symptoms
People rarely describe the real problem. I look for the workaround they built, because that is the honest brief. Research across six markets said the product worked but never reassured anyone.
Where AI helps. I cluster research notes and support tickets quickly to see where the weight sits, then verify by hand. A cluster is a starting point, never a finding.
Interviews · analytics · support tickets · the spreadsheet they built to cope
- 03
Decide, and name the trade-off
Every decision costs something. I write down what I gave up and why before I draw the screen. A PIN at confirmation is friction; it was the right friction, and the completion rate held.
Where AI helps. AI-assisted prototyping gets a concept to something testable in hours, so the conversation is about a working thing rather than a description of one.
Flows · entity models · wireframes · prototypes
- 04
Test the thinking, not the pixels
A prototype exists to be wrong early. It goes in front of users, engineers, and whoever owns the risk, so I change my mind on paper instead of in production.
Usability sessions · stakeholder review · edge cases · engineering constraints
- 05
Ship it properly
Handoff is not the end of design. I run structured design QA against the build, because what users get is what counts, not what is in the file.
Engineering partnership · design QA · failure states · release checks
- 06
Watch it, then systemise it
I owned product metrics weekly, not quarterly. When the same problem turns up twice it stops being a screen and becomes a pattern, a system, or a process that outlives me.
Activation and completion · drop-off · NPS · support volume · design system
then it starts again, with better evidence
- 01
Question the brief
The request is almost always “redesign this screen”. The job is working out what is actually failing. At Afriex that reframe turned a visual refresh into three years of reducing uncertainty at the moments money moves.
The stated problem · business goals · existing flows · what support keeps hearing
- 02
Find the pattern under the symptoms
People rarely describe the real problem. I look for the workaround they built, because that is the honest brief. Research across six markets said the product worked but never reassured anyone.
Where AI helps. I cluster research notes and support tickets quickly to see where the weight sits, then verify by hand. A cluster is a starting point, never a finding.
Interviews · analytics · support tickets · the spreadsheet they built to cope
- 03
Decide, and name the trade-off
Every decision costs something. I write down what I gave up and why before I draw the screen. A PIN at confirmation is friction; it was the right friction, and the completion rate held.
Where AI helps. AI-assisted prototyping gets a concept to something testable in hours, so the conversation is about a working thing rather than a description of one.
Flows · entity models · wireframes · prototypes
- 04
Test the thinking, not the pixels
A prototype exists to be wrong early. It goes in front of users, engineers, and whoever owns the risk, so I change my mind on paper instead of in production.
Usability sessions · stakeholder review · edge cases · engineering constraints
- 05
Ship it properly
Handoff is not the end of design. I run structured design QA against the build, because what users get is what counts, not what is in the file.
Engineering partnership · design QA · failure states · release checks
- 06
Watch it, then systemise it
I owned product metrics weekly, not quarterly. When the same problem turns up twice it stops being a screen and becomes a pattern, a system, or a process that outlives me.
Activation and completion · drop-off · NPS · support volume · design system
then it starts again, with better evidence
- 01
Question the brief
The request is almost always “redesign this screen”. The job is working out what is actually failing. At Afriex that reframe turned a visual refresh into three years of reducing uncertainty at the moments money moves.
The stated problem · business goals · existing flows · what support keeps hearing
- 02
Find the pattern under the symptoms
People rarely describe the real problem. I look for the workaround they built, because that is the honest brief. Research across six markets said the product worked but never reassured anyone.
Where AI helps. I cluster research notes and support tickets quickly to see where the weight sits, then verify by hand. A cluster is a starting point, never a finding.
Interviews · analytics · support tickets · the spreadsheet they built to cope
- 03
Decide, and name the trade-off
Every decision costs something. I write down what I gave up and why before I draw the screen. A PIN at confirmation is friction; it was the right friction, and the completion rate held.
Where AI helps. AI-assisted prototyping gets a concept to something testable in hours, so the conversation is about a working thing rather than a description of one.
Flows · entity models · wireframes · prototypes
- 04
Test the thinking, not the pixels
A prototype exists to be wrong early. It goes in front of users, engineers, and whoever owns the risk, so I change my mind on paper instead of in production.
Usability sessions · stakeholder review · edge cases · engineering constraints
- 05
Ship it properly
Handoff is not the end of design. I run structured design QA against the build, because what users get is what counts, not what is in the file.
Engineering partnership · design QA · failure states · release checks
- 06
Watch it, then systemise it
I owned product metrics weekly, not quarterly. When the same problem turns up twice it stops being a screen and becomes a pattern, a system, or a process that outlives me.
Activation and completion · drop-off · NPS · support volume · design system
then it starts again, with better evidence
Open to senior product design roles. Full-time remote or contract. Available now. Can be hired directly, as a contractor, or through an employer of record such as Deel or Oyster.
Lagos, Nigeria (UTC+1). Full overlap with UK and EU hours, 4+ hours with US Eastern. Experienced with distributed teams across Africa, Europe and North America.
Chinonye Onuoha · Product Designer
Open to senior product design roles. Full-time remote or contract. Available now. Can be hired directly, as a contractor, or through an employer of record such as Deel
or Oyster.
Lagos, Nigeria (UTC+1). Full overlap with UK and EU hours, 4+ hours with US Eastern. Experienced with distributed teams across Africa, Europe and North America.
Chinonye Onuoha · Product Designer