Design leader who makes good work actually ship

I work at the edges: where design meets product, where product meets engineering, where someone has to push the whole thing forward.

My Approach

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 and map the system. The one thing that actually matters usually becomes clear from there.

02

I work on both sides of the design-engineering line

I'm in the codebase. I write specs engineers can build from and ask questions that show I understand the constraints. That earns trust. And trust changes 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 I've stopped trying.