
I'm a product designer and UX researcher who works where products actually break — the gap between what teams build and what people really do. My process starts in the field, not the conference room: watching real users in their real context, then designing the system that fits how they already think, rather than teaching them to think like the system.
Every project begins by questioning the brief. The stated problem is rarely the real one — a hearing app isn't about audio, it's about dignity; a research platform isn't about hierarchy, it's about the questions people ask. I read behavior in context, looking for the moment where my own assumptions turn out to be wrong. That moment is usually where the actual design begins.


I don't hand off static mockups and hope. I build working prototypes with real data, because a screenshot only tells you what people think they'll do — never what they actually do. Functional prototyping is how I run research, surface behavior, and earn the right to be surprised. The build isn't a separate phase after the thinking. It's how the thinking gets tested.
Real listening is rarer than designers admit. Mostly we hear the loudest stakeholder, the deadline, our own certainty. The discipline is watching someone use the thing you made and letting yourself be wrong about it. The best decisions I've made all came after being wrong about something. The worst came when I was sure.
