A little context goes a long way...
Only you can see your suggestions
Product Designer at Headspace
Product designer. Currently 🙏🏻 @Headspace. Previously @Lyft + @Google.
Be intentional about your process and take the time to prepare. Create clear research goals, write an interview script, and watch out for common pitfalls.
What are you trying to understand about your product, a specific feature, or your users, and why?
It sounds simple, but relying on your script (which has been reviewed and agreed upon by a diverse set of stakeholders) can help remove bias.
a. Ask open-ended questions that begin with "why", "what" and "how". This helps draw out information and personal stories. b. Conversely, avoid yes/no questions. They aren't great conversation starters and don't help you understand motivation. c. Avoid questions that you think you already know the answer to. This can help with confirmation bias later on (when we remember information that confirms our beliefs). d. Write out probing, follow-up questions. This helps clarify anything that could be ambiguous or misinterpreted. This also helps us avoid an anchoring bias, when we rely too heavily on the first piece of information we get.... See more
These teammates are inherently biased and invested. than someone else who didn't work on the feature. If this is unavoidable, you may consider telling a white lie to let users know that you didn't work on the feature. This helps users feel more comfortable being candid in their feedback.... See more
Highlight things that stick out as wins or red flags, but save the interpretation for post-session debriefs. This can help prevent a whole load of cognitive biases, such as a clustering illusion (overestimating importance of small clusters within a bigger dataset) and the framing effect (reacting to information differently based on how it's presented).... See more
Like a first date, right?