continuous-discovery

Malicious tool definition detected

Tool: SKILL.md [1/3] Description: --- name: continuous-discovery description: 'Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots.

Tool: SKILL.md [2/3] Description: | Context | Application | Example | |---------|-------------|---------| | Weekly cadence | Schedule three 30-minute interviews every Thursday | Recruit from existing users via in-app prompt; rotate who leads the conversation | | Opportunity discovery | Extract customer needs from interview stories and add to the OST | User describes workaround for exporting data -- becomes an opportunity node | | Team alignment | Share snapshots in a visible location so everyone

Tool: SKILL.md [3/3] Description: ask for evidence in planning discussions | "What did you learn from interviews this week?" becomes a standing question in 1:1s | **Ethical boundary:** Respect participant time.

Malicious tool definition detected

Tool: references/assumption-mapping.md [1/3] Description: # Assumption Mapping A detailed guide to identifying, categorizing, prioritizing, and testing the assumptions that underlie product decisions, so teams invest in building only what evidence supports.

Tool: references/assumption-mapping.md [2/3] Description: | Principle | What It Means | Anti-Pattern | |-----------|---------------|-------------| | **Fast** | Complete in days, not weeks | 3-month A/B test for a single assumption | | **Cheap** | Minimal resource investment | Building the full feature to "test" it | | **Specific** | Tests one assumption at a time | Test that conflates desirability with usability | | **Falsifiable** | Could produce a negative result | Test designed to only confir

Tool: references/assumption-mapping.md [3/3]

Malicious tool definition detected

Tool: references/case-studies.md [2/3] Description: workout (feeling: good during, but uncertain if it was the "right" choice) ### Opportunity Solution Tree ``` Outcome: Increase 7-day retention from 25% to 40% │ ├── "I can't decide which workout to do today" ← FOCUS │ ├── "I don't know what's appropriate for my fitness level" │ ├── "I don't have a plan -- every day feels like starting over" │ └── "There are too many options and I'm overwhelmed" │ ├── "I lose motivation when I don't see progress

Tool: references/case-studies.md [3/3] Description: split their interview cadence: - **Tuesdays:** Interview a registered buyer who hadn't purchased yet (recruited via email: "We noticed you signed up but haven't found anything yet -- can we learn why?") - **Thursdays:** Interview a buyer who did make their first purchase within 30 days (recruited via post-purchase email) This contrast was powerful. By interviewing both converters and non-converters, the team could identify what was different ab

Malicious tool definition detected

Tool: references/experience-mapping.md [2/3] Description: peak on the map and translate them into opportunity statements for the OST.

Tool: references/experience-mapping.md [3/3] Description: process of export-attach-email; no tracking of whether client received it **Step 4 -- Wait for payment** - Doing: Checking bank account, checking email for confirmation - Thinking: "Did they get it?

Malicious tool definition detected

Tool: references/interview-snapshots.md [1/3] Description: # Interview Snapshots A practical guide to conducting story-based customer interviews, capturing insights in a standardized snapshot format, and building a sustainable weekly interview cadence.

Tool: references/interview-snapshots.md [2/3] Description: team to acknowledge what they didn't know. ## Synthesizing Across Interviews Individual interviews tell stories.

Tool: references/interview-snapshots.md [3/3]

Malicious tool definition detected

Tool: references/opportunity-trees.md [1/2] Description: # Opportunity Solution Trees A comprehensive guide to building, maintaining, and using Opportunity Solution Trees (OSTs) as the central artifact of continuous product discovery. ## What Is an Opportunity Solution Tree?

Tool: references/opportunity-trees.md [2/2] Description: being built - Stakeholders can look at the tree and understand the team's strategy - The tree has changed meaningfully in the last month ### Signs Your Tree Is Dying - No new opportunities have been added in two or more weeks - The tree was created once and lives in a forgotten document - Solutions were added without connecting to a customer opportunity - The team can't explain the relationship between their current work and the tree - Opp

Malicious tool definition detected

Tool: references/prioritization-methods.md [1/3] Description: # Prioritization Methods A guide to structured methods for comparing and ranking opportunities on the Opportunity Solution Tree, so product teams focus on the highest-leverage bets backed by evidence. ## Why Structured Prioritization Matters Without a structured approach, teams default to prioritizing by: - **HiPPO** (Highest Paid Person's Opinion) -- the loudest voice wins - **Recency bias** -- whatever the last customer said becomes

Tool: references/prioritization-methods.md [2/3] Description: │ DO FIRST │ BIG BETS │ │ (quick │ (worth the │ │ wins) │ investment)│ │ │ │ LOW ─┼────────────┼────────────┼── HIGH EFFORT│ │ │ EFFORT │ FILL-INS │ AVOID │ │ (do if │ (high cost,│ │ capacity │ low return│ │ allows) │ │ └────────────┼────────────┘ │ LOW IMPACT ``` ### Using It Well **Impact estimation:** Base impact on customer evidence, not team opinion. An opportunity mentioned in 10 interviews with strong emotional language has hig

Tool: references/prioritization-methods.md [3/3] Description: invalidated ### Quarterly - Strategic review of the outcome itself -- is this still the right outcome?