Approach
These are the principles I've built and refined over 20 years of shipping product. They're not abstract values — they're how I actually make decisions about quality, users, and systems.
1. Quality is a strategy.
I treat quality as a competitive advantage, not a luxury that ships when there's time. When a plan is too big, I cut scope — not craft. A smaller thing done well always beats a bigger thing done halfway, and quality compounds: it builds trust, reduces rework, and creates momentum.
2. Start from the job, not the feature.
I begin with what people are actually trying to do — their workflow, their friction, their definition of success. Features follow from that understanding, not the other way around. If you can't describe the user's problem without naming your solution, you haven't done the work yet.
3. Be opinionated early.
I'd rather make a bet and learn from it than wait for perfect information that never comes. Strong opinions, loosely held. Name your assumptions, test them, and change your mind when the evidence says to. Ambiguity doesn't resolve itself — decisions do.
4. Data informs, it doesn't decide.
Research and metrics are inputs, not answers. I use them to sharpen judgment, not outsource it. The most important questions in design — is this clear? is this worth building? — rarely have a dashboard waiting.
5. Design is systems and storytelling.
Great products feel coherent. That coherence comes from thinking in systems — not just screens — and owning the narrative that ties them together. I design the information structure, the naming, the handoffs, and the story that makes it all make sense to everyone in the room.
6. Think big, build small.
Set a clear direction, then ship in smaller steps that create learning and momentum. Progress comes through reps, not grand reveals. Every iteration should teach you something and move the work forward.