Outside of design, I'm two months into judo as a white belt - currently at the getting-thrown-a-lot stage of learning something from scratch. I also try to make it to as many UX Crunch talks as I can, usually writing up a reflection afterward - partly to make the ideas stick, partly because writing in public is its own kind of practice.

I work best on ambiguous problems - data that doesn't have a clear story yet, or requirements shaped by conflicting stakeholder needs. My process starts with research and ends with evidence: I'd rather validate a direction through testing and prototypes than argue for it on instinct. I default to owning scope end-to-end, from framing the problem to shipping the solution, particularly in small teams where that ownership matters most.

• Works with engineers from early discovery through implementation, not just at handoff
• Frames success with a primary metric, a counter-metric, and a guardrail - not just a single number in isolation
• Documents rationale alongside outcomes: rejected directions and the reasoning behind each, not just the final design
• Currently deepening design systems fundamentals - token architecture, component libraries, and documentation