Nw Jtbd Opportunity Scoring

JTBD Opportunity Scoring

Use when prioritizing features, stories, or backlog items based on customer-defined outcomes. Opportunity scoring (Ulwick's ODI) replaces gut-feel prioritization with evidence-based ranking.

Outcome Statements

Every customer need expressed as a desired outcome following strict format:

[Direction] + the [metric] + [object of control] + [contextual clarifier]

• Direction: "Minimize" or "Maximize"
• Metric: time, likelihood, number, or frequency

Examples

• "Minimize the time it takes to identify the root cause of a production issue"
• "Minimize the likelihood of deploying untested code to production"
• "Maximize the likelihood that acceptance criteria cover all relevant scenarios"
• "Minimize the number of iterations needed to reach shared understanding"
• "Minimize the frequency of false positive alerts during monitoring"

Quality Checks

Outcome statement must be: Solution-free (no specific technology) | Measurable (ratable on importance/satisfaction 1-5) | Controllable (customer can assess improvement) | Unambiguous (same interpretation by all stakeholders)

Deriving Outcome Statements

Walk the 8-step job map (see jtbd-core skill) and generate 2-3 per step. Produces 16-24 outcome statements per job -- comprehensive view of customer needs.

The Opportunity Algorithm

Opportunity Score = Importance + max(0, Importance - Satisfaction)

Where:

• Importance = % of respondents rating outcome 4 or 5 on 1-5 scale
• Satisfaction = % of respondents rating current satisfaction 4 or 5 on 1-5 scale
• Score range: 0-20 (higher = greater opportunity)

How It Works

Rewards outcomes both important and unsatisfied. If satisfaction >= importance, second term is zero (appropriately served). If satisfaction < importance, gap amplifies score (underserved).

Score Interpretation

Applying to Feature Prioritization

Step 1: Generate Outcome Statements

From job mapping and interview findings, compile 15-30 per major job.

Step 2: Rate Importance and Satisfaction

Gather ratings from users/stakeholders. For small teams:

• Interview 5-10 users directly
• Use internal team ratings as proxy (mark as "team estimate" vs "user data")
• Leverage support tickets, feature requests, bug reports as signals

Step 3: Calculate and Rank

Compute scores, sort descending. Top scores = highest-priority features.

Step 4: Map to Stories

Each high-scoring outcome maps to one or more stories. Score 15+ should produce at least one story in current iteration.

Step 5: Identify Overserved Areas

Scores below 10 are simplification candidates. Resources on overserved outcomes are better redirected to underserved ones.

Opportunity Scoring Matrix Template

## Opportunity Scoring: [Product/Feature Area]

| # | Outcome Statement | Imp. (%) | Sat. (%) | Score | Priority |
|---|-------------------|----------|----------|-------|----------|
| 1 | Minimize the time to [outcome A] | | | | |
| 2 | Minimize the likelihood of [outcome B] | | | | |
| 3 | Maximize the [quality] when [context C] | | | | |

### Scoring Method
- Importance: % of respondents rating 4+ on 5-point scale
- Satisfaction: % of respondents rating 4+ on 5-point scale
- Score: Importance + max(0, Importance - Satisfaction)
- Priority: Extremely Underserved (15+), Underserved (12-15),
  Appropriately Served (10-12), Overserved (<10)

### Top Opportunities (Score >= 12)
1. [Outcome] -- Score: [X] -- Story: [link or title]
2. [Outcome] -- Score: [X] -- Story: [link or title]

### Overserved Areas (Score < 10)
1. [Outcome] -- Score: [X] -- Simplification opportunity: [description]

### Data Quality Notes
- Source: [user interviews / team estimates / support ticket analysis]
- Sample size: [N respondents]
- Confidence: [High if N >= 10 with user data, Medium if team estimates]

Worked Example

Context: CLI tool for deploying applications. 8 users surveyed.

Prioritization result:

1. Root cause identification (14.9) -- build better deployment diagnostics
2. Rollback speed (14.0) -- invest in one-command rollback
3. Environment misconfiguration (11.5) -- incremental improvements to validation
4. Untested code prevention (10.4) -- maintain current pre-deploy checks
5. Onboarding time (9.0) -- consider simplifying; current docs may be over-engineered

Small-Team Adaptations

Ulwick's methodology assumes large-scale surveys (100+ respondents). For small agile teams:

• 5-10 interviews sufficient for directional signals. Treat scores as relative rankings, not absolute.
• Support tickets as proxy data: High-frequency complaints = high importance + low satisfaction.
• Team consensus estimation: When user access limited, rate collectively. Document as "team estimate."
• Iterate: Re-score after each release as satisfaction shifts.

Integration with Other Prioritization Methods

Cross-References

• For core JTBD theory and job map steps: load jtbd-core skill
• For interview techniques to gather importance/satisfaction data: load jtbd-interviews skill
• For translating high-priority outcomes to BDD scenarios: load jtbd-bdd-integration skill
• For story-level prioritization (MoSCoW, Value/Effort): load leanux-methodology skill

Source: nWave-ai/nWave → nWave/skills/nw-jtbd-opportunity-scoring/SKILL.md

Also appears in: nWave-ai/nWave/plugins/nw/skills/nw-jtbd-opportunity-scoring/SKILL.md