discovery-interview-guide
$
npx mdskill add mohitagw15856/pm-claude-skills/discovery-interview-guideDesign interviews that surface genuine insight — not validation of what you already believe. Every guide follows a story-based, past-behaviour-focused structure.
SKILL.md
.github/skills/discovery-interview-guideView on GitHub ↗
---
name: discovery-interview-guide
description: "Create a structured user discovery interview guide with screener questions, a discussion guide, and a synthesis framework. Use when planning user interviews, customer discovery sessions, Jobs-to-be-Done research, or problem validation. Produces a complete guide covering warm-up, problem exploration, and a per-session synthesis template."
---
# Discovery Interview Guide Skill
Design interviews that surface genuine insight — not validation of what you already believe. Every guide follows a story-based, past-behaviour-focused structure.
## Core Principles
1. **Never ask about the future.** "Would you use X?" tells you nothing. "Tell me about the last time you did X" tells you everything.
2. **Interview for behaviour, not opinion.** Opinions are cheap. Behaviour is evidence.
3. **The 5 Whys.** Every surface answer is a door. Keep opening doors.
4. **Confirm the problem before exploring the solution.** Never show a prototype until you've confirmed the pain exists unprompted.
## Interview Structure (60 minutes standard)
### 1. Warm-Up (5 min)
Build rapport. Get them talking. Don't discuss the topic yet.
- "Tell me a bit about your role and what a typical week looks like for you."
- "What tools do you rely on most day-to-day?"
### 2. Context Setting (10 min)
Understand their world before diving into the problem space.
- "Walk me through how you currently [handle the domain area]."
- "What does that process look like from start to finish?"
- "Who else is involved when you do this?"
### 3. Problem Exploration (25 min) — THE CORE
Surface pain without leading.
- "Tell me about the last time you had to [relevant task]. What happened?"
- "What was the hardest part of that?"
- "How did you handle it?"
- "What did you try before settling on that approach?"
- "What does it cost you when this goes wrong?" (time, money, stress, reputation)
- "If you could wave a magic wand and change one thing about this process, what would it be?"
⚠️ **Do not mention your product or feature during this phase.**
### 4. Current Solutions (10 min)
Understand the competitive landscape from their perspective.
- "What tools or workarounds do you use today for this?"
- "What do you like about [current solution]? What frustrates you?"
- "Have you tried other approaches? What happened?"
### 5. Wrap-Up (10 min)
- "Is there anything about this topic we haven't covered that you think I should know?"
- "Is there anyone else you'd recommend I speak to?"
- "Would you be open to a follow-up if I have more questions?"
---
## Output Format
### Discovery Interview Guide — [Topic] — [Date]
**Research Goal:** [One sentence: what decision will this research inform?]
**Target Participant Profile:** [Role, company size, behaviour qualifier]
**Screener Questions** (for recruiting):
1. [Question] → Must answer: [Y/N or specific]
2. [Question] → Must answer: [Y/N or specific]
3. [Disqualifier question] → Disqualify if: [answer]
**Interview Guide:**
[Full structured guide using the format above, customised to the specific research topic]
**Synthesis Template** (fill after each interview):
- Key quote: "[verbatim]"
- Core pain: [1 sentence]
- Current workaround: [what they're doing today]
- Intensity (1–5): [how painful is this?]
- Surprise/unexpected finding: [anything that challenged your assumptions]
**Pattern Detection** (after 5+ interviews):
- Pain mentioned by [X/N] participants: [theme]
- Workaround used by [X/N] participants: [theme]
- Most emotionally charged moment in interviews: [observation]
---
## Required Inputs
Ask the user for these if not provided:
- **Research topic or question** (what decision will this inform?)
- **Target participant profile** (role, behaviour, company type)
- **Session length** (30 / 45 / 60 / 90 minutes)
- **Number of interviews planned**
- **Known hypotheses to test or avoid confirming prematurely** (optional)
## Quality Checks
- [ ] No future-tense questions ("would you...") — only past-behaviour questions
- [ ] Product or solution not mentioned until after pain is confirmed
- [ ] Questions open-ended (cannot be answered yes/no)
- [ ] Synthesis template included for per-session notes
- [ ] Screener questions identify and disqualify wrong participants
## Guidelines
- Recommend 5–8 interviews to reach thematic saturation for most discovery questions
- Always record with permission — transcripts beat notes
- If user is new to interviewing: remind them to stay silent after asking a question (aim for 80/20 participant-to-interviewer talking ratio)
- Never synthesise during the interview — do it after, when you can look across sessions
- Flag confirmation bias: if user writes questions that lead toward a predetermined answer, rewrite them as open-ended alternatives
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.