An overview the UX research process

- My favorite response to nearly every question about UX is, well, that depends. There is never just one right way to do something or an exact set of steps that will always be applicable, but every research has phases to plan and execute research, followed by a phase to understand and communicate findings and insights. This course won't cover details of how to choose appropriate methodology or run research efforts, so if you want that information, put my UX Research Fundamentals course on your saved list. UX research should always start with defining and aligning on a research goal so that it's very clear what you're trying to learn and what decisions will be made with that information. You'll want to identify specific objectives and think through the kind of data that will best answer those questions, such as whether you need to observe the behavior of a specific set of users or gather opinions from a large sample of a target population. Identifying what you're trying to learn and what kind of data will best serve that will determine the most appropriate research method to use. I cover the different methods and information on how to choose in my course on UX Research Fundamentals. You'll need to think through who you need to recruit and the logistics of finding, communicating with, scheduling, and compensating them. Be sure to consider what would be ideal for your learnings, as well as realistic constraints, like budget or the participants' availability. You may need to make some compromises to best address your exact situation. You'll also need to think through potential restrictions or regulations. Some industries and organizations have very specific rules about how they reach out to customers or provide payments, and sometimes you need to get creative to find a solution that works for all. Choosing who you'd like to talk to is usually the easy part. The combination of method and recruitment approach will have the most impact on deciding timeline, location, and budget. They'll help you identify how long you'll need to allow for recruiting, schedule when and where exactly the research will take place, determine how long you'll need to analyze and synthesize the data, and plan how and when you'll communicate your findings. If you work in an environment where you have a set budget, you may need to work back from that to adjust either method or recruitment approach, or advocate for a higher budget to address the needs. This is also likely the point that you'd be ready to pitch a research effort if that's applicable to your context. Once you've determined the general methodology and participant recruitment plan, you'll want to flesh out the more specific details of your approach, crafting the specific questions you'll ask or tasks for users to perform. Make sure to give yourself time to thoroughly plan and revise, incorporating feedback from stakeholders and teammates. Collaborating on the plan helps the whole team engage with the research process and ensures that you don't miss any potential nuances in context or background information. Then it will come time to execute the research and begin collecting data. This execution part varies widely on method, but it's always crucial to get right so that you receive high-quality data. For instance, if you set up an unmoderated usability test and the prototype link isn't working or the screen recording doesn't happen, you'll have wasted all the effort of finding participants and setting up the sessions. Once all your data is collected, it's time to make sense of what you found. The analysis and synthesis process is very dependent on your method and type of data collected, whether that's calculating something concrete like an average time on task, or extracting meaning from a series of conversations. You'll very likely end up writing some kind of report or presentation to communicate what you found. The goal here is not just to report back facts, but translate findings into meaningful, actionable insights. Finally, research efforts are most effective when they're able to be connected to other streams of work. I recommend looking for a way to document and organize efforts and key takeaways. Regardless of the tool or process, having some sort of repository that stores information about the planning and findings from past efforts can help you better share existing information to new or related team members and plan for future work. Focus on connecting your effort to the broader context of your organization and its overall goals.