How to write a user story

A user story is a short sentence that describes a feature from the user’s point of view, usually in the form "As a [user], I want [goal] so that [reason]". A good story does four things:

Four blank white cards arranged in a two-by-two grid
Four blank cards, ready for one user, one goal and one reason each.Photo: BRRT / Pixabay
  1. 1

    A real user

    A person or role, not "everyone".

  2. 2

    One goal

    The thing the user wants to do.

  3. 3

    A reason why

    The benefit the user gets.

  4. 4

    Acceptance criteria

    What must be true for the story to be done.

Write your stories in Evernote. Turn the brief into story cards, draw the sprint, and assign stories.

Write your user stories in Evernote

How to write a user story in 7 steps

  1. 1

    Name the user

    Choose the person or role who benefits. A regional sales manager is more useful than "a user" because the team can picture the work.

  2. 2

    State the goal

    Write what the user wants to do, in one sentence. Keep it to one outcome, not a list of features.

  3. 3

    Add the reason

    Say why the user wants it. The reason is the value the team is trying to deliver.

  4. 4

    Write acceptance criteria

    List what must be true for the story to be done. Atlassian says acceptance criteria make the story testable.

  5. 5

    Keep it small

    A story that cannot be finished in a sprint is usually too large. Split it until the team can finish it and get feedback.

  6. 6

    Review the story together

    Use the three C’s: the card, the conversation and the confirmation. The written card starts the conversation; the team adds detail together.

  7. 7

    Add it to the backlog

    Put the story in the backlog with its owner and sprint. Refine it before the team brings it into a sprint.

Checkout stories

Six stories for the November sprint
StoryOwnerDue
1Save a recipeNiaNov 14
3Add ingredients to a listOmarNov 19
4Share the listTessNov 24
5Edit a saved recipeNiaNov 26
5Remove a saved recipeOmarNov 27
7Search saved recipesTessNov 28

Each row is a story, with its owner and due date. The full sentence and acceptance criteria live under the story in the same note.

Story, task or epic?

The label matters less than the level of detail. Use the one that helps the team have the right conversation.

ItemWhat it isExample
User storyA useful outcome from the perspective of someone who benefits.As a cook, I want to save a recipe so that I can find it later.
TaskWork the team performs to deliver an outcome.Create the saved recipes table.
EpicA large story that is still too big to finish in a sprint.Saved recipes, including lists, sharing and editing.

Definitions from Mountain Goat Software, "User Stories: What They Are, How to Write Them, and Examples".

Free user story template

Copy it, or save it to your Evernote account and write one card for each story.

Story: [short name]

As a [type of user]

I want [goal]

So that [reason]

Acceptance criteria:
-
[what must be true]
-
[what must be true]

Owner: [name] · Sprint: [name or dates]

Notes from the conversation: [what the team decided]

Trusted by Millions Worldwide

4.4

2,100+ reviews on G2

4.4

8,200+ reviews on Capterra

4.4

73,000+ reviews on App Store

248M

Registered users

User story questions

What is a user story?

Atlassian describes a user story as an informal, general description of a software feature written from the end user’s or customer’s perspective. Mountain Goat Software calls it a short description of desired functionality told from the perspective of someone who wants it.

What is the format of a user story?

The common format is "As a [user], I want [goal] so that [reason]". Atlassian says that format keeps the user, the goal and the benefit in one sentence, which gives the team something concrete to discuss.

What are acceptance criteria?

The details that tell the team what must be true for the story to be complete. Atlassian says acceptance criteria make the story testable, and Mountain Goat says they can be examples, rules, tests or brief notes.

What are the three C’s of user stories?

Card, conversation and confirmation. The card is the written description, the conversation is where the team adds detail, and the confirmation is the acceptance criteria. Atlassian and Mountain Goat both use the same three words.

How long should a user story be?

Short enough to fit on a card and start a conversation. Mountain Goat says the written story is a reminder; the real requirement emerges through conversation, examples, rules, sketches, tests and decisions.

What is the difference between a user story and a task?

A story describes a useful outcome for someone who benefits. A task describes the work the team performs to deliver that outcome. Mountain Goat gives the example of a story about saving a payment method, while creating the database table is a task.

What is an epic?

A large story. Mountain Goat says an epic is useful when the team wants to remember an important capability before the details are known, and that it should be split into smaller stories as it gets closer to development.

Who writes user stories?

Anyone can write one. The product owner is accountable for the backlog, but Mountain Goat notes that developers, testers, designers, analysts, Scrum Masters, stakeholders and users can all contribute.

How to write a user story with Evernote

Keep the product brief, the story cards and the acceptance criteria in one notebook, so the team writes from the same context.

  1. 1

    Write the story cards.

    Open the brief and ask the AI Assistant to make user stories with a story, owner and due date. It creates a note with one row per story.

  2. 2

    See the sprint.

    Ask it to add a gantt chart of the stories. The Mermaid chart shows which stories overlap and which one sets the sprint end date.

  3. 3

    Assign the stories.

    Ask it to turn each story into a task assigned to its owner. Each person sees their story and the sprint date.

  • You can also ask the AI Assistant to rewrite a vague story with a clearer user, goal and reason.
  • You can also link the user interview note to the story, so the evidence sits beside the card.
  • You can also share the backlog note with the team, so everyone adds acceptance criteria in one place.

Keep the brief, the cards and the acceptance criteria together

Write one story per row, give it an owner and a sprint, and let the team add the detail in the same note.

Start for free