Actionable Tips to Unearth User Insight Gems
The hard-learned tips that would’ve made a better product, faster.
There’s a skill chasm between how well you think you run a user interview vs how you actually run a user interview.
I had dozens of saved audio files, all 20–40 minutes long. I didn’t want to listen and transcribe them since it’d take forever. But one day, I decided to start binge listening to my own interviews. And I discovered a ton of points for improvement.
My takeaways may be differ from your own, so I highly, highly encourage you to sit down, listen to your interviews, and really think about how to improve them. With that said, here’s the insights I’ve rediscovered from reviewing my own experiences.
General Ground Rules
- Empathy: If your interviewee doesn’t feel like you care, then they won’t BE HONEST with you. Get ready for “Yes” “No” defaults if you don’t.
- Body Language: Exercising body language can be a powerful way to show you care and build empathy. Nodding, leaning in, and movement mimicry demonstrate you CARE about your interviewee.
- “Foot-in-the-door” principle. Generate easy questions, then ramp up the question difficulty. Build trust and rapport before asking difficult questions. (“So what do you do on a day to day basis?” is easier to answer than “TELL ME YOUR BIGGEST PAIN POINT WITH YOUR ANALYTICS SOFTWARE?”)
- Risk Identification: Identify your biggest source of risk and generate questions to tackle it.
Coming up with Questions
- Question Audit: Determine if you ask as many open ended questions as you think you do. We have a bias to underestimate this number.
- Avoid Leading Questions: Anchoring open-ended questions will create biased responses and potentially faulty data. (“What are scenarios you feel a little uncomfortable in, for example, the office, the lunch room, etc.”)
- Use their words: Review commonly used phrases from previous interviews and incorporate those into your questions. People give better answers when your language resonates with them. (Case study: interviewees reacted better to the words expectations and assumptions than misconceptions)
- Concrete Questions: Avoid aspirational/hypothetical questions. People answer with what their ideal self does. Go for concrete questions embedded in experience. This gives you what they actually did. (“How do you generally use X” -> When was the last time you use X? Can you walk me through your experience?”)
- Break down themes: Identify your question themes and break them into manageable sub-questions. (“Why do you shop online?” = vague answers — > “What were the last items you bought online?” = more specific content)
- New Perspectives: Question phrasing and reframing can impact the quality of response you receive. (“What does this enable you to do” vs “Was there anything you couldn’t do before that you can now”)
In the Midst of Action
Frameworks to Discover Insights
- Feature Request Abstraction: Identify feature requests and follow up on their importance. This prevents you from wasting time building the wrong features. (I really want an export to excel feature. Why? Because I want to use excel to sort the prices…etc.)
- Finding Inconsistencies: Seek inconsistencies between what people do and say. These indicate gaps where you can provide value. (“I want to buy new clothes BUT they’re too expensive right now.”)
- Problem Mapping: Always seek out the origin of a problem with WHEN did you first notice this was a problem? This provides you valuable context. (“When did you first starting noticing X was a problem? What steps did you take to resolve it?”)
- Push + Pull: Incorporate “push + pull” into the interview to really understand a interviewee’s fears, motivations, desires, and other strong emotions. (“What are the consequences of X? How would you life be improved if X were solved?”)
- Compare/Contrast: Use the principle of compare/contrast to understand trade-offs. That way you understand what people truly value.(“How does X compare to Z?…Oh, so X is faster and easier to use but more expensive, so you chose X because it was more affordable?…)
- Launch Points: Leverage their shared problem examples as a launch point to find similar problems. Ah, so you mentioned X is a problem. Any other instances X is a problem?
Tactics to Clarify Meaning
- Clarify Definitions: Clarify adjective definitions into functional design specifications. This informs design. (Easy? What’s an example of an app you find easy to use?)
- Summarize: Summarize to clarify and confirm interviewee motivations if you’re uncertain. But don’t overuse or it sounds like you’re not listening. (“So X is important because of Y?”)
- Provoke: Provoke the interviewee by summarizing motivations (slightly) incorrectly to find unexpected insights. (“So X is important because of Z?…Oh, so it’s important because of more Y and less Z”)
- Question Follow-Up: You can ask close-ended questions, IF you follow up with them.
- Question Follow-Up: You can ask biased questions, IF you follow up with them. (“What do you most dislike about X? … Got it, so what are the consequences of X? …. None really?”)
- Dig Deep: Dig deeper into the root reasons with the 5 WHYS. (I personally believe “WHY” is difficult to answer. I reframe WHYs with WHATs. EG “Why do you shop online” -> “What do you shop online for” Then you can reverse engineer why they shop online.)
Fallbacks when you run out of questions
- Bread Crumbs: Follow the bread crumb trail of emotionally charged words. Emotional words indicate areas people really care about. (“So you LOVE when you finish that workflow? What makes you LOVE finishing that workflow?)
- Different Perspectives: Leverage different perspectives with 5 Ws and H to keep things going. (“When did you?… What did you?… How did you?…”)
Things NOT to do
- No Hypotheticals: Don’t ask them to hypothesize about other people’s actions or how systems they’re unfamiliar with work. You’ll get made-up answers. (NO: “So how do you think X works?” if they haven’t worked with X)
- No two-in-one: Never ask 2 questions in one question. Make it easy on the interviewee. (“So what’s your favorite part about this and what makes this better than X?” -> “So what’s your favorite part?… What makes this better than X?”)
Small tricks to get extra bit of insight
- Silence: Create an uncomfortable silence to encourage more interviewee sharing by waiting 2–3s. People will feel compelled to share more to break the silence.
- New Leads: Near the end, ask “Is there anyone else you recommend I speak to?” You’ll often get new leads for interviews.
- The Catch-All: Ask “Is there anything I should’ve asked but didn’t?” at the end as well. If you’ve missed something important, the interviewee will speak up.
- Always Find the Gems: Don’t assume you know everything. Every interview has something new…if you really listen.
That’s it for now! Hopefully one of these tips will provide you some inspiration to try something new. Test them out, mix and match, and really empathize with your users.
If you like what you just read, please hit the ‘Recommend’ button below as that would mean a lot!