Research to Solution
Product Design
Turning insights, user needs, and business goals into products people actually want to use.

The Kid Who Taught Me More Than Any Design Book
A few years ago, I was sitting in a music studio with a teenager who had been told most of his life that he wasn't trying hard enough.
Teachers thought he lacked focus. Adults thought he lacked discipline. Friends thought he lacked ambition.
The truth was simpler.
Nobody had taken the time to understand how he learned.
When we stopped trying to force him into someone else's system and started building around his strengths instead, something changed. Not overnight. But enough. Enough for him to believe in himself again.
I've thought about that moment many times since.
Because design is often the same story.
Most Problems Are Not Where They Appear To Be
People rarely struggle because they're lazy.
Users rarely struggle because they're incapable.
More often, they're struggling because something was designed without them in mind.
A confusing process. An unclear message. A system built around assumptions instead of reality.
The deeper I looked into UX and product design, the more I realised I had been solving similar problems long before I knew what UX was.
My Education Started Long Before UX
I've studied UX Design and Human-Centered Design, but I've also spent years studying people.
Through youth work, leadership development, group psychology, communication, conflict management, coaching and community engagement, I learned how people think, learn, collaborate and grow.
Through music production and songwriting, I learned creativity, iteration and the power of small details.
Those experiences continue to shape how I approach every project today.
Why I Design
I don't design because I love interfaces.
I design because I'm fascinated by people.
What makes someone trust. What makes them hesitate. What makes them stay. What makes them leave.
Technology changes constantly. Human behaviour doesn't.
Understanding people will always be more important than understanding software.
What I Hope To Build
The products I admire most are rarely the most complicated.
They're the ones that quietly remove obstacles.
The ones that make people feel capable.
The ones that reduce frustration and create confidence.
The ones that leave someone slightly better off than before.
That's the kind of work I want to create.
Not because it's impressive.
Because somewhere there's a person simply trying to make something work.
And they deserve an experience designed with them in mind.
