Work Experience In Practice

The strategy, analytics, research and experience design behind how I approach building problem-solving solutions.

My Process

Kickoff Process + Workflow

Over the years, working on projects in various industries, the beginning of each project starts with getting an understanding to define the ask. What are we doing? Why do we want to? How will this better the product for both the business and the user? To drill down, this may include hosting Discovery studios or Design Thinking Workshops to help flush out details and set expectations on the approach between design teams, the Product team, and the stakeholder. Ultimately the goal is to define the intent and set expectations.

Get Clarity

Building a complete picture begins with gathering information and understanding the "what, why, and how" to start the process—collecting the necessary details such as research materials, marketing analysis, data structures, and information architecture forms the foundation to build on. This information also informs what UX practice and tools may be necessary to generate the North Star, a point used to drive direction and focus efforts.

Work the Plan

Working on the plan is taking all the gathered information and after careful study apply UX processes to refine and define what the next steps will be. This includes with every project building a living user flow mapping of the ask. It may also include if necessary building data flow mapping, user journey, or service blueprints to further clarify the ask. At each step review with stakeholders communicating as often as possible to reassure is still following the initial intent, the projects North Star.

Design, Visuals + Functionality

The process of defining the ask works to cut down on one of the most detrimental mistakes that take place when approaching a solution—jumping into the visual design too early, which can derail a project, causing confusion, time, and money. Whether it is building, journey maps, or service blueprints to inform what we are making and how the next step begins with defining with wireframes and prototypes to display the intent visually, getting caught up in visuals can lead to missed specifications. Though flowcharts are not as sexy, they are more informative and beneficial to defining a solution than any wireframe graphic interface.

PROJECT CASE STUDY