The foundations of my design process
“I keep my process simple: turn complex problems into products that are genuinely understandable, functional, and easy to use.”
Digital product design isn’t one discipline; it’s the intersection of three. Making sense of what exists, shaping how it’s navigated, and building what people actually touch. I work across all three, and it’s in their overlap that the judgment defining a product really lives.
Information Design
Before anything looks good, it has to make sense. I work on the architecture of information: what gets shown, in what order, with what hierarchy, and under what logic. It’s the least visible part of the process and, almost always, the one that decides whether a product is understood or abandoned.
I model content, navigation structures, and naming systems built to survive growth. I translate complexity (dense data, heavily branched flows, unforgiving business rules) into clear structures a person can move through without conscious effort. When this layer works, nobody notices it. That’s exactly the point.
Experience Design
Here I move from structure to journey. I design how a product is traversed: entry points, the decisions it asks for, the friction worth removing and the friction worth keeping. Every screen exists in relation to the one before it and to what the person is actually trying to get done.
I work from research and from the real context of use, not the ideal one, to define flows, states, edge cases, and critical moments. I prototype, validate, correct. The goal isn’t an experience that impresses; it’s one that feels inevitable, where the next action always looks like the obvious one.
User Interface Design
This is the layer you touch. Here the system becomes tangible: type, scale, color, rhythm, motion, behavior. I design interfaces where every decision is deliberate, because details are what carry precision, confidence, and character.
My technical background in frontend development shapes how I approach this layer: I design component systems meant to be built, not just presented. Tokens, states, variants, and documentation that live the same way in the design file and in the codebase. That removes the translation step between teams and makes what gets approved, quite literally, what ships.