Skip to content
cccskills
FreePublished on GitHub

nw-opportunity-mapping

Opportunity Solution Trees, opportunity scoring, Lean Canvas, JTBD job mapping, and technique selection guide

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Opportunity Mapping

Opportunity Solution Tree (OST)

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

Building the OST

  1. Define desired outcome from customer research
  2. Map opportunities from interview insights (min 5 distinct)
  3. Score each using Opportunity Algorithm
  4. Generate solution ideas for top 2-3
  5. Seek real diversity in solutions (avoid variations of same idea)

Opportunity Scoring Algorithm

Formula: Score = Importance + Max(0, Importance - Satisfaction) Importance: 1-10 | Satisfaction: 1-10 | Max score: 20

ScoreMeaningAction
>8High importance, satisfaction gap -- underservedPursue
5-8Moderate importance or partially servedEvaluate
<5Low importance or well-servedDeprioritize

Process: gather importance + satisfaction from 5+ interviews, calculate per opportunity, rank, select top 2-3.

Job Mapping (JTBD)

Universal Job Map Steps

StepGoalOutcome Format
DefineDetermine what needs doingMinimize time to identify [object]
LocateFind inputs/informationMinimize time to gather [resources]
PrepareReady inputs for useMinimize likelihood of missing [requirements]
ConfirmVerify readinessMinimize likelihood of incorrect [categorization]
ExecutePerform core taskMinimize time from [start] to [completion]
MonitorTrack progressMinimize uncertainty about [status]
ModifyAdjust if neededMinimize effort to correct [issues]
ConcludeComplete the jobMinimize 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"

Lean Canvas

One-page business model for Phase 4 viability validation.

  1. Problem: Top 3 problems (Phase 1 validated) | 2. Customer Segments: by JTBD
  2. UVP: single clear message | 4. Solution: top 3 features for top problems
  3. Channels: path to customers (Phase 4 validated) | 6. Revenue Streams: monetization
  4. Cost Structure: key costs | 8. Key Metrics: activity metrics
  5. Unfair Advantage: not easily copied

4 Big Risks

RiskQuestionValidation
ValueWill customers want this?Interviews, fake doors
UsabilityCan customers use this?Prototype testing, task completion
FeasibilityCan we build this?Spikes, expert review
ViabilityBusiness model works?Lean Canvas, stakeholder review

Technique Selection Guide

GoalTechniques
Validate problemMom Test, Job Mapping
Understand needsOutcome Statements, Opportunity Mapping
Prioritize opportunitiesOST, Opportunity Algorithm
Generate solutionsIdeation with OST constraints
Validate solution valueHypothesis Testing, Prototypes
Test usabilityPrototype testing, Task completion
Assess feasibility4 Risks, Spikes
Structure business modelLean Canvas
Continuous learningWeekly customer touchpoints

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

See all skills by nWave-ai

Report a problem with this skill