Go where the user is
The insight is never in the dashboard alone. It is in a rider’s hand at a junction, or a trader’s ledger under a market awning. I get out of the office for it.

Hello,
I’m Maria Adebayo
Eighteen months across payments, lending and logistics — discovery through delivery. I start with the numbers, pressure-test them against real users, and write specs an engineering team can build from without a follow-up meeting.
Lagos, Nigeria
--:--WAT · UTC+1
I build
and everything
in between.
18months in product
Before product I did support, executive assistance and data entry — which means I spent a year reading complaints in the user’s own words and another learning where operational work actually breaks. Then analytics, then product. It is an unglamorous route and the best training I could have had.
Support → Analyst → Associate PM → PM.
04products shipped
Payments, SME credit, operations tooling, learning. Different industries, same job: find the thing that is quietly costing the business or the user something, prove it with numbers, and get a fix in front of people before the quarter turns.
Roughly 120,000 people use something I helped ship.
01demanding market
I build for intermittent connectivity, shared devices, metered data and users with no patience for friction. Products that hold up under those conditions tend to feel effortless everywhere else — it is the most useful design constraint I have worked with.
Based in Lagos. Open to remote and to relocating.
03How I work
Not a framework. Just how I actually work, learned mostly by getting it wrong first.
The insight is never in the dashboard alone. It is in a rider’s hand at a junction, or a trader’s ledger under a market awning. I get out of the office for it.
I came up through analytics, so I open with what the data says and follow it with what it means. Opinions are cheaper when they arrive second.
A flag on 10% of users for three weeks beats a perfect launch nobody can reverse. I would rather be wrong cheaply and early.
Intermittent connectivity, shared devices, metered data. Designing for the hardest conditions first makes the product better for everyone on the easy ones.
Half of this job is being unambiguous in writing. If an engineer has to ask me what a spec means, the spec was the problem, not the engineer.
I ask the obvious question in the room everyone else is too senior to ask. It has saved us more than once, and I have no plans to grow out of it.