It all started with a compiler error I couldn’t stop thinking about. I trained as an engineer, and spent the early part of my career building things that worked but that nobody enjoyed using. I could ship a feature and still feel like something was missing from it — I just didn’t have the vocabulary for what.
The turn came when I realised the bugs I cared most about weren’t in the code — they were in the experience. A confusing empty state. A form that asked for things it didn’t need. The kind of problem no test suite catches and no stack trace points at.
So I moved into product design — and kept the engineering. It means I design in systems, scope against what’s actually buildable, and can have the hard conversation with the people who have to ship it. Turns out “I know why that’s expensive” is a surprisingly useful thing to be able to say in a design review. 😉
Today I design products that get measured: CSAT scores, retention lifts, churn curves. And when I’m not doing that, I’m giving tools back to the community that taught me — because someone did that for me first.
- Figma
- Design systems
- Prototyping
- User research
- Usability testing
- SUS / PURE evaluation
- No-code
- Framer
Caught on camera: me trying to sound smart 🎥
A workshop where I (hopefully) made sense, shared some wisdom, and didn’t just ramble. Watch at your own risk.