How I work

The short version

I'm a designer who doesn't stop at the mockup. I design the thing, build a lot of it, use AI to move fast, and step into product and team roles when that's what moves the work forward.

• Design, hands-on. UI, brand, and the design systems that keep them together.
• Design to code. I build in the real stack, so nothing gets lost in handoff.
• AI to move fast. Prototypes in hours, and systems that scale without me.
• The people side. Customers, stakeholders, and design teams.

Design, hands-on

The craft is still the core. I'm in Figma every day, doing interface design, brand, and design systems. That means tokens, components, and the rules that keep a product consistent as it grows. This part hasn't gone away. It's the base everything else builds on.

Design to code, no handoff

Mockups aren't the end of my job. I work in the product repos. I define tokens, shape component APIs, and write the components myself (web, iOS, Android, or Framer). When the same person designs it and ships it, nothing gets lost in translation. The design system is the real, running code, not a Figma library that drifts away from the product.

AI as leverage

AI changed how fast I can move and how much one person can hold. Two ways I lean on it:

• Prototypes in hours. I build clickable, real-feeling prototypes with AI tools and take them straight to customers, so people react to the real thing before engineering commits.
• Systems that extend themselves. I set up repos with machine-readable rules and AI agents that build new components on spec. They come out typed, tokenised, and on-brand, so the system stays consistent without me checking every change.

None of this is about novelty. It helps me ship more, keep quality high, and put my time into the hard parts instead of the repetitive ones.

The people side

Design isn't only the screen. Depending on what a product needs, I step into:

• Customer and stakeholder work. I take demos and prototypes to customers, gather feedback first-hand, and start those conversations myself instead of waiting for a brief.
• Design leadership.I've built and led a 20+ person design org. That covered structure, hiring, a fair career-leveling system, and the standards that keep quality high at scale.

I'm comfortable as the maker, and as the person who builds the function around the making.

What stays constant

Tools change fast. The approach doesn't. Show up, do the repetitive work well, and play the long game. It's the same discipline I bring to triathlon. Whatever the tool, the goal stays the same. A product that feels simple, stays consistent, and gets better over time.