Engineer. Designer. Both.

I've built
things

my whole
life.

01 / Story

I've built things my whole life — starting with Lego as a kid, which taught me how pieces fit together, how systems work, how to solve problems by understanding what you're building before you start.

Now I design everything that catches my curiosity — hardware, enterprise systems, web experiences. The medium changes, but my approach doesn't. I always start with why…

…I'm not an engineer who designs on the side, or a designer who codes. I'm someone who thinks about problems whole, who asks why before building anything.

02 / Beliefs

  1. Start with why.

    Why does this need to exist? What problem are we solving? What should it feel like? I ask before I build anything — the answers shape everything I make.

  2. Understand, then build.

    Most problems aren't solved by the fanciest technology or the prettiest design. They're solved by understanding how something actually works — the workflow, the constraints, the human side. Once you see that clearly, the solution becomes obvious.

  3. Intention outlasts trends.

    Business fundamentals don't change; technology does. Trends fade, but intention endures — so I build for the reason a thing exists, not for the moment it ships.

  4. Good enough isn't.

    Good enough is usually not enough. I give the details that matter — typography, motion, color, how something feels — the same time as the workflows and constraints underneath them.

  5. One piece at a time.

    The way this computer was built: from the pieces at hand, one at a time, each one considered before it's placed. Not just the parts you see, but the ones underneath that complete the build.

  6. Think whole.

    I'm not an engineer who designs on the side, or a designer who codes. Whether it's a system for a Fortune 500 company or the motion in an interface, the rigor is the same.

03 / What I do

  • Product Design
  • Enterprise Systems
  • Web Experiences
  • Motion & Interaction
  • Hardware