It started under a table.
As a child, I would sit under the table with my sister’s quantitative reasoning books, colouring the white spaces in illustrations of animals. In my mind, I wasn’t just colouring. I genuinely believed I was completing something the illustrator had left unfinished.
Looking back, I find that funny. But I also recognise something about myself that hasn’t changed: I’ve always been fascinated by what something could become, not just what it already is.
As I grew older, that curiosity became a whole world inside my head. I could imagine interfaces, interactions and experiences that didn’t exist — sometimes visualising an entire solution before knowing how it would be built, and sometimes imagining things the available technology simply couldn’t support.
Sometimes the imagination arrives before the technology.
Over the years I’ve designed concepts that were technically possible but difficult to implement, and others that were simply ahead of the tools available at the time. Some ideas had to be simplified. Others had to wait.
Watching AI and modern development tools make those interactions achievable has been genuinely interesting. But experience taught me something more useful: just because I can imagine something doesn’t mean someone needs it. That’s where research, collaboration and product thinking come in.
I still love exploring what could be possible. I’ve just become much more interested in what should actually be built.
Learning to think beyond the screen.
My career has taken me through banking, government services, healthcare, fintech, emerging technology and consumer products. I’ve worked on products where a single interaction could affect someone’s money, their access to a public service, or their ability to care for a family member.
A screen is rarely the whole problem. Behind it are people, processes, business rules, technical limitations and decisions that all have to work together. In healthcare that means cognition, accessibility, physical ability, caregivers and clinicians. In government services it means regulation, legacy process and multiple user roles. In financial products it means turning unfamiliar technical concepts into workflows people can follow.
That’s why my work extends beyond visual design into product strategy, research, information architecture, design systems, prototyping and implementation. I enjoy working with engineers, understanding how systems operate, and making a complicated experience feel surprisingly simple.
Building things keeps me curious.
One of the best ways I’ve learned is by building my own products. MuviDB is one of them. What began as a simple question about discovering African films became a much larger challenge involving filmographies, credits, streaming availability, cinema listings, reviews, data architecture and automation.
It has pushed me into decisions I wouldn’t encounter by designing screens alone: infrastructure, operating costs, data quality, APIs and what happens after a product goes live. Before it there was NaijaWatts, for making shared electricity costs easier to calculate, and an open-source collection of African fintech brand assets.
Building something yourself makes one thing obvious: designing something and keeping it running are two very different challenges. I enjoy both.
Read the case study ↗What keeps me going.
I don’t think I’ll ever stop imagining things. There will always be another problem to untangle, another interaction to question, or another idea that seems impossible until someone finds a way to make it work.
What has changed is my relationship with those ideas. I’m less interested in designing something because it’s impressive, and more interested in whether it makes someone’s life easier, gives them clarity, or solves a problem they’ve learned to live with.
What I’m looking for.
Senior product design roles where I can help shape products from the early questions through to implementation, working with people who enjoy solving complex problems. I’m particularly drawn to teams where design contributes to product direction, not just the final interface — Staff, Principal and Senior roles, design systems work, and the space between design and implementation.
And I still want to work on the occasional idea that feels a little ahead of its time.
Let’s talk ↗