Job Story
A requirements format from JTBD that focuses on the situation and motivation rather than the user persona, using 'When... I want to... So I can...' structure.
Also known as: JTBD Story, Situation-Motivation-Outcome
Category: Techniques
Tags: requirements, products, customer-research, agile, frameworks
Explanation
Job Stories are an alternative to traditional User Stories that emerged from the Jobs to Be Done framework. Developed by Alan Klement and the Intercom team, they shift focus from user personas to the situation and motivation driving behavior.
**The Format**:
When [situation],
I want to [motivation],
So I can [expected outcome].
**Example Comparison**:
*User Story*: "As a premium subscriber, I want to download videos, so that I can watch offline."
*Job Story*: "When I'm commuting on a train with poor connectivity, I want to have my content ready, so I can continue learning without interruption."
**Why Job Stories Work Better**:
1. **Situation > Persona**: The same person behaves differently in different situations. A "premium subscriber" behaves differently commuting vs. at home. Situation captures this context.
2. **Motivation > Feature**: "Download videos" is a solution, not the job. The job is "continue learning without interruption." Job Stories keep focus on the underlying need.
3. **Outcome > Benefit**: "So I can" forces clarity on what success looks like, preventing feature creep.
**When to Use Job Stories**:
- Designing new features (understand the triggering situation)
- Prioritizing work (which situations matter most?)
- Evaluating solutions (does this actually help in that situation?)
- User research (interview about situations, not preferences)
**Writing Good Job Stories**:
- Be specific about the situation (time, place, constraints)
- Focus on emotional and functional motivations
- Make outcomes measurable when possible
- Avoid embedding solutions in the motivation
**Job Stories vs User Stories**:
| Aspect | User Story | Job Story |
|--------|------------|------------|
| Focus | Who (persona) | When (situation) |
| Risk | Persona assumptions | Situation assumptions |
| Strength | Role clarity | Context clarity |
| Best for | Role-based systems | Behavior-driven design |
Job Stories complement User Stories rather than replacing them—use the format that best captures the insight.
Related Concepts
← Back to all concepts