asb-interview-learning

Synthesizes customer interview debriefs into evidence-cited hypothesis updates and a stop-or-continue verdict.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-interview-learning-evanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asb-interview-learning
Source: https://github.com/evanish/reusable-PM-templates/tree/main/Templates%20to%20reuse/Work/asb-customer-discovery/asb-interview-learning
Command: npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-interview-learning-evanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running customer discovery interviews, teams struggle to turn scattered notes into disciplined learning: hypotheses go unupdated, single anecdotes get over-weighted, and nobody decides when to stop interviewing. This Skill reads per-interview debrief files against your working HYPOTHESES.md and QUESTIONS.md and walks you through evidence-cited updates one proposal at a time. ## Core Features & Use Cases - Three-tier update rule: Distinguishes stray voices (parked in a 'That's funny' watch section), patterns (which validate, tune, or disprove hypotheses), and revelations (single voices that legitimately reframe a belief). - One-proposal-at-a-time walk: Every change is proposed with quoted evidence from named debrief files, decided by the user, applied immediately, and recorded in a mandatory change log with frozen hypothesis/question numbering. - Closing verdict: Ends each synthesis with a committed continue (with focus and number), stop-and-act, or re-aim decision based on surprise rate and convergence. - Use Case: You have nine interview debriefs in an interviews/ folder. Run this Skill to validate H2, tune H3's pricing threshold, mark H7 disproved, add a new hypothesis with a matching interview question, and get a verdict to continue with five more freelancer interviews. ## Quick Start Ask the assistant to synthesize the interview debriefs in your interviews folder against HYPOTHESES.md and QUESTIONS.md and tell you whether to keep interviewing.

Frequently Asked Questions about asb-interview-learning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synthesize customer interview notes into hypothesis updates?

Collect one debrief file per interview mapping answers to question numbers, then run the synthesis over that directory against your HYPOTHESES.md and QUESTIONS.md. Each proposed change is presented one at a time with quoted evidence, and you accept, adjust, or reject it before it is applied and logged.

How many customer interviews before I can claim a pattern?

Pattern claims require several interviews telling the same story; one or two debriefs can only produce revelations or 'That's funny' watch items, never pattern-level hypothesis changes. At shallow depth the closing verdict is presumptively to continue interviewing.

When should I stop doing customer discovery interviews?

Stop when the surprise rate falls and core hypotheses on pain, coping, and money converge to stable resolutions. If five more identical conversations would change no decision, the verdict is stop and act; diverging answers with no center indicate re-aiming instead.

Can I use raw interview transcripts instead of debrief files?

No, raw transcripts are declined because synthesis over them skips the recording discipline of answer mapping, verbatim vocabulary, and guru flags. Each conversation should first be recorded as a brief debrief file, then synthesized.

What happens to disproved hypotheses in the file?

Disproved hypotheses stay in HYPOTHESES.md, struck through and marked with the date and what reality said, because a disproven belief is itself a finding. Their numbers are never reused, and every change gets a one-line entry in the change log.