A clear path.
Room to iterate.
From understanding the problem to refining the experience: how I approach UI/UX design.
The process adapts to the project. Research access, scope, and timelines shape the methods—and new findings can take the work back to an earlier stage.
Discover
Understand people and context.
Start by understanding the people using the product, the problem they need to solve, and the business constraints. Review the existing experience and comparable products, then use interviews or observation where access allows.
Questions to answer
Who is this for? What are they trying to do? Where does the current experience create friction?
Useful outputs
Research notes, key user needs, a picture of the current journey, and a list of assumptions to investigate.
Define
Turn insights into a focused problem.
Bring the findings together, identify the most important pain points, and agree on the task the design should improve. Map the user flow and information structure before investing in detailed screens.
Questions to answer
What should we prioritize? What constraints matter? How will we know the experience has improved?
Useful outputs
A problem statement, prioritized requirements, user flows, and a clear scope for the first solution.
Design
Make the solution tangible.
Explore structure through wireframes, then develop visual hierarchy, components, and interaction states. Build a prototype that makes the key journey concrete enough to discuss and test.
Questions to answer
Is the next action clear? Does the hierarchy support the task? What happens when content is empty, loading, or something goes wrong?
Useful outputs
Wireframes, interface designs, reusable components, and an interactive prototype.
Validate
Test, refine, and hand off.
Use task-based feedback to identify confusion and refine the experience. Collaborate with the product team on behavior, responsive layouts, and component states, then review the implementation against the intended design.
Questions to answer
Can people complete the task? Where do they hesitate? What should change before release, and what needs further learning?
Useful outputs
Usability findings, revised designs, implementation notes, and a prioritized list of next improvements.