How I Work
Process, collaboration model, and the principles behind design decisions for complex operational systems.
Process
Not a linear pipeline. These phases overlap. Validation regularly sends the work back to understanding, and shaping sometimes reveals the problem was framed wrong. The sequence reflects how the work actually moves, not a methodology to follow.
Collaboration
Principles
Evidence over intuition
I build the case before I defend the decision. Quantitative data and domain research carry more weight than design preference.
Domain depth over surface polish
Understanding how the work actually gets done produces better interfaces than following UI trends.
Honest testing over confirmation bias
The goal of testing is to find problems. Independent validation, structured defect classification, questions that challenge assumptions.
Clarity over cleverness
Especially where mistakes have real consequences. Clear states, predictable interactions, language that matches how users think.
Where I’m Heading
Product Designer transitioning into Design Technologist
The work I do sits at the intersection of complex systems and human behavior. Increasingly, the gap between a design and a working interface is where the real problems live. Static mockups fall short when you’re designing for algorithmic states, edge cases in operational workflows, and UI behavior that depends on data the algorithm produces.
I now design and prototype directly in code using a component-based, Storybook-driven workflow, which has made engineering collaboration significantly tighter, particularly when specifying states, transitions, and system feedback in interfaces where getting it wrong has real consequences.