Nw Jtbd Analysis

JTBD Analysis

Core Principle

A job is the progress a person is trying to make in a particular circumstance. Jobs are stable over time — technology changes, jobs don't. People hire products to make progress; they fire them when they fail.

The trap: Feature requests describe a proposed solution, not the underlying job. Always extract the job first.

Job Statement Format

Copy code
When [situation/trigger], I want to [motivation/action], so I can [expected outcome]

Examples (good):

• "When I'm hosting a virtual networking event, I want to facilitate natural conversations between strangers, so I can create valuable connections that wouldn't happen otherwise."
• "When I join an event as a participant, I want to quickly find relevant people to talk to, so I can maximize the value of my limited time."

Job Types — Extract All Three

Abstraction Layers — Navigate to the Real Job

Jobs usually live at strategic or physical level, not tactical.

Navigation rules:

• Use "why?" to move up layers
• Use "how?" to move down layers
• Stop when further "why?" produces a life-goal answer

First-Principles Extraction — 3-Step Inversion

When a feature request is presented as a job, apply this:

1. Identify the Activity — What visible action is the user performing?

   • e.g., "User brainstorms on a whiteboard"

2. Reject the Activity as the Job — Does anyone wake up wanting to do this activity?

   • "Nobody wakes up wanting to brainstorm" → the job is deeper

3. Strip to Irreducible Function — What remains if all tools and methods are removed?

   • e.g., "Reduce uncertainty via input-synthesis-convergence"

Disruption check: Is there a higher-level job that would make this entire job unnecessary?

ODI Outcome Statements — Measurable Success Criteria

Format: [Direction] + [Metric] + [Object] + [Context]

Direction: Always "Minimize" (95% of time). "Maximize" only when more is genuinely better.

Metrics priority:

1. the time it takes to — speed/efficiency (preferred)
2. the likelihood of — avoiding occurrences
3. the likelihood that — avoiding results
4. the number of — quantity reduction
5. the effort required to — ease

Good vs bad examples:

Forbidden words: easy, reliable, good, better, effective, efficient, manage, handle, deal with. Forbidden patterns: solution references ("using AI", "via the app"), compound statements with "and"/"or", demographics.

Opportunity Scoring

Formula: Score = Importance + Max(0, Importance - Satisfaction)

Where Importance and Satisfaction are surveyed 1-10.

Output format per opportunity:

Copy code
| Outcome | Importance | Satisfaction | Score | Status |
|---------|------------|--------------|-------|--------|
| Minimize time to find relevant attendees | 9.2 | 4.1 | 14.3 | Under-served |

DIVERGE Output for JTBD Phase

Produce docs/feature/{feature-id}/diverge/job-analysis.md with:

1. Raw request — verbatim feature/problem statement received
2. Job extraction — 5 Why chain from tactical to physical/strategic level
3. Job statements — functional (required) + emotional + social (if identifiable)
4. Disruption check — Is there a higher-level job this entire job is serving?
5. Outcome statements — 3-6 measurable ODI-format statements
6. Opportunity candidates — Which outcomes appear most under-served?

Gate: Job must be at strategic or physical abstraction level. Tactical-level jobs are not acceptable input for brainstorming — elevate first.