MY PROCESS
I don’t have a fixed process, and I’m a bit suspicious of anyone who does. Design is creative work, and every team and problem is different, so the way I work has to bend to fit. I’ve spent years in fast, sometimes chaotic teams, which taught me to move quickly without dropping the craft. I design for the user first and stay close to engineering, rather than throwing the work over the fence. Structure keeps me focused, but the skill that matters is knowing when to break it. It comes down to one thing: solving the right problem, and building something people actually want to use.
How I work
Champion the user
Every decision starts with the person on the other side of the screen. I get clear on what they’re actually trying to do, and on what’s quietly getting in their way.
Collaborate closely with dev
Design and engineering ship together, not over the wall. I prototype, pair, and pressure-test ideas against what’s actually buildable.
No fixed playbook
No two teams or problems are the same, so I don’t force a template onto them. I shape the approach to fit and keep moving without letting the craft slip.
Structure, then bend it
Structure keeps me focused. Knowing when to break it is the part that takes judgement, and it keeps the work aimed at the right problem instead of the process.
SKILLS
What I bring across the product lifecycle, from first insight to pixel-perfect, engineering-ready execution.
End-to-end product design
From data-driven discovery to pixel-perfect, engineering-ready UI, owned across the full journey.
Research & discovery
Turning messy, fuzzy problems into clear direction through structured research and synthesis.
Design systems & craft
WCAG-compliant systems and hands-on UI craft that engineers can ship without guesswork.
AI-assisted delivery
Using generative AI to research, prototype and build faster, from insight to shipped product.