THE PROCESS
One process, wherever I plug in.
I'm a solo product designer. I can sit inside your company like a senior hire, in your tools and your standups, or take a whole product independently from the first call to launch. Either way the work is the same: research, direction, identity, UX and UI, then hands-on support through build and release. The six stages below are how I move any project from discovery to live, on a team or on my own.
01 / COLLECT
First, I learn the people and the business.
Interviews, the analytics you already have, a hard look at the competition, and support tickets nobody has read in months. On their own these are scattered signals. They only start to matter once they live in one place and point the same way.
02 / MAP
Then the noise has to become a shape.
Synthesis used to mean days of tagging notes by hand across scattered files. Now I pull the research into one place and let the patterns surface, so I reach the real problem sooner and spend the hours I save on judgment instead of busywork.
03 / JOURNEYS
I follow one real person, step by step.
Not the tidy flow from the whiteboard. The path someone actually takes, with the friction, the second-guessing, and the moment they almost walk away.
04 / PROBLEMS
I leave with a sharp problem, not a wishlist.
The drop-off in the journey, the ticket that keeps coming back, the metric that will not move. They usually point at the same few things. Those are what I name here.
05 / PRIORITIZE
Not everything ships at once.
Some of the work is high impact and cheap to do. Some is the right call and still has to wait. I would rather be honest about that early than pretend the whole list launches together.
06 / FILTER
I explore more directions than I need, on purpose.
Exploring used to be slow, so I would commit to one idea early. Now I can put several credible directions on the table and let most of them go, which makes the final call sharper because it holds up against real alternatives.
07 / DESIGN x AI
This is where the tools earn their place.
Type, colour, grid, motion, and the components that make everything downstream feel like one product.
Flows, wireframes, and the finished screens, edge cases and empty states included.
08 / FINALE
From a flat file to something you can feel.
I stay close through build, prototyping in real code where it helps, so what ships stays true to what was designed. Then I watch how it behaves for real people and fold what I learn back in.
The design-to-code loop is where the tools changed my work the most. I can prototype in real code, catch where an idea breaks in practice, and give engineers something far closer to the real thing than a static file to interpret.
WHAT STAYS HUMAN
The tools got faster. The decisions are still mine.
Everything you just scrolled through was built the way I would build your product: AI doing the heavy lifting, and a human refusing to ship the almost-right version. If you are making something real, I want to hear about it.
If you have something worth making, start a conversation. Contact