My way of work
01
I start with what's broken
Before opening Figma, I audit what exists. Most problems aren't where people think they are. I come to stakeholder meetings with a point of view already formed — not to impose it, but to have a real conversation.
02
I look outside my domain
Some of my best decisions on HR products came from fintech, healthcare, and consumer apps. I actively seek references outside my field — for interaction patterns and mental models I can adapt to a different context.
03
I build my case with data
I run 5 to 8 user interviews per discovery phase. I cross-reference qualitative findings with product analytics. When I push back on a PM, I do it with evidence.
04
I design for the whole product
I run 5 to 8 user interviews per discovery phase. I cross-reference qualitative findings with product analytics. When I push back on a PM, I do it with evidence.
05
I stay involved until it ships
Research · audit · exploration · flows · UI · testing · dev handoff · QA. The gap between a design file and a shipped product is where quality gets lost — I try to close that gap.
06
I write handoffs developers don't have to guess
I document all interface states, edge cases, and responsive rules. On complex projects, I produce motion specs and prototype animations with Claude or Figma Make — delivering an interactive reference instead of a text description.
07
I ask if AI earns its place
Before designing any AI feature, I ask: does this remove a real burden? Can the user trust the output? What does it cost — for the user, and for the business? If the answers aren't clear, I go back to the problem.