Skip to content
BENIBIX Learn

Job Story vs User Story

People think a job story is a user story with new words, and it is not. A user story starts from a type of user and is a piece of work to build. A job story starts from a moment: when this happens, I want to do this, so I can get that. It names no product, so it shows the need before anyone picks a fix.

Business📦 Product Management

Job Story

A need in one line: when this happens, I want this, so I can do that.

A job story is a short sentence that writes down one job a user wants done. It follows a pattern: when (a situation), I want to (a motivation), so I can (an outcome). It starts from the moment, not from a type of person. That keeps the focus on why the need comes up. Teams use job stories to plan features without guessing who the user is.

Example
"When my bus is late, I want to see where it is, so I can plan my wait."
Why it matters
The situation part shows when the feature must work. That detail is what makes a good design.
Full entry
Business📋 Agile Delivery

User Story

A short note of one thing a user wants, and why. The details come from talking.

A user story is a short note about one thing a user wants. It is written from the user's side, in plain words. The usual form is: as a kind of user, I want something, so that I get a gain. The card is kept short on purpose. The details come from talking with the team and from the acceptance criteria. A story should be small enough to finish in one sprint.

Example
Emma's team writes: as a shopper, I want to save my cart, so that I can buy later. They agree on two acceptance criteria and build it in four days.
Why it matters
It keeps the team talking about what users need, not only about features. The why part helps them pick the simplest way to get there.
Full entry

In one line

Job Story
A need in one line: when this happens, I want this, so I can do that.
User Story
A short note of one thing a user wants, and why. The details come from talking.