PROCESS / PRINCIPLES IN PRACTICE

Good design is a
series of good decisions.

My working approach balances user needs, product constraints and implementation realities. The process flexes to the problem rather than forcing every project through a rigid template.

01

UNDERSTAND

Get close to the problem.

Align on the business goal, user context, known constraints and what is still uncertain. Separate evidence from assumptions so the team knows what needs validation.

Stakeholder alignmentResearch planningProblem framingSuccess criteria
USEFUL OUTPUTSProblem statementResearch questionsOpportunity areas
02

STRUCTURE

Make the workflow make sense.

Organize information around user tasks. Map key journeys, content hierarchy, edge cases and the decisions a user needs to make at each step.

User journeysInformation architectureTask flowsWireframes
USEFUL OUTPUTSJourney mapNavigation modelLow-fidelity flows
03

EXPLORE & TEST

Prototype to learn, not just to impress.

Explore alternative solutions, test important assumptions early and refine the interface based on observed friction and feedback.

Interactive prototypesUsability testingIterationAccessibility checks
USEFUL OUTPUTSClickable prototypeTest observationsPrioritized changes
04

SYSTEMIZE & DELIVER

Design for the real world.

Build reusable components, specify empty and error states, account for responsive breakpoints and partner with engineering through implementation.

Design systemsResponsive UIDeveloper handoffQA collaboration
USEFUL OUTPUTSComponent libraryResponsive specsHandoff notes

QUALITY CHECKLIST

Details are part of
the experience.

CHECK 01

Accessibility

Readable contrast, focus visibility, semantic structure and keyboard access.

CHECK 02

Responsive

Useful layouts from small screens to wide desktop viewports.

CHECK 03

States

Loading, empty, success, validation and error states are considered.

CHECK 04

Consistency

Shared components, tokens and interaction patterns reduce surprises.