# Job Story

A contextual requirements statement that connects a triggering situation, a person’s motivation, and the outcome they seek without relying on demographic personas.

- Type: artifact
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/job-story/>)

## What it means

A job story frames product behavior around causality and context. It commonly follows “When \[situation\], I want to \[motivation\], so I can \[expected outcome\].” Unlike a conventional user story centered on a role, it emphasizes the circumstances that create demand and the progress a person is trying to make.

## Why it matters

The same person can need different things in different situations, while people with different demographics may pursue the same outcome. Job stories direct attention toward triggers, anxieties, trade-offs, and desired progress, helping teams explore multiple solutions rather than attaching a feature to a broad persona label.

## When to use it

Use job stories when situational context strongly shapes behavior, when persona-based stories feel generic, or when research reveals a clear struggle and desired outcome. They are especially useful in discovery and interaction design. Pair them with acceptance criteria when work moves toward implementation.

## How it works

1. Research recent real situations, including triggers, current alternatives, constraints, and anxieties.
2. Describe the situation precisely enough to explain why the need becomes active.
3. State the motivation and desired progress without embedding a preferred feature.
4. Explore solutions and identify which assumptions or risks require testing.
5. Add examples and acceptance criteria that preserve the job while guiding delivery.

## A practical example

A finance team writes: “When I notice an unfamiliar card charge while away from home, I want to understand and control it immediately, so I can protect my money without blocking legitimate travel spending.” This opens options beyond a generic “freeze card” feature and highlights reassurance, verification, and recovery.

## Where it breaks

Job stories can become invented narratives if they are not grounded in observed behavior. The format may underrepresent enduring accessibility needs, organizational roles, permissions, or relationships between actors. Not every requirement has a meaningful situational trigger, and delivery still needs testable detail.

## Common mistakes

- Writing a hypothetical context that has not been supported by research.
- Placing the desired interface or feature inside the motivation clause.
- Ignoring important actor characteristics merely because the format deemphasizes personas.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/job-story/#visualization-job-story>)

## Sources

1. [Designing Features Using Job Stories](<https://www.intercom.com/blog/using-job-stories-design-features-ui-ux/>) — Intercom · Creator-authored guide
2. [How We Accidentally Invented Job Stories](<https://www.intercom.com/blog/accidentally-invented-job-stories/>) — Intercom · Origin account

## Related topics

- [User Story](<https://wiki.soroush.uk/topic/user-story/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
