Principles of Product Management: Ethnographic Research, Contextual Inquiry, Diary Studies

Ethnographic Research, Contextual Inquiry, Diary Studies

Ethnographic Research, Contextual Inquiry, Diary Studies

What This Is

These are qualitative research methods that help PMs uncover why users behave the way they do—not just what they do. Unlike surveys or analytics, these techniques reveal hidden needs, workflows, and emotional triggers by observing users in their natural environment (ethnography), shadowing them during tasks (contextual inquiry), or tracking their behaviors over time (diary studies). Why it matters: Most product failures stem from solving the wrong problem. These methods help you discover unmet needs before building anything.

Real-world example: Slack’s early team used contextual inquiry to observe how teams used email and chat tools in real work settings. They noticed users struggled with context switching between tools, leading to the "threads" feature—a core differentiator that reduced noise and improved productivity.

Key Terms & Frameworks

• Ethnographic Research: Observing users in their natural environment (e.g., home, office) to understand behaviors, culture, and pain points without interference. Goal: Uncover latent needs (problems users don’t articulate).

• Example: Airbnb sent researchers to live with hosts to understand their workflows, leading to features like calendar sync and automated messaging.

• Contextual Inquiry: A structured interview + observation method where you watch users perform tasks in their real environment, asking questions while they work. Combines master-apprentice model (you learn by watching) with artifact walkthroughs (users explain tools they use).

• Framework: AEIOU (Activities, Environments, Interactions, Objects, Users) – a checklist for what to observe.

• Diary Study: Users self-report behaviors, thoughts, or emotions over time (e.g., daily logs, photos, or voice notes). Useful for longitudinal insights (e.g., habit formation, infrequent tasks).

• Example: Spotify used diary studies to track how users discovered music over a month, leading to the "Discover Weekly" playlist.

• Jobs-to-be-Done (JTBD): A framework to reframe user needs as "jobs" they’re "hiring" your product to do. Ethnography helps uncover these jobs.

• Formula: "When [situation], I want to [motivation], so I can [outcome]."

• Example: McDonald’s milkshakes were "hired" by commuters to kill time during long drives—not just as a snack.

• Affinity Diagramming: A synthesis method where you cluster observations from research into themes (e.g., pain points, workarounds). Used after ethnography/contextual inquiry to spot patterns.

• Steps: 1) Write observations on sticky notes, 2) Group similar notes, 3) Label themes.

• Shadowing vs. Interviewing:

• Shadowing: Silent observation (ethnography/contextual inquiry).
• Interviewing: Asking questions (e.g., "Why did you do that?").

• Key difference: Shadowing reveals actual behavior; interviews reveal perceived behavior (which can be biased).

• Saturate & Group: A synthesis technique where you saturate (collect all data) and group (find patterns). Used to turn raw research into actionable insights.

• Example: After observing 10 users, you notice 8 use a workaround—this becomes a high-priority opportunity.

• The 5 Whys: A root-cause analysis tool. Ask "why?" 5 times to uncover the real problem behind a symptom.

• Example:

  
  
  1. Why did users abandon checkout? → "Too many steps."
  2. Why are there too many steps? → "We ask for shipping and billing separately."
  3. Why do we ask separately? → "Legacy system constraints." → Real problem: System inefficiency, not just UX.

• Participant Recruitment Matrix: A table to ensure diverse user samples. Columns: Segment (e.g., power users, new users), Behavior (e.g., frequent vs. occasional), Demographics (e.g., age, location).

• Goal: Avoid bias by including edge cases (e.g., users who churned, users who use workarounds).

• Think-Aloud Protocol: Ask users to verbalize their thoughts while performing a task. Reveals cognitive friction (e.g., "I’m confused by this button").

• Example: Google used this to improve search results—users said, "I don’t know what ‘cached’ means," leading to clearer labels.

• Behavioral vs. Attitudinal Data:

• Behavioral: What users do (e.g., clicks, time spent). From analytics or observation.
• Attitudinal: What users say (e.g., "I love this feature"). From interviews or surveys.
• Key insight: Behavioral data > attitudinal data (users often don’t do what they say).

Step-by-Step / Process Flow

How to Run Ethnographic Research, Contextual Inquiry, or Diary Studies

(Pick one method based on your goal—see table below.)

Step 1: Define the Research Goal

• Ask: "What problem are we trying to solve?" (e.g., "Why do users abandon our onboarding flow?").
• Avoid: Vague goals like "understand users better." Instead, use JTBD or problem statements:
• "We want to reduce churn in our SaaS product by understanding why users stop using it after 30 days."
• Pro tip: Align with OKRs (e.g., "Increase retention by 15% by Q3").

Step 2: Recruit Participants

• Target 5–10 users per segment (e.g., power users, churned users, new users).
• Use a recruitment matrix to ensure diversity (see Key Terms).
• Incentivize: Offer gift cards ($50–$100), swag, or early access.
• Avoid: Recruiting friends/family (bias) or only "ideal" users (miss edge cases).

Step 3: Design the Study

• For Ethnography/Contextual Inquiry:
• Create a discussion guide (not a script!) with:
  • Warm-up questions (e.g., "Walk me through your typical day").
  • Task prompts (e.g., "Show me how you use [product] to [achieve X]").
  • Probes (e.g., "Why did you do that?" "What’s frustrating here?").
• Tools: Notebook, camera (with permission), screen recording (for digital tasks).
• For Diary Studies:
• Choose a format: Text logs, voice notes, photos, or a dedicated app (e.g., dscout, UserTesting).
• Prompt examples:
  • "Take a photo of your workspace when you use [product]."
  • "What’s one thing that frustrated you today about [product]?"
• Frequency: Daily or weekly, depending on the behavior.

Step 4: Conduct the Research

• Ethnography/Contextual Inquiry:
• Observe first, ask later. Let users work naturally before probing.
• Use AEIOU to structure notes (see Key Terms).
• Capture artifacts: Photos of workarounds, screenshots of tools they use.
• Debrief: After the session, ask, "What surprised you about what you saw?"
• Diary Studies:
• Send reminders (e.g., "Don’t forget to log your experience today!").
• Follow up on interesting entries (e.g., "You mentioned X—can you tell me more?").

Step 5: Synthesize Insights

• Affinity Diagramming:
• Write observations on sticky notes (1 idea per note).
• Group similar notes (e.g., "Users struggle with X," "Users use Y workaround").
• Label themes (e.g., "Onboarding friction," "Lack of trust in data").
• Saturate & Group:
• Look for patterns (e.g., 8/10 users do X).
• Identify outliers (e.g., 1 user does Y—why?).
• Map to Opportunities:
• Turn themes into problem statements (e.g., "Users abandon onboarding because they don’t understand step 3").
• Prioritize using ICE (Impact, Confidence, Ease) or RICE.

Step 6: Share Findings & Drive Action

• Create a research report with:
• Key insights (1–3 sentences per theme).
• Supporting quotes/photos (e.g., "User said: ‘This is so confusing’").
• Opportunities (e.g., "Simplify step 3 in onboarding").
• Present to stakeholders with a story arc:
• Hook: "We discovered a major drop-off in onboarding."
• Insight: "Users don’t understand step 3 because it uses jargon."
• Opportunity: "If we simplify the language, we could increase activation by 20%."
• Align on next steps: Use dot voting or ICE to prioritize solutions.

Common Mistakes

PM Interview / Practical Insights

What Interviewers Probe

1. "How would you decide between ethnography, contextual inquiry, or diary studies for a given problem?"
2. Answer: Match the method to the research goal:
   • Ethnography: Cultural/contextual insights (e.g., "How do nurses use our app in a hospital?").
   • Contextual Inquiry: Task-specific workflows (e.g., "How do users complete a purchase?").
   • Diary Study: Longitudinal behaviors (e.g., "How do users form habits with our app over a month?").

3. Trap: Don’t say "ethnography" for everything—it’s time-consuming and not always necessary.

4. "How do you handle a stakeholder who says, ‘We don’t need research—just build it’?"

5. Answer: Use data + storytelling:
   • "Last time we skipped research, we built a feature 80% of users ignored. Here’s how research could save us time/money."
   • "Let’s run a quick 5-user contextual inquiry—it’ll take 1 week and give us confidence we’re solving the right problem."

6. Trap: Don’t argue—show the cost of not researching (e.g., wasted dev time, low adoption).

7. "How do you turn research insights into product decisions?"

8. Answer: Use prioritization frameworks (e.g., ICE, RICE) + storytelling:
   1. Synthesize (affinity diagramming).
   2. Prioritize (e.g., "This pain point affects 60% of users and is easy to fix").
   3. Align (e.g., "If we fix X, we could increase retention by 10%").

9. Trap: Don’t just list insights—tie them to business outcomes.

10. "How do you avoid bias in qualitative research?"

11. Answer: Use triangulation (combine methods) + diverse recruitment:
    • Methods: Mix ethnography + analytics + surveys.
    • Recruitment: Use a participant matrix to include edge cases.
    • Analysis: Have multiple team members review insights.
12. Trap: Don’t rely on confirmation bias (e.g., only listening to users who validate your hypothesis).

Quick Check Questions

1. Your team wants to redesign the checkout flow for an e-commerce app. You have 2 weeks. Which method do you use, and why?
2. Answer: Contextual inquiry (1–2 weeks, task-specific, reveals workflow pain points).

3. Why: Ethnography is too slow; diary studies are better for longitudinal behaviors.

4. During a contextual inquiry, a user says, "I love this feature!" but never uses it. What do you do?

5. Answer: Dig deeper ("Show me how you use it" or "When was the last time you used it?"). Why: Attitudinal data (what users say) often conflicts with behavioral data (what they do).

6. You’re launching a new fitness app. How would you use diary studies to improve retention?

7. Answer: Ask users to log daily (e.g., "What motivated you to work out today?" or "What made you skip a day?"). Why: Reveals habit triggers and emotional barriers over time.

Last-Minute Cram Sheet

1. Ethnography = Observe users in their natural environment (e.g., home/office) to uncover latent needs.
2. Contextual Inquiry = Interview + observe users while they perform tasks (use AEIOU framework).
3. Diary Study = Users self-report behaviors/emotions over time (great for longitudinal insights).
4. JTBD = "When [situation], I want to [motivation], so I can [outcome]." (Reframe needs as "jobs.")
5. Affinity Diagramming = Cluster sticky notes into themes to spot patterns.
6. AEIOU = Activities, Environments, Interactions, Objects, Users (checklist for observations).
7. 5 Whys = Ask "why?" 5 times to find the root cause of a problem.
8. Behavioral > Attitudinal data (users do ≠ users say).
9. Recruit 5–10 users per segment (avoid bias by including edge cases).
10. ⚠️ Don’t lead questions (e.g., "Don’t you hate this?" → "How do you feel about this?").
11. Workarounds = unmet needs (document them!).
12. Prioritize insights with ICE/RICE (tie to business outcomes).