How to Use Ethnographic Research in Product Design
Explain when and how a PM should utilize ethnographic research (in-context user observation) compared to traditional quantitative surveys or A/B testing.
Why Interviewers Ask This
Interviewers ask this to assess your ability to distinguish between qualitative depth and quantitative breadth. They want to see if you understand that ethnographic research reveals the 'why' behind user behaviors, which surveys often miss. At Airbnb, they value designers who prioritize human connection and context over raw data alone.
How to Answer This Question
1. Define Ethnography: Start by clarifying that ethnography involves in-context observation to uncover unarticulated needs, distinct from self-reported survey data.
2. Contrast Methodologies: Explain when to use it versus A/B testing. Use ethnography for early discovery or complex emotional journeys (e.g., trust in booking) and A/B testing for optimizing known variables.
3. Provide a Scenario: Describe a specific situation where you observed users in their environment, noting a behavior they couldn't articulate in an interview.
4. Connect to Strategy: Detail how these insights directly influenced product features or strategic pivots, ensuring alignment with business goals.
5. Conclude with Impact: Summarize the outcome, emphasizing how deep empathy led to better user retention or satisfaction metrics.
Key Points to Cover
- Demonstrates clear distinction between observing actual behavior versus relying on self-reported data
- Shows strategic timing for research methods, knowing when to dive deep versus when to scale
- Connects qualitative insights directly to tangible product improvements and business outcomes
- Reflects Airbnb's cultural emphasis on empathy, trust, and authentic human connection
- Proves ability to identify hidden pain points that quantitative tools like A/B tests cannot detect
Sample Answer
I utilize ethnographic research when standard analytics and surveys fail to explain why users are dropping off or hesitating. For instance, at Airbnb, understanding the anxiety of first-time hosts is critical. While surveys might tell us hosts are nervous, only in-context observation reveals the specific friction points, such as the fear of taking photos in a messy room or the confusion over listing pricing algorithms.
I contrast this with A/B testing, which is ideal for optimizing a known button color or headline once we understand the problem. However, if we don't know what the problem is, testing variants is inefficient. In one project, I shadowed guests during check-in. We noticed they weren't using the app's messaging feature because they were worried about appearing intrusive. This insight wasn't in our survey data. Consequently, we redesigned the communication flow to be more asynchronous and less immediate, reducing guest anxiety.
This approach aligns with Airbnb's core value of belonging. By prioritizing ethnographic depth, we move beyond guessing user needs and design solutions rooted in real human behavior, leading to higher conversion rates and stronger community trust.
Common Mistakes to Avoid
- Confusing ethnography with focus groups, failing to emphasize the importance of natural context
- Overvaluing qualitative data without explaining how it integrates with quantitative validation
- Suggesting ethnography for every problem, ignoring scenarios where speed or scale requires A/B testing
- Failing to provide a concrete example of how observation changed a specific product decision
Practice This Question with AI
Answer this question orally or via text and get instant AI-powered feedback on your response quality, structure, and delivery.
Related Interview Questions
Improve Spotify's Collaborative Playlists
Easy
SpotifyExplain 'North Star Metric'
Easy
LinkedInTrade-offs: Customization vs. Standardization
Medium
SalesforceDesign a 'Trusted Buyer' Reputation Score for E-commerce
Medium
AmazonDesign a Feature for Collaborative Budgeting (Airbnb)
Medium
AirbnbAchieving Consensus on Architecture
Hard
Airbnb