My Design Process
Solve the right problem, then make it feel obvious.
My process adapts to the project, team, and product maturity. The order shifts, the depth changes, but the intent stays the same: understand the problem, design with care, and ship with confidence.
Understand the problem
Talk to stakeholders. Make sure the brief is the real brief.
Define users and business goals
Who is this for? What are we trying to move?
Research and gather insights
Interviews, UX reviews, lightweight surveys, support data.
Map workflows and pain points
Walk the journey. Find where it breaks.
Ideate possible solutions
Sketches, parallel directions, internal critique.
Wireframe and prototype
Lo-fi and hi-fi, real enough to react to.
Test with users and stakeholders
Usability sessions, A/B tests, honest feedback.
Refine the design
Tighten copy, spacing, motion. Cut anything that doesn't earn its place.
Handoff to development
Design system tokens, annotated specs, accessibility notes.
Measure and improve
Watch the data, listen to support, and keep shipping.
Methods I lean on
A small, sharp toolkit.
A small note
"My process changes based on the project, timeline, team, and product maturity. I focus on solving the right problem — not just creating polished screens."