Jobs Stories are an alternative to user stories that focus on the situation that triggers the need rather than the persona. By starting with context, they keep the solution space open and ground feature decisions in real user motivation.
As a replacement or complement to user stories, particularly during ideation when you want to avoid premature solution commitment.
- Identify the trigger situation from your JTBD research
- Write: 'When [specific situation], I want to [motivation/action], so I can [expected outcome]'
- Avoid describing the solution in the 'want to' section — keep it open
- Use jobs stories as the brief for design and development
- One jobs story per feature or interaction — keep them small and specific
'When I'm at the gym and need energy without interruption, I want the music to match my pace automatically, so I can stay in the zone without touching my phone.' This is richer than 'As a gym user, I want a workout playlist' — it opens solutions including BPM-matching, auto-queue, and hands-free controls.
Please contact the author for more information on these examples at linkedin.com/in/kshitijrege
- Writing the solution into the 'want to' clause — keep it about motivation, not mechanism
- Making the situation too vague — 'when I use the product' is not a trigger situation
- Skipping the 'so I can' clause — it defines the real measure of success
- When Coffee and Kale Compete — Alan Klement