Strategy and craft aren't in tension — they reinforce each other. I work from outcomes back to decisions, own the full stack because every handoff loses something, and hold a craft bar high enough that users actually feel it. A few principles that shape how I work:
01
Know what you're moving.
Before starting, I want to know which metrics this work is meant to shift — support case volume, self-serve rate, time-to-resolve, activation, retention. Design decisions look different when you can trace them to outcomes. I stay close to the data before and after shipping.
02
Research that maps users to the business.
Good research isn't just about empathy — it's about translation. I dig into what users are actually trying to accomplish, then map those goals to business goals, then to experience goals. That chain is what separates a defensible design decision from an opinionated one.
03
Craft is the standard, not the finish line.
The quality of the details signals the quality of the thinking. Typography, hierarchy, interaction behavior, empty states, edge cases — these aren't polish, they're the product. I hold a high craft bar not because it looks good in a portfolio, but because users feel it and it builds trust.
04
Full-stack by default.
I run research, set strategy, define information architecture, design the interactions, and prototype in code when fidelity matters. Owning the full stack isn't about control — it's about compression. Every handoff is a place where context and craft get lost.
05
Systems that scale, shipped fast enough to matter.
Comprehensive systems and frameworks let you move quickly without losing coherence. I build the patterns early so iterations are additive, not corrective — then bias toward getting something real into the market, measuring what happens, and closing the loop.