Shaping chaos to clarity. Making complex feel simple.

My design process

Listening before making.

1. Diagnostic

   Design serves a purpose, and it is rarely the one written in the brief. So the first step is listening — to users, watching what they actually do, not what they say in interviews. Mapping the real problem, the real constraints, the risks the brief did not name. That part is harder than any pixel decision that follows.

2. Prototypes & systems

   Design is a lived experience, not a screenshot. So before anything ships I build real interactive prototypes — clickable, edge cases included, the kind you can hand to a stakeholder and they get it without you in the room. Code and AI are part of the process now, not a separate phase: I prototype in the same tools the team will build with. What you see is what ships, give or take a sprint.

3. Scaling & sustainability

   Design must hold as the product grows. The unsexy part of the job: versioning the tokens, keeping the documentation alive, deciding who owns what, reacting fast when a new client type or platform shows up next quarter. A design system that nobody maintains might as well not exist — and most don't, which is the actual problem.