AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

product-discovery

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

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--product-discovery at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 2

references/discovery-frameworks.md

Discovery Frameworks

Opportunity Solution Tree (OST)

Purpose: continuously connect product outcomes to validated opportunities and tested solutions.

Core structure:

  • Outcome (metric)
  • Opportunity nodes (needs/pains)
  • Solution ideas
  • Experiments

OST practice tips:

  • Keep tree live; update after each interview or test.
  • Separate opportunity evidence from solution proposals.
  • Avoid single-branch trees that force one solution.

Jobs-to-be-Done (JTBD)

Use JTBD to understand progress users seek.

JTBD template: "When [situation], I want to [motivation], so I can [expected outcome]."

JTBD interview focus:

  • Trigger moments
  • Current alternatives and workarounds
  • Purchase/adoption anxieties
  • Desired progress and success criteria

Kano Model

Classify features by impact on satisfaction:

  • Must-be: expected baseline features
  • Performance: more is better
  • Delighters: unexpected value multipliers
  • Indifferent: low impact
  • Reverse: can reduce satisfaction for some users

Use Kano when prioritizing solution concepts after problem validation.

Design Sprint Methodology

Typical phases:

  1. Understand
  2. Sketch
  3. Decide
  4. Prototype
  5. Test

Discovery usage:

  • Compress learning cycle into one week.
  • Best for high-ambiguity opportunities requiring cross-functional alignment.

Assumption Prioritization Matrix

Map assumptions on two axes:

  • Risk if wrong (low -> high)
  • Certainty (low -> high)

Priority order:

  1. High risk, low certainty (test first)
  2. High risk, high certainty (validate quickly)
  3. Low risk, low certainty (defer)
  4. Low risk, high certainty (document)

Discovery Evidence Rules

  • One source is not enough for major decisions.
  • Triangulate qualitative and quantitative signals.
  • Predefine decision criteria before test execution.
  • Archive evidence with date, segment, and method.