I design products.
I think in systems.

My title has always been in design, but my thinking has never stayed there. My strongest work is at the leadership level. Building the function, shaping the direction, staying close enough to know when something's off.

How I Approach Work

Good design isn't just how something looks. It's how well you understood the problem before you touched a tool.


01

I break things down until they're clear

When a problem feels overwhelming, that's usually a signal the framing is wrong. I slow down, map the system, and find the one thing that actually matters. That clarity tends to unblock everyone around me too.

02

I stay in the room with engineers

I've spent enough time in codebases and sprint reviews to understand how engineers think. I write specs they can actually use, and I ask questions that don't waste their time. That trust makes a real difference in what ships.

03

Every detail has a downstream effect

A small UX decision can create a data modeling problem. A component choice can constrain a product decision six months later. I try to hold that context while still moving fast. If something's wrong, I'd rather raise it before it becomes a rebuild.

04

I think at the product level

Design decisions are product decisions. I've never been able to treat them as separate jobs, and the work is better for it. Design is where I work. Product is how I think.