Job Stories
Synonyms: Job Story, JTBD Story, Jobs-to-Be-Done Story, Context-Based User Story, Situation-Based Story
Definition
Use cases
- Feature design: When a user forgets a password, they want to regain access quickly, so they can continue using their account.
- Checkout design: When a shopper is unsure whether an order went through, they want confirmation, so they can avoid paying twice.
- Product discovery: When someone needs to compare several apartments, they want to see prices and locations together, so they can choose a suitable place.
How it's used in practice
- Interview users about specific situations in which they needed help or tried to complete a task.
- Identify the trigger, motivation, and expected outcome from their answers.
- Write each job story using the 3-part format.
- Check that the motivation describes a need, not a proposed feature.
- Use the stories to guide design ideas, requirements, and usability tests.
Challenges & limitations
- Weak research: Stories based on assumptions may describe needs that users don't have.
- Vague situations: "When I use an app" gives the team little context for making design decisions.
- Missing user differences: Job stories may overlook differences in ability, experience, or access when those details affect the task.
Free resources
- Intercom: How We Accidentally Invented Job Stories — explains where job stories came from and why Intercom focused on situations, motivations, and outcomes.
- 24 ways: Jobs-to-Be-Done in Your UX Toolbox — explains how job stories fit into UX research and product design.
