# Continuous Discovery Habits

> Structured methodology for infusing weekly customer research into product decisions through five interconnected habits

- Skill: `lev-os/continuous-discovery-habits` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lev-os/continuous-discovery-habits`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lev-os/continuous-discovery-habits/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: lev-os (https://skillmd.com/u/lev-os)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/lev-os/continuous-discovery-habits

---


# Continuous Discovery Habits

## Overview
Teresa Torres' framework for making continuous customer discovery a sustainable team habit rather than a one-off event. Published in her 2021 book, this methodology helps product teams integrate ongoing customer research into daily product decisions through five core habits.

## Core Principle
Product success comes from continuous, structured customer engagement, not sporadic research sprints. Teams should talk to customers every week to maintain a tight feedback loop between discovery and delivery.

## The Five Core Habits

### Habit 1: Weekly Customer Interviews (Keystone Habit)
The foundation of continuous discovery. Talking with customers weekly keeps discovery agile and prevents building in isolation.

**Why Weekly**:
- Disprove hypotheses and pivot within days, not months
- Build interviewing muscle memory through repetition
- Maintain fresh customer context for daily decisions
- Catch problems early before significant investment

**Implementation**:
- Schedule recurring interview slots (even if you don't fill all)
- Rotate interview responsibilities across the product trio
- Document insights immediately after each session
- Target 2-3 interviews minimum per week

### Habit 2: Start with Outcomes, Not Solutions
Use desired business outcomes as the north star for all discovery work. Outputs (features shipped) matter less than impact created.

**Outcome-Oriented Mindset**:
- Define success as customer behavior change, not feature completion
- Choose one key outcome metric to focus discovery efforts
- Frame opportunities as "How might we impact [outcome]?"
- Resist jumping to solutions until opportunities are well understood

**Example**:
- BAD: "Ship personalized recommendations feature"
- GOOD: "Increase repeat purchase rate by 15%"

### Habit 3: Use Visual Mapping (Opportunity Solution Trees)
Represent discovery work visually to make team thinking explicit and maintain alignment.

**Key Visual Tools**:
- **Opportunity Solution Trees**: Connect outcome � opportunities � solutions � experiments
- **Experience Maps**: Document current customer journey and pain points
- **Assumption Maps**: Track what you believe vs. what you've validated

**Benefits**:
- Shared understanding across product trio
- Explicit gaps in knowledge become visible
- Easy to communicate with stakeholders
- Historical record of decision-making

### Habit 4: Focus on One Opportunity at a Time
Tackle opportunities incrementally by focusing deeply on one before moving to the next.

**Why Narrow Focus**:
- Prevents analysis paralysis from too many parallel efforts
- Enables deeper understanding through sustained investigation
- Faster learning cycles with concentrated attention
- Clearer cause-and-effect when measuring impact

**Process**:
- Select highest-leverage opportunity from your tree
- Break into sub-opportunities if too large
- Run experiments to address specific sub-opportunities
- Only expand scope after gaining confidence

### Habit 5: Test Assumptions Through Experiments
Use structured experiments to quickly evaluate solutions and de-risk decisions before building production features.

**Experiment Types** (in order of speed/cost):
1. **One-question surveys**: Quick validation of specific beliefs
2. **Prototype tests**: Low-fidelity mockups to test solution viability
3. **Concierge tests**: Manual delivery of automated solution
4. **Wizard of Oz tests**: Fake the backend, test the frontend
5. **Minimum Viable Products**: Simplest shippable version

**Testing Framework**:
- State assumption explicitly: "We believe [customer segment] has [problem] because [evidence]"
- Define success criteria: "We'll know we're right if [observable outcome]"
- Choose fastest/cheapest test that answers the question
- Compare and contrast multiple solutions to reduce bias

## The Product Trio Model

Continuous discovery requires collaboration between three roles:
- **Product Manager**: Outcome ownership, prioritization, business context
- **Designer**: Customer empathy, solution ideation, usability
- **Tech Lead**: Technical feasibility, implementation strategy, constraints

**Trio Dynamics**:
- All three participate in customer interviews (rotating facilitator)
- Shared decision-making on what to build
- Combined expertise reduces blind spots
- Collective accountability for outcomes

## Implementation Steps

### Step 1: Establish Weekly Interview Cadence
- Block recurring calendar time for interviews
- Create systems for recruiting participants (customer database, screeners)
- Develop interview guides focused on understanding opportunities, not pitching ideas
- Set up recording/note-taking process

### Step 2: Define Your Outcome
- Choose one measurable business outcome to focus on
- Ensure it's truly an outcome (behavior change) not output (features)
- Get stakeholder alignment on the target outcome
- Make it visible and frequently referenced

### Step 3: Build Your Opportunity Solution Tree
- Start with your outcome at the top
- Map current understanding of opportunities underneath
- Add solution ideas that could address each opportunity
- Identify experiments to test solutions

### Step 4: Run Your First Experiment Cycle
- Choose highest-priority opportunity from your tree
- Generate 3+ solution ideas for that opportunity
- Design fastest test to compare solutions
- Run experiment and document learnings

### Step 5: Create Feedback Loops
- Weekly team synthesis of interview insights
- Monthly review of progress toward outcome
- Quarterly reflection on discovery process itself
- Continuous refinement of habits

## Practical Applications

### Research Question Examples
- "How do customers currently solve [problem] without our product?"
- "What workarounds have they created to address [pain point]?"
- "When was the last time [outcome we target] happened for you?"
- "Walk me through your decision-making process for [relevant choice]"

### Experiment Examples
- **Landing page test**: Different value props to test message resonance
- **Paper prototype**: Hand-drawn screens to test workflow before coding
- **Concierge**: Manually deliver service to test if customers want it
- **Fake door**: Button for non-existent feature to gauge interest

## Common Pitfalls

### "Research Sprint" Mentality
Doing 10 interviews in one week then none for months. Discovery must be continuous to stay current with customer needs.

### Solution-Focused Interviews
Asking "Would you use this feature?" instead of exploring actual problems. Leads to false positives and confirmation bias.

### Skipping the Trio
PM interviewing alone misses design and engineering perspectives. All three roles bring essential lenses to discovery.

### Analysis Paralysis
Endless opportunity exploration without testing solutions. Balance discovery breadth with decisive experimentation.

## Success Metrics

- **Interview Consistency**: Weeks with 2+ customer interviews / total weeks
- **Outcome Progress**: Movement on target outcome metric
- **Experiment Velocity**: Number of assumption tests run per month
- **Decision Confidence**: % of features backed by experiment data

## Integration with Other Frameworks

**Builds on**:
- Jobs to Be Done: Uncover customer jobs through weekly interviews
- Dual-Track Agile: Discovery and delivery happening concurrently
- Lean Startup: Build-Measure-Learn applied to product discovery

**Pairs with**:
- Opportunity Solution Trees: Primary visual tool for continuous discovery
- The Mom Test: Interview technique for avoiding biased questions
- RICE Prioritization: Decide which opportunities to tackle first

## When to Use

**Best for**:
- Established product teams with delivery cadence
- Organizations committed to outcome-based product development
- Teams that can access customers regularly
- Products with active user base to interview

**Not ideal for**:
- Pre-product startups (no customers to interview yet)
- Teams without access to customers (talk to stakeholders as proxy)
- Pure platform/infrastructure teams (adapt to "customers" = internal teams)

## References
- "Continuous Discovery Habits" - Teresa Torres (2021)
- Product Talk blog - producttalk.org
- Business of Software Conference talk by Teresa Torres
- Continuous Discovery Habits newsletter

## Related
- opportunity-solution-trees
- jobs-to-be-done
- mom-test
- dual-track-agile
- product-trio
- outcome-over-output
- lean-startup
- build-measure-learn