My process
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.
Stakeholder & SME interviews · Domain and industry research · Risk and dependency mapping
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.
Problem statements · Design principles · MVP scope & priorities
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.
Entity & relationship maps · Information architecture · Journey maps & task flows
Wireframes to high fidelity, shaped by feedback from users and stakeholders where possible and pressure-tested with engineering. Progressive disclosure keeps dense screens calm. When engineering constraints or new edge cases surface, I loop back and adjust the structure rather than force the design.
Wireframes & prototypes · Usability testing · Hi-fi UI
I leave behind patterns and conventions, not just screens, and stay close to engineering through handoff and build.
Reusable patterns & components · Engineering handoff · Post-launch iteration