Skip to content

How I work

The job of a designer has changed a lot. Here's how I actually work today: what I still do by hand, where AI does the heavy lifting, and the roles I step into when a product needs them. It's more about how I operate than any one project.

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.
How the work fits together
01
Design

UI, brand & the design systems that hold them together.

02
Code

Built in the real stack, nothing lost in handoff.

03
AI

Prototypes in hours, and systems that scale without me.

04
People

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.

contributions · last 12 monthsSep 2025 to Sep 2026
1232 contributions in the last yearLessMore

AI to move fast

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.

Claude Code · last 12 monthsSep 2025 to Sep 2026
Sessions
60
Messages
55,469
Total tokens
49.2M
Active days
41
Current streak
1d
Longest streak
8d
Peak hour
12 PM
Favorite model
claude-fable-5
LessMore

The everyday stack

These earn their place every week. Figma for design, Claude Code for shipping, and the stack this site runs on.

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.

Work with me

If that's the kind of designer your team or product needs, let's talk.