Extracting Insights from Qualitative Interviews and User Tests (Continuous Discovery Habits)

Goal

To guide an AI assistant in systematically extracting meaningful insights from qualitative interviews or user test sessions, creating structured interview snapshots that capture specific stories, opportunities, and behavioral insights following the Continuous Discovery Habits methodology.

Output

Format: Markdown (.md)
Location: user-interviews/snapshots/
Filename: snapshot-[participant-name]-[date].md

Process

1. Data Validation: Assess the completeness and quality of provided interview data
2. Context Extraction: Identify session type, research goals, and participant context
3. Story Identification: Extract specific behavioral stories, not generalizations
4. Experience Mapping: Create user journey maps for key stories
5. Opportunity Analysis: Identify pain points, needs, and improvement areas
6. Insight Synthesis: Recognize patterns and behavioral insights
7. Snapshot Creation: Compile into structured interview snapshot
8. Quality Review: Validate completeness and clarity

Guide

When Receiving Interview Data

• Ask clarifying questions if data is incomplete or ambiguous
• Request specific examples if only general statements are provided
• Confirm participant context if demographic or behavioral details are missing
• Validate research goals to ensure alignment with snapshot objectives
• Highlight inconsistencies if conflicting information appears

Data Processing Guidelines

• Focus on concrete behaviors over opinions or intentions
• Extract contextual details (when, where, with whom, why)
• Identify emotional moments (frustration, delight, surprise, confusion)
• Capture workarounds and problem-solving approaches
• Note repeated patterns that indicate systematic issues
• Distinguish between what people say vs. what they do

Quality Standards

• Completeness: All required sections must be filled
• Specificity: Use concrete examples, not generalizations
• Clarity: Write in clear, actionable language
• Consistency: Follow established format and structure
• Insight Value: Each insight should be actionable or informative

Output Format

Required Structure

# Interview Snapshot: [Participant Name]

**Date:** [YYYY-MM-DD]  
**Type:** [Discovery Interview | Usability Test | Contextual Inquiry | Other]  
**Duration:** [Minutes]  
**Interviewer(s):** [Name(s)]  

---

## Quick Facts
- **Segment:** [User profile / role / demographic]  
- **Key Behaviors:** [2-3 observed behavior patterns]  
- **Tools Used:** [Products, tools, services mentioned]  
- **Experience Level:** [Novice / Intermediate / Expert / Domain-specific level]  
- **Setting:** [Contextual environment and circumstances]  

---

## Memorable Quote
> "[Direct quote that captures participant's voice and perspective]"

---

## Story Summary

### Story 1: [Descriptive title]  
**Context:** [Time, place, situation, trigger]  
**What Happened:** [Concrete actions taken, step by step]  
**Outcome:** [Result or consequence of the actions]

**Key Moments:**  
- [Specific behavioral insight with context]  
- [Emotional response or reaction]  
- [Workaround or adaptation used]  

*(Repeat as needed for additional stories)*

---

## Experience Map
*A text-based, visual representation of the participant's journey for a specific story. Focus on concrete actions and context, not generalizations.*

**Scope:** [Start and end points of the journey]  
**Goal:** [Participant's desired outcome]  

**Journey Stages:**
1. **Stage: [Stage title]**
   - **Actions:** [Specific behaviors and steps taken]
   - **Thoughts/Feelings:** [Quotes or paraphrased emotions]
   - **Pain Points:** [Specific frustrations or challenges]
   - **Tools/Resources:** [What was used or available]

*(Repeat for each stage in the journey)*

---

## Opportunities
- **[Opportunity title]**: [Specific description of customer needs, pain points, desires, wants—chances for us to intervene in a way that makes our customers' lives better.]

---

## Insights
- **[Insight category]**: [Pattern or behavior that goes beyond a single story, e.g., user mental models, decision-making shortcuts, systemic frustrations]

Optional Sections

• Follow-up Questions: Additional research needed
• Related Research: Connections to other studies or findings
• Stakeholder Notes: Implications for different teams or roles

Quality Assurance Checklist

Before Finalizing

• All required sections are complete
• Stories contain concrete behavioral details
• Experience map follows logical flow
• Opportunities are specific and actionable
• Insights go beyond individual stories
• Quotes are accurate and representative
• Context is clear and complete

Best Practices

Experience Mapping

• Start with clear boundaries (what triggers the journey, what defines success)
• Focus on concrete actions and decisions
• Include emotional states and pain points
• Map the complete journey, not just the happy path

Opportunity Identification

• Connect opportunities to specific stories and behaviors
• Consider both explicit needs and implicit frustrations
• Evaluate impact and feasibility
• Prioritize based on frequency and severity