Scoping a project’s user-research phase is a classic Catch-22 situation. Before a project even begins, you must plan the research activities and the time necessary to perform them, but you’ll rarely have enough information to make these decisions optimally until after the project begins. If you estimate too much time and money, you might scare clients away. Estimate too low, and you’ll either go over budget or won’t have enough time to do the research properly.
To accurately scope user research, you must have a somewhat detailed understanding of the project’s business goals, the users, and their tasks. While you can usually get an overview of this information by talking with your clients, it’s difficult to obtain accurate, detailed information until after a project’s kickoff meeting and initial stakeholder discussions. At that point, you might realize that the research methods you’ve planned aren’t the ones that would let you best understand the problem. You might need more or different participants, and there might not be enough time to conduct and analyze the research. In this column, I’ll discuss some of the problems you may encounter when scoping user research and provide some advice about how to make scoping more accurate. Read More
In UX research, your job is to understand, persuade, and influence. First, you need to talk to users to understand their behaviors and uncover their needs. Then, you need to convey your learnings to the product team in a persuasive, coherent way. Finally, you need to drive action within the product team, influencing the project and its priorities.
Establishing strong partnerships with both your product owner and your overall product team is the best way to increase the impact of your research. Involve the team throughout your research process—from defining the research goals to presenting the final readout—and everyone will get more out of the research. The product team learns how valuable well-designed, well-executed research can be, and you’ll conduct better informed, more relevant research. Having regular discussions with the product team helps you focus on the most valuable research goals, enabling you to refine your research plan to ensure maximum impact. Read More
Have you ever worked with a product owner who has never collaborated with UX researchers before? Or a product owner who is fearful of or even hostile to your conducting research for his product? How do you educate a product owner on the value of UX research and reassure him or her that you’re not coming in to issue orders?
A product owner could feel threatened that a UX researcher—who might not know the ins and outs of the product that well—would be evaluating the product and recommending future actions, features, and strategies. As a UX researcher, empathy and communication are two of your most important tools—and working with a new product owner is a great opportunity to leverage them. It’s important to consider things from the product owner’s point of view and alleviate any concerns through clear communication. Read More