Understand the system
Before designing anything, I map the people, data, rules and constraints: stakeholder interviews, domain research, and time with the SMEs who know the real edge cases.
My process
Every project is different, but the shape is consistent. Each step links to where it happened in real work.
Before designing anything, I map the people, data, rules and constraints: stakeholder interviews, domain research, and time with the SMEs who know the real edge cases.
I turn what I’ve learned into a sharp problem statement and a small set of principles the team can use to settle debates later.
With complex products, the experience often succeeds or fails at the structure level. I work out entities, relationships, information architecture and flows before any pixels.
Wireframes to high fidelity, tested with real users and pressure-tested with engineering. Progressive disclosure keeps dense screens calm.
I leave behind patterns and conventions, not just screens, and stay close to engineering through build and rollout.