Site icon Beyond the Backlog

10 Ways to Understand Users and Fuel Product Discovery

Ways to Understand Users

Understanding all the various ways to understand users is a critical part of developing any new product, yet it deeply understanding your audience can often seem like an elusive goal. How can product managers truly get inside the minds of their target customers? What are users thinking but not saying out loud? Uncovering these insights in an accurate and actionable way is key to creating products that delight instead of disappoint. 

Rather than making assumptions or relying on instinct, smart product managers take a structured approach to product discovery research. Getting clear on user needs from the start helps ensure you build the right solutions to real problems. This prevents wasting time and resources on features users neither want nor need.  

This blog post will explore 10 ways to understand users that you can add to your discovery tool belt to uncover those critical user needs that may otherwise go unseen. Mixing and matching various qualitative and quantitative discovery methods allows product managers to develop a holistic point of view. Testing assumptions in multiple ways builds confidence by validating key needs from different angles. Read on to enhance your product discovery efforts.



10 Ways to Understand Users

1. Interviews

Conducting one-on-one user interviews offers a qualitative, conversational approach to gathering feedback. These sessions aim to deeply understand customer perspectives, pain points and desires through open-ended questioning and listening. This format provides more texture and nuance than surveys or focus groups.

Successful interviews start with careful screening and scheduling with targeted users that match your ideal customer profile. Prepare by developing an interview guide that outlines key topics to cover while leaving room for exploration through follow-up questions. Structure the guide across four segments: intro, context questions, product-specific questions on features and pain points, and closing. 

During the interview, build rapport through active listening: probe areas of interest, ask for examples or stories, and request clarification without judging responses. Wrap up by summarizing key discussion points and insights to validate that your interpretation resonated accurately. 

After interviews, analyze findings across the full set of sessions to spot trends, themes, and outliers. Look for common pain points to address or feature needs to guide your solution. Diverging perspectives also provide useful insights. Synthesize top requests and issues into a prioirtized roadmap for idea validation.

2. Focus Groups

Moderated focus groups offer another direct user feedback approach, this time in a group setting. Pulling together 6-10 users at once allows product managers to gather different perspectives in the same session. The group dynamic sparks participants to react and build on others’ comments, yielding exponentially more feedback.

Carefully recruit a diverse but aligned participant group that fits key user categories. Develop a discussion guide that hits on a range of relevant discovery topics while allowing natural flow between participants. Identify prompts for the moderator to reign in or encourage interaction as needed. 

Schedule sessions in locations convenient for participants when possible. Set up a comfortable, informal environment and provide refreshments to create a casual vibe. Record the discussion to capture all insights that emerge.  

Later, analyze across focus groups to find areas of alignment or debate. Does consensus exist around key pain points or feature needs? Are groups split in their perspectives on anything substantial? Capture verbatim participant quotes that illustrate findings especially well. 

These qualitative discovery approaches powerfully complement quantitative data or assumptions. Diving deep with real users guides product managers toward solutions that hit the mark by addressing clearly defined needs in a resonating way.

3. Surveys  

Surveys allow product managers to gather customer feedback and quantify user needs at a broader scale than qualitative methods. Well-designed surveys yield concrete data on priority features or services to guide discovery. They also provide benchmark metrics to measure solution success later. 

Carefully structure surveys to extract meaningful insights from customers. Begin with screener questions to confirm the respondent matches your target demographic. Start with broad issues to diagnose before diving into specific product feedback. Use a mix of closed-ended rating scale questions and open-ended options to gather data points and detailed written feedback.  

Keep surveys focused and scannable by limiting to 10-15 questions max. Offer an incentive upon completion to boost response rates. Promote through emails, in-app messages, or ads to motivate participation.

Analyze results by tallying rating scale data to reveal higher priority needs and common pain point themes mentioned. Break down responses by demographic factors if sample size allows. Share key statistics and verbatim comments that support major survey findings.  

Follow up a broad discovery survey with solution-specific surveys to refine concepts. Quick pulse surveys can test new features or content with users in an ongoing feedback loop.  

4. Customer Advisory Boards

Customer Advisory Boards (CABs) create a conduit for continual qualitative feedback from a set group of target users. Recruiting engaged customers that align with user segments serves as a sounding board over an extended timeframe. This builds more personal customer relationships compared to one-off surveys or interviews.

Good CAB recruitment establishes representation across your buyer personas, firmographics, or customer lifecycle stages. Compensate members appropriately for their extended commitment, such as through software discounts or gift cards. Aim for 10-15 advisors.

Set a regular cadence for convening your advisors, either through in-person events or virtual meetings every quarter or semester. Prepare discussion guides that probe product perceptions, ideas, or roadmap reactions. Schedule informal time for personalized outreach to nurture individual connections.

Manage logistics gracefully by coordinating schedules in advance and adapting to accommodate advisors. Collect qualitative feedback, quotes, and case studies to integrate user perspectives into strategy planning or market positioning. Thank advisors publicly for their valued partnership.  

5. Ethnographic Research  

Ethnographic research takes discovery directly into the user’s natural environment to uncover subtle behaviors, needs, and pain points by observation. Rather than asking what people want, watch what people do instead. 

These immersive techniques provide authentic real-world context compared to lab studies or surveys. Send researchers into relevant consumer settings: homes, offices, stores, events, etc. They blend in passively without interfering to capture candid insights first-hand.  

Common ethnographic approaches include:

Look at emotional connections and social influences as well as functional needs. Note environmental factors that positively or negatively impact interactions. Flag quotes, photos, or videos that vividly demonstrate key learning.  

Compile findings across observations to pinpoint pain points and gaps. Highlight use cases that diverged from your assumptions for further exploration. Turn ethnographic data into journey maps or personas bringing statistics to life.

6. Analytics Review  

Product analytics offer quantitative data on how customers currently use solutions by tracking in-app behavior. Tools like Amplitude, Mixpanel, or Google Analytics compile usage data points for analysis. 

Review analytics dashboards to uncover focus areas receiving little traffic as well as heavily used features. Look for unexpected usage patterns or workflows compared to the happy path. Monitor task completion rates. Analyze behavioral cohorts and retention metrics. 

Survey or interview analytics power users to better interpret findings by probing their reasoning. Seek to explain surprising data points through additional discovery. 

Cross tabulate analytics by persona, plan type, lifecycle stage or other variables to extract segment-specific insights. Identify VIP users for proactive outreach. Overlay ethnographic or testing observations to enrich dry data with human context. 

Analyze support tickets, NPS scores, or app store ratings in conjunction with usage patterns. Does low satisfaction correlate to specific areas? Which adopted elements show positive gains?  

Existing analytics offer a data treasure trove to guide discovery in progressive ways. Humanize metrics through direct customer dialogs for meaningful impact.

7. Support Ticket Mining  

Customer support conversations represent a goldmine of discovery insights. Users naturally describe their goals, obstacles, misconceptions, suggestions, and emotions when seeking help. Mining these tickets offers an efficient way to identify needs.

Set up processes to review support interactions and extract findings. Catalog topics, recurrent issues, intense user reactions, or feature requests. Highlight compelling user quotes and cases to tell a story.  

Support an analysis by tallying themes and topics to prioritize addressing based on frequency. Map trends over time aligned to product changes. Notify relevant teams of spikes or concerns.

Seek follow-up consent for future contact to probe findings from standout tickets. Reach back out listen more, learn why obstacles occurred, and make suggestions tangible. Build goodwill through the care.  

8. Competitor Analysis   

Gleaning insights from competitors’ offerings and customer reception sharpens your discovery efforts. Comparing where alternatives fall short steers you toward key differentiators. 

Review competitor websites, content marketing, and product messaging through the lens of a customer. How do they position value? Does it resonate? Where might false assumptions exist? 

Proactively interact with competitor solutions personally or via a user testing panel. Note sticking points, what feels seamless, and what lacks. Check app store ratings and analyze critical reviews.

Subscribe to competitors’ user research reports or summaries when available publically online. Jump off their discover takeaways with your audience in mind. 

Keep ethics top of mind when utilizing competitive intelligence by accessing only public information sources. Allow discoveries to inspire creative solutions instead of copying.  

9. User Testing

User testing means putting working prototypes or design mockups directly in front of target customer groups to gather feedback. Rather than asking what they want to see, have users interact with potential solutions. 

Prepare clear tasks for testers aligned to key assumptions or concepts to validate. Develop an instruction guide and questions to probe reactions. Carefully facilitate and observe sessions without guiding reactions.  

Gather feedback on elements that worked or didn’t, eased or hindered goals, pleased or annoyed. Identify areas of confusion and note suggestions. Thank users for bettering the end-product creators and customers alike benefit from enhancements.  

Testing early and often prevents major rework down the line. Recruit iteratively: 5 users often surface the majority of insights. Build testing feedback loops into development roadmaps.

10. Suggestion Boxes   

Finally, a low-lift tactic invites customers directly into the ideation process. Provide easy venues for sharing suggestions like a website form, in-app input field, dedicated email, or social post hashtag.  

Monitor channels closely to review ideas as shared. Catalog recommendations thematically in digital boards that developers and leadership can access. Upvote resonating suggestions.  

Follow up with proposal contributors if contact details are provided. Ask thoughtful questions for more context to evaluate feasibility. Or poll customers on variants of an idea to refine direction.  

Offer public recognition such as highlighting contributors in communications or naming features after engaged users. Enable customers to vote on popular proposals.  

Make it simple for time-pressed customers to share candid recommendations in their voices while scrolling through an app or visiting your website. Suggestion box methods harness the creativity of your best co-creators: the customers themselves!


Subscribe for free and never miss a post:


Ways to Understand Users: Conclusion

We covered a range of both common and creative approaches to deeply understand user needs critical for informing product direction. The most effective ways to understand users incorporate a blend of quantitative and qualitative methods. Surveys gather wide input identifying patterns. Interviews and testing dive into the meanings behind the data.  

Getting creative by shadowing customers in their native environment gives context to usage analytics. Advisory panels provide trusted guidance in interpreting findings and brainstorming solutions. Competitor analysis reveals strategic opportunities for differentiation.  

No single way to understand users perfectly captures every requirement on its own. So, form connections across qualitative and quantitative learnings to build confidence in identifying priorities. Pressure test through a different lens.  Then distill down the wealth of data into clearly defined user needs statements to orient product roadmaps around. Frame needs in terms of root problems rather than assumed solutions to spark creative ideas later. Circle back frequently with user panels to refine the approach and iterate.  

With clear insights, product managers can develop solutions that truly resonate with users by addressing their pain points and desires more potently. Utilizing these 10 ways to understand users can lead to building the right products right. Understanding begins with asking.


If you liked this post on 10 Ways to Understand Users, you may also like:

Exit mobile version