nw-discover

Plan and execute evidence-based product discovery through customer interviews and assumption testing.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-discover-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-discover
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-discover
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-discover-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to validate early product ideas and problem-solution fit without structured customer learning and evidence-based decision making.

Core Features & Use Cases

  • Structured interview framework based on Mom Test principles to surface real pain and avoid bias.
  • Lightweight artifact production (wave decisions, problem validation, lean canvas) to guide downstream DISCOVER and DISCUSS waves.
  • Quick-start guidance for initiating project-wide discovery at the outset of a product concept.

Quick Start

Start by running nw-discover with your product concept to begin customer interviews and assumption testing.

Frequently Asked Questions about nw-discover

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

FAQPage Schema
How do I validate product-market fit through customer interviews without introducing bias?

You validate product-market fit through customer interviews using a structured framework based on Mom Test principles. This approach surfaces real pain points and prevents bias, ensuring your early product concept is evaluated on genuine evidence rather than compliments.

What is assumption testing and when should I start it during product discovery?

Assumption testing is the process of validating problem-solution fit through evidence-based customer learning. You should start it at project initiation across early-stage product concepts to guide interview-driven validation and gather market context before development.

How do I create a lean canvas and wave decisions for early-stage product discovery?

You create a lean canvas and wave decisions by executing lightweight artifact production during the discovery process. These artifacts capture problem validation and market context to formally guide the downstream DISCOVER and DISCUSS waves effectively.

Can I use this assumption testing framework with an existing lean canvas?

Yes, you can integrate this framework with an existing lean canvas. The process produces lightweight artifacts including problem validation and lean canvas updates to ensure your current assumptions are rigorously tested through structured customer interviews.

What is the best way to document formal handoff for the DISCOVER workflow?

The best way to document formal handoff is to generate context files and wave decision artifacts as part of the DISCOVER workflow. This formal handoff documentation captures validated problem-solution fit evidence for downstream execution teams.

Why do I need structured customer learning for early product concepts?

You need structured customer learning because product teams frequently struggle to validate early product ideas and problem-solution fit without it. Evidence-based decision making prevents building solutions based on untested assumptions and market misalignment.