Process
Breaking down design problems
I have some standard process flows, but every project has its own unique needs and requirements. A great user experience means that you need to get to know the user. Ask questions. Learn users’ pain points and what delights them. Don’t take requirements as black-and-white solutions. Everything else in the UX process is just supporting this goal.
Research
No design is going to be successful if you don’t understand your audience. I use a combination of research methods to identify users’ issues and expectations.
Techniques include user observation, competitive analysis, heuristic evaluation, data analysis, user testing, and interviews. I work with a fantastic team of UX researchers who know a lot more than I do about curating the best research techniques for the situation and analyzing the results.
Define the problem
Once I understand the user’s pain points, the next step is to identify the issues we need to solve and the reasons why we want to solve them. This also creates a guidepost for the success of the project.
I hold sessions with the product owner, subject matter experts, business analysts, and developers to further understand their concerns and priorities.
Design and content
Next is the design process. It’s iterative, messy, and can get frustrating at times. The final set of deliverables depends on the project, but can include:
- User flows
- Personas
- Blueprinting
- Wireframes
- High-fidelity layouts
- Copy decks
- Prototypes
- Visual designs
- Design system components
Validate and implement
Testing the effectiveness of the designs is a continuous process throughout the project, from wireframes to final code. I work with the product, research, and development teams to gather feedback and iterate through the designs to ensure the product meets the needs of the user.
