Why Job Stories are better than User Stories (and how to use them)

What are Job Stories and how do they differ from User Stories?

Job Stories are, just like user stories, a way to describe user wishes or needs. But instead of focusing on 'As a [user], I want [action], so that [reason]', job stories start from the situation, the motivation, and the desired outcome. This emphasis on context and motivation provides a clearer understanding of why someone has a particular 'job to be done'. User stories often focus on personas and roles, while job stories are based on a problem or task the user wants to accomplish.

‍

Example: User Story vs. Job Story

• User Story: “As a traveler, I want to book a hotel, so that I can stay overnight at my destination.”
• Job Story: “When I travel and visit an unfamiliar city, I want to quickly find reliable and affordable accommodation, so that I don't have to worry about where to stay.”

‍

How to write effective Job Stories?

A Job Story typically follows the structure:

When [situation], then I want to [motivation] or I want to [action], so that [desired outcome].

1. When: outline the context in which the user finds themselves, such as a specific situation or trigger.
2. Then I want to: describe what the user truly wants to do in this situation, what the core of the ‘job’ is.
3. So that: indicate what result or benefit the user is seeking.

By naming these three elements, you focus on the user's motivation and the ultimate goal.

‍

Checklist for strong Job Stories

• Context is clear: Which situation prompts the user to act?
• Desired outcome is measurable or at least concretely described.
• No persona needed: The situation and objective suffice.
• Testable: It must be clear when you are finished (Definition of Done).

‍

Examples of Job Stories in practice

• Banking: “When I want to check my balance on the go, I want to be able to log into the app quickly, so I know how much budget I still have for unexpected expenses.”
• E-commerce: “When I've just ordered a product, I want to be able to track its status, so I know when it will arrive and I can be home to receive it.”
• Education Platform: “When I want to learn a new skill, I want to see which lessons are available, so I can take targeted steps and measure my progress.”

‍

Integrating Job Stories into Scrum

1. Backlog: Replace (or supplement) user stories with job stories. This keeps the true ‘job to be done’ clear in your backlog.
2. Refinement: Discuss the situation and desired outcome of each job story with the team. This provides additional context.
3. Planning: Clarify what is minimally required to get the job story ‘Done’. Sometimes job stories can be split if they turn out to be too large.
4. Review: Verify if the job story has been fulfilled by checking if the user now achieves the desired outcome in the described situation.

‍

Practical Application of Job Stories in Backlog Management

• Group job stories by themes (e.g., “Payment”, “Registration”, “Search”).
• Combine job stories with story mapping: what steps does the user take and what ‘jobs’ are associated with them?
• Keep the backlog lean: if a job story is unlikely to be picked up, park it until it's prioritized.

‍

Conclusion

Job Stories offer an alternative, often more in-depth, way to describe user needs. Instead of focusing on personas, you delve into the situation and motivation behind the usage. This can help give your team greater insight into the 'why' and 'how' of a feature, ultimately leading to solutions that better meet the real needs of your users. Give it a try in your next sprint and discover if this approach improves your backlog management and team collaboration.

‍