From nw
Builds Opportunity Solution Trees, scores opportunities via importance-satisfaction formula, maps JTBD jobs, and fills Lean Canvas for product discovery and prioritization.
npx claudepluginhub nwave-ai/nwave --plugin nwThis skill uses the workspace's default tool permissions.
Connects desired outcomes to opportunities to solution ideas:
Builds Opportunity Solution Trees (OST) mapping outcomes to customer opportunities, solutions, and experiments. Guides continuous product discovery and prioritization.
Use this skill when the user asks about "opportunity solution tree", "OST", "Teresa Torres framework", "build my OST", "map opportunities to solutions", "how should we structure our discovery", "connect outcomes to opportunities", "continuous discovery framework", or wants to visually structure the relationship between outcomes, opportunities, and solutions. Also use this skill when a user has a list of ideas and wants to organize them against user outcomes.
Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions. Use for outcome-driven product discovery, prioritization, or communicating product strategy.
Share bugs, ideas, or general feedback.
Connects desired outcomes to opportunities to solution ideas:
Desired Outcome
|
+-- Opportunity 1 (score)
| +-- Solution Idea A
| +-- Solution Idea B
|
+-- Opportunity 2 (score)
| +-- Solution Idea C
|
+-- Opportunity 3 (score)
+-- Solution Idea D
+-- Solution Idea E
Formula: Score = Importance + Max(0, Importance - Satisfaction) Importance: 1-10 | Satisfaction: 1-10 | Max score: 20
| Score | Meaning | Action |
|---|---|---|
| >8 | High importance, satisfaction gap -- underserved | Pursue |
| 5-8 | Moderate importance or partially served | Evaluate |
| <5 | Low importance or well-served | Deprioritize |
Process: gather importance + satisfaction from 5+ interviews, calculate per opportunity, rank, select top 2-3.
| Step | Goal | Outcome Format |
|---|---|---|
| Define | Determine what needs doing | Minimize time to identify [object] |
| Locate | Find inputs/information | Minimize time to gather [resources] |
| Prepare | Ready inputs for use | Minimize likelihood of missing [requirements] |
| Confirm | Verify readiness | Minimize likelihood of incorrect [categorization] |
| Execute | Perform core task | Minimize time from [start] to [completion] |
| Monitor | Track progress | Minimize uncertainty about [status] |
| Modify | Adjust if needed | Minimize effort to correct [issues] |
| Conclude | Complete the job | Minimize time from [completion] to [result] |
Outcome statement format: [Direction] + [Metric] + [Object] + [Clarifier] Example: "Minimize the time it takes to identify which project budget a new expense should be allocated to"
One-page business model for Phase 4 viability validation.
| Risk | Question | Validation |
|---|---|---|
| Value | Will customers want this? | Interviews, fake doors |
| Usability | Can customers use this? | Prototype testing, task completion |
| Feasibility | Can we build this? | Spikes, expert review |
| Viability | Business model works? | Lean Canvas, stakeholder review |
| Goal | Techniques |
|---|---|
| Validate problem | Mom Test, Job Mapping |
| Understand needs | Outcome Statements, Opportunity Mapping |
| Prioritize opportunities | OST, Opportunity Algorithm |
| Generate solutions | Ideation with OST constraints |
| Validate solution value | Hypothesis Testing, Prototypes |
| Test usability | Prototype testing, Task completion |
| Assess feasibility | 4 Risks, Spikes |
| Structure business model | Lean Canvas |
| Continuous learning | Weekly customer touchpoints |