My UX Process
Discovery & Research
I start with posing the question: “How can user goals and business objectives co-exist to create the ideal experience?” Starting with this question provides value to every party involved in the project. In order to reach the answer to this question, I begin with conducting workshop sessions with stakeholders from every facet of the team, in order to flesh out project requirements. From then, depending on the timeline and constraints speaking with end users or doing a formal intake of a current product follows suit. From the intake process, insights are clustered, journeys are made and the next stage can begin.
Information Architecture
Once discovery has been conducted, the team understands our user and project requirements have been gathered, I jump into ideating solutions. This can come in many forms and vary in fidelity depending on the problem and project landscape. In the past, I’ve utilized card sorts and tree tests to inform wireframes. Having frequent check-ins with stakeholders allows them to understand how everything gathered from discovery is going to be represented. By focusing on getting the right information hierarchy, I am able to close the gap between this phase and the visual design phase, allowing for myself or another visual designer to elevate the design, as opposed to trying to interpret it.
Prototyping
When annotations and wireframes aren’t enough to get across intended interactions, I focus on building a prototype. My prototypes vary depending on budget, software used, and fidelity but the goal is always to create something that the team and I can use to gain a clear understanding of what the interactions and flow should be.
Usability Testing
In order to get the necessary insights that will help drive success for the project, usability testing is conducted. Moderated sessions allow the whole project team to get glimpses of a user’s mental model and their thoughts on the product - both experience and interface wise. I have conducted sessions in the past, been an observer and have taken notes for a moderator. Regardless of role, it is always so amazing to see someone use a product and tear it to shreds or highlight a good experience - each session gathers insights to enhance the final solution.
Documentation
Documentation is the final step before I hand off to other designers or developers. This final pass helps to clean up files, capture final interactions and make sure all team members involved are aligned on the intent of the product. Detailed documentation ensures a smooth and efficient handoff to ensure that the product is brought to life past visual design.
