About Me
A little about how I see design.
I'm a Product Designer interested in the relationship between people, problems, and the digital experiences we create to bring them together.
My work is rooted in understanding user needs, making complex workflows easier to navigate, and translating requirements into clear, usable interfaces. I care about how a product looks, but even more about whether it makes sense to the person using it.
I also bring a broader product perspective to design. Understanding requirements, constraints, priorities, and delivery helps me make decisions that consider both the user experience and the realities of building a product.
My journey
From understanding the problem to shaping the experience.
My approach to design begins with questions. Who is the user? What are they trying to achieve? What makes the task difficult today? And what does a better experience need to make possible?
From there, I work through the structure of the experience, the decisions a user needs to make, and the interactions that help them move forward. I pay attention to the details that are easy to overlook, especially error states, permissions, unusual scenarios, and moments where the system needs to explain what is happening.
Working alongside product and engineering teams has also reinforced an important part of my design practice: a good solution needs to work for the user and make sense within the product's technical and operational context.
Where I've worked
Where I've contributed.
Every organization brings its own users, constraints, and challenges. My professional experience has given me opportunities to contribute to digital products and collaborate with people across the product development process.
Seamfix
L&L Africa Wanderlust
Stutern Graduate Accelerator
My design principles
What guides my design decisions.
- 01.
Start with the user
I want to understand the need behind the request, not just the screen someone has asked for. That understanding helps me evaluate whether a proposed solution actually addresses the problem.
- 02.
Make complexity easier to navigate
Complex products do not have to create confusing experiences. Clear hierarchy, predictable interactions, useful feedback, and thoughtful workflows can help users understand what to do next.
- 03.
Consider the details
The experience includes more than the ideal path. I think through validation, errors, permissions, empty states, loading states, and other scenarios that affect how a product behaves in practice.
- 04.
Design with the team
Good design needs collaboration. Working with product, engineering, and QA helps clarify constraints, align expectations, and ensure that the intended experience is understood beyond the design file.
The work tells the rest of the story.
Explore the work I've contributed to, take a look at the products I'm building independently, or get in touch to discuss a design opportunity.