continuous-discovery

Solid

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

Testing & QA 1,169 stars 127 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Continuous Discovery Habits Framework Framework for building a sustainable, weekly practice of customer discovery that keeps product teams making progress toward desired outcomes. Rather than treating discovery as a phase that happens before development, this framework embeds customer learning into the ongoing rhythm of product work so that every decision is informed by fresh evidence. ## Core Principle **Good product discovery requires a continuous cadence, not a one-time event.** Teams that talk to customers every week, map opportunities visually, and test assumptions before building consistently outperform teams that rely on intuition, stakeholder opinions, or quarterly research cycles. The goal is at least one customer touchpoint per week, every week, by the product trio (product manager, designer, engineer). ## Scoring **Goal: 10/10.** When reviewing or creating a product discovery practice, rate it 0-10 based on adherence to the principles below. A 10/10 means the team has a weekly interview cadence, maintains a living Opportunity Solution Tree, systematically tests assumptions, and uses evidence to decide what to build. Lower scores indicate gaps in cadence, structure, or rigor. Always provide the current score and specific improvements needed to reach 10/10. ## Framework ### 1. Opportunity Solution Trees **Core concept:** An Opportunity Solution Tree (OST) is a visual map that connects a desired outcome at the top to customer opportunities in the middle and ...

Details

Author
wondelai
Repository
wondelai/skills
Created
4 months ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

continuous-discovery-habits

Product discovery framework based on Teresa Torres' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing assumption tests before committing to a feature, (4) writing or critiquing interview snapshots from customer conversations, (5) generating multiple solution candidates for an opportunity (especially with How Might We), (6) mapping a current-state customer experience or journey to surface unmet needs, (7) diagnosing why a product team is shipping without moving outcomes, (8) running a discovery pre-mortem before committing to a solution branch, (9) building or strengthening a weekly customer-interview habit, (10) connecting business outcomes to product outcomes to opportunities to solutions in a single coherent tree.

0 Updated 3 days ago
tomaszstaniak
AI & Automation Listed

product-discovery-coach

Coaches a product trio through continuous product discovery: weekly customer touchpoints, assumption mapping, story mapping, and the discovery / delivery dual-track cadence. Use when standing up a discovery practice from scratch, debugging why discovery isn't sticking, training a new product manager on continuous discovery, or designing a quarterly discovery plan around an outcome.

1 Updated today
varunk130
Web & Frontend Solid

opportunity-solution-tree

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.

11,809 Updated 1 weeks ago
phuryn
AI & Automation Solid

product-discovery

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.

16,782 Updated 3 days ago
alirezarezvani
AI & Automation Solid

inspired-product

Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "product roadmap", "opportunity assessment", "product vision", "product-led growth", or "discovery vs delivery". Also trigger when restructuring product teams away from output-driven models, setting product strategy, or defining what to build next based on outcomes. Covers product discovery techniques, team structure, and continuous value delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.

1,169 Updated 2 weeks ago
wondelai