Playground

  • Read case study

    Pulse Board

    Product design

    Read case study
  • Read case study

    Ledger Lite

    Design system

    Read case study
  • Read case study

    Viz Studio

    Brand and product

    Read case study

Craft is a tool for building an advantage

In my approach, design and engineering are the foundation of how a product earns trust — not separate stages, but one practice.

I believe good craft does more than polish an interface. It decides what the product is actually for and whether it reaches the people it was meant to help, in the visuals, in the words, and mostly in the small details nobody notices until you ship.

That’s the job I call design engineering. I stay in it from the first product decision through interaction design to the code that ships it, so the experience still holds together once the product grows past the parts I can hold in my head.

Principles that shape how the work gets made

  1. Experimentation over convention

    I push on established norms to find better ways of thinking and making. Progress usually lives in the uncomfortable space between certainty and discovery — where assumptions break and better answers show up.

  2. Intuition over process

    I trust experience, judgement, and creative instinct over rigid frameworks. Process can support the work, but it shouldn’t run it.

  3. Compasses over maps

    I design with direction, not fixed destinations. Principles help me move through complexity where frameworks can’t. The path tends to reveal itself when I’m moving, not when I’m planning.

  4. Systems over objects

    I care more about relationships, rules, and structure than singular artifacts. Good systems create consistency without boxing expression in.

  5. Intelligence over automation

    I use AI to expand what’s possible, not replace what matters. The tools speed up execution — my judgement still shapes the outcome.

Where the hours go

A rough map of the last 30 days on my machine — which apps held my attention, and for how long. It can’t tell a focused afternoon from a rabbit hole, but the hours still count.

Cursor4 days, 6 hours, 12 minutes
Figma3 days, 14 hours, 28 minutes
Claude1 day, 9 hours, 41 minutes
Linear18h, 22m
Slack11h, 8m
Dia9h, 14m
Paper4h, 36m

When I’m not making something myself, I’m usually reading, listening, or keeping track of work other people made that I don’t want to lose — then bringing pieces of that back into the craft.

A working mix of craft

How I tend to show up across design and engineering — not a scorecard, more a shape of the practice. Switch profiles to see where the weight shifts.

Me skill profile

Notes from the making

Essays and notes on systems, shipping, and how products get their shape — thinking that sits beside the product, not after it. These three are on the way.

  • What making looks like when AI is in the loopSoonComing soon
  • Design systems that survive contact with productionSoonComing soon
  • Notes on shipping taste at the speed of codeSoonComing soon

since you made it all the way down here, you might as well linger over a few [photos] I took