4.4
2,100+ reviews on G2
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:

A person or role, not "everyone".
The thing the user wants to do.
The benefit the user gets.
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.
Choose the person or role who benefits. A regional sales manager is more useful than "a user" because the team can picture the work.
Write what the user wants to do, in one sentence. Keep it to one outcome, not a list of features.
Say why the user wants it. The reason is the value the team is trying to deliver.
List what must be true for the story to be done. Atlassian says acceptance criteria make the story testable.
A story that cannot be finished in a sprint is usually too large. Split it until the team can finish it and get feedback.
Use the three C’s: the card, the conversation and the confirmation. The written card starts the conversation; the team adds detail together.
Put the story in the backlog with its owner and sprint. Refine it before the team brings it into a sprint.
| Story | Owner | Due |
|---|---|---|
| 1Save a recipe | Nia | Nov 14 |
| 3Add ingredients to a list | Omar | Nov 19 |
| 4Share the list | Tess | Nov 24 |
| 5Edit a saved recipe | Nia | Nov 26 |
| 5Remove a saved recipe | Omar | Nov 27 |
| 7Search saved recipes | Tess | Nov 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.
The label matters less than the level of detail. Use the one that helps the team have the right conversation.
| Item | What it is | Example |
|---|---|---|
| User story | A 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. |
| Task | Work the team performs to deliver an outcome. | Create the saved recipes table. |
| Epic | A 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".
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]
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
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.
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.
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.
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.
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.
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.
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.
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.
Keep the product brief, the story cards and the acceptance criteria in one notebook, so the team writes from the same context.
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.
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.
Ask it to turn each story into a task assigned to its owner. Each person sees their story and the sprint date.
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