User-Centric Research for PMs
User-Centric Research for PMs
Get to know your Users, and What They want
User-Centred Design Requires User Research
As you’re framing the problem you’re trying to solve — it’s important to ask:
What do your users want to get done?
What are their goals?
What are they trying to achieve?
So, What is user research?
User research focuses on understanding user behaviors, needs, and motivations through observation techniques, task analysis, and other feedback methodologies. This field of research aims at improving the usability of products, services, or processes by incorporating experimental and observational research methods to guide the design, development, and refinement of a product. User researchers often work alongside product manager, designers, engineers, and programmers in all stages of product creation and idealization.
User research is an iterative, cyclical process in which observation identifies a problem space for which solutions are proposed. From these proposals, design solutions are prototyped and then tested with the target user group. This process is repeated as many times as necessary.
User research is the act of interviewing prospective and actual users of your products to gain clarity on a number of objectives. You might use it to figure out why people aren’t adding recommended products to a cart, why they’re not clicking through your emails on mobile phones, or why adoption of your application has fallen significantly.
You may also be developing a new product or redesigning a website and know you want to do it differently this time around. All of these are great reasons to let your users tell you how they feel about your product.
Benefits of user research
Decrease costs in the long term; save on development and redesign efforts
Increase user satisfaction; deliver exactly what your target wants
Get qualitative feedback which helps you to improve user’s interactive experience increasing conversion rate
Understand what best supports user’s goals and motivations; focus on the features that really matter to your target
Gain a competitive advantage; stand out from the crowd, be always 1 step ahead of your competitors, create a “wow” effect
Shorten the learning curve for new users; make your product easy-to-use
Have not only a beautiful design but a smart one, putting your user in the center of your product strategy
User Research Methods
A wide range of research methods is available in the field of user research. To better understand when to use which method, it is helpful to view them along with a 2x2 dimensional framework with the following axes :
User research essentially splits into two subsets:
Qualitative research – Ethnographic field studies and interviews are examples of methods that can help you build a deep understanding of why users behave the way they do
Quantitative research – With more structured methods such as surveys, you gather measurable data about what users do and test assumptions you developed from qualitative research.
We can also split user research into two approaches:
Attitudinal – you listen to users’ words (e.g., in interviews).
Behavioral – you watch their actions through observational studies.
Usually, you can get the sharpest view of a design problem when you apply a mixture of both quantitative and qualitative research as well as a mixture of attitudinal and behavioral approaches.
The Context of the product use
Natural use of the product – the goal is to leave the user with a product and look at what he or she does. This provides greater validity but less control over what topics you learn about.
Scripted use of the product – is done in order to focus the insights on specific usage aspects, for example newly redesigned flow.
Not using the product during the study – studies, where the product is not used, are conducted to examine issues that are broader than usage and usability, such as a study of the brand, demand, etc
A hybrid of the above – allows users to interact with and rearrange design elements that could be part of a product experience, in order to discuss how their proposed solutions would better meet their needs and why they made certain choices. Concept-testing methods employ an approximation of a product or service that gets at the heart of what it would provide in order to understand if users would want or need such a product or service.
Qualitative Research
Qualitative research is primarily exploratory research, undertaken to establish users’ underlying motivations and needs. It’s useful to help you shape your thinking and to establish ideas, which can then be built and tested using quantitative methods.
Broadly speaking, qualitative methods are largely unstructured, tend to be subjective, are at the softer end of science, and are about establishing insights and theories (which we then test, often using quantitative approaches). They tend to be smaller sample sizes and require a degree of hands-on facilitation. With qualitative research user behaviors and attitudes are gathered directly.
I’ll be exploring one qualitative research methods in this newsletter today that is
User Interivews
Interviews are a great way to really get to the heart of your users’ needs. To facilitate interviews effectively requires a degree of empathy, some social skills, and a sense of self-awareness. If you’re not this person, find someone on your team who is.
It’s important to put your interviewees at ease; they need to feel comfortable sharing their thinking with you. If you can build a rapport with them, they’ll often open more honestly with you. One of the biggest benefits of interviews — over, for example, surveys — is that you learn not only from your interviewees’ answers but by their body language, too.
Broadly speaking interviews fall into one of two categories:
Structured Interviews: Where the interviewer focuses on a series of structured questions, comparing the responses of the interviewee to other interviewees’ responses.
Semi-Structured Interviews: Where the interviewer adopts a looser, more discussion-driven approach, letting the interview evolve a little more naturally.
In reality, anyone who has conducted interviews will know that that is — by nature — organic. Even if you have a predetermined structure in place, it’s important to allow some breathing room to allow the interview to evolve.
Put some thought into your research questions in advance, but allow the interviewee the latitude to move into areas that you may not have considered up front. Interviews are a useful way to challenge your assumptions and interviewees can often lead you to unexpected discoveries and things that you perhaps weren’t aware of.
It’s important to put the interviewee at ease, ensuring they feel comfortable answering your questions. Facilitating an interview effectively isn’t easy, so it’s helpful to use another member of the team as a notetaker, this allows you to focus 100% on your interviewee.
User interview questions
Here is a list of helpers I use when I build my user interview questions. I usually prefer to conduct semi-structured interviews. It means that I write a guide with the main questions and topics I want to ask about. But I might not totally follow this guide and dig into topics that users will bring up while talking to them. This makes it feel more like a conversation than guided interviews do. Even if I record/have a note-taker, I like to take my own notes during the interview. This lets me ask to follow-up questions on what the user said later. I also usually ask a few questions during usability tests, so here again, those questions are handy.
Those questions are for the core of the interview outside of your screener, demographic questions.
1. Open discovery questions
To keep the conversation going I want to ask open questions. Those questions are questions that require more than a single word answer (like yes/no). Avoid starting questions by “did you” / “have you” / “were you” and replace them with “why”, “how”, etc.
“Tell me about …”
“Could you describe to me how you… / your experience with…?”
Frequency and quantity: “How often do you…?” “How much/many…” (how much can also be used to probe-level of knowledge like “how much do you know about this topic?”)
“What … do you use/do?”
“Why do you …”
2. Understanding user tasks/activities
Here are a few starter questions that help me understand how people perform tasks and activities. Most of the time I work on a digital products, but those can apply to any type of task or activity.
“Can you describe how you / how you would [task]?”
“What are all the things you need to do in order to [task?]”
Sequence: “Walk me through [task], how would you?”
Comparison: “What is the difference between [task 1] and [other tasks]?”
3. Performing/showing
User interviews don’t have to be limited to questions you can also ask people to perform tasks.
“Please / can you show me how you … “ ask them to perform the task, share their screen, etc.
Role-playing: “Let’s pretend I’m a colleague who knows nothing about this, can you guide me so that I could do it myself afterward?” (a friend of mine likes to use “explain to me like I’m five years old”, I like the idea but it might not be good in some situations ^^)
4. Recalling the past / anticipating the future
You can ask people about events in the past. Be careful though: any event prior to a few days in the past might be distorted. People are Lazy, Forgetful Creatures of Habit. Also note that people have a hard time projecting in the future so, again, treat the replies to those kinds of questions lightly.
“Can you recall a situation when you …, what did you do?”
“Can you tell me about your most significant/ memorable experience/interaction with…?”
“How do you think … is going to help you?”
“Could you describe the ideal product/experience…?”
5. Opinions/points of view/attitude and projections
Those questions usually help me ask about opinions. Still, you need to bear in mind that opinions questions are highly susceptible to some biases. For example: courtesy bias is “the tendency to give an opinion that is more socially correct than one’s true opinion, so as to avoid offending anyone”.
“What do you think about …?”
“What do you like/dislike about…?”
“What would your friend/partner/colleague think of that?
“Some people …, other …, what is your opinion on that?”
“Last week I interviewed people who did // said … What do you think of that idea // how do you feel about this approach?
6. Talking about problems and pain points
Part of my job is to understand issues and pain points in order to try to solve them. Here are some questions that help.
“How does this problem impact you?”
“How did you solve that issue ?”
“What’s the hardest / most frustrating part about …?”
“If you had a magic wand, what would you change?”
7. Sentence completion and drawing
Last but not least I sometimes ask people to complete a sentence. I also ask them to draw something like a process, how they recall the interface, etc. Some people are more visual thinkers than others so it can really help. How many times did you end up in a conversation where someone just said “wait let me show you” and started drawing a chart to explain to you? 🙂
Product Manager’s Guide
40% off for all the subscribers of productmindset newsletter
