User Stories: Write Short Sentences That Name the Who, What and Why
A user story is a one-sentence way to describe what a person wants from a product and why. Learn the pattern, the three Cs and the INVEST check.
In short
A user story is a one-sentence note that says what a person wants from a product and why, usually as a role, a goal and a reason.
5 min readFree
What You Will Learn
A user story is a short note that describes a feature from the view of the person who wants it. <cite index="6-6">A user story is a short, simple description of a feature told from the perspective of the person who desires the new capability.</cite> Teams use these notes to talk about work in plain words. Because they use everyday language, everyone on a team can read them. In this lesson you will learn the sentence pattern, the three Cs, and a six-point check called INVEST.
Key words
- User story
- A short, plain description of one feature, told from the point of view of the person who wants it.
- Role
- The kind of person who uses the product, such as a shopper or a new member.
- Goal
- The action the person wants to take.
- Benefit
- The reason the person wants it. It comes after the words 'so that'.
- Acceptance criteria
- The checks that show a story is finished and working.
- INVEST
- A six-letter checklist for judging whether a user story is good.
What is the three-part sentence?
The most common template is the Connextra form: As a <role> I can <capability>, so that <receive benefit>. <cite index="6-3">Mike Cohn wrote what is now the standard book on writing user stories, User Stories Applied, published in 2004.</cite> In that book he described the three parts this way. Each part does one job.
Role
Name a real kind of user, not just 'user'. 'Shopper' tells the team far more than 'person'.
Goal
Say what the person wants to do. <cite index="7-7">User stories are written in terms of goals rather than solutions.</cite>
Benefit
Explain why it matters. <cite index="5-4">Mike Cohn suggested the so-that clause is optional, although it is still often helpful.</cite>
Here is a full example: As a shopper, I want to save my cart, so that I can finish buying later.
Tip
Read your sentence out loud. If a real shopper would not say it that way, rewrite it in their words.
Build a Story From Parts
Programmers often keep the three parts in separate variables, then join them into one sentence. This sample uses only the standard library, so it runs as it is.
role = 'shopper'
goal = 'save my cart'
benefit = 'I can finish buying later'
print(f'As a {role}, I want to {goal}, so that {benefit}.')Output
As a shopper, I want to save my cart, so that I can finish buying later.
What are the three Cs?
The 3 C's of user stories, card, conversation and confirmation, is a framework that Ron Jeffries proposed in 2001. Each C is a stage. A story moves through all three before the work is built.
- 1
Card
Write the short version of the story on a card or a digital note. <cite index="21-10,21-11">The card is the short, written version of the story. It acts as a reminder of the need.</cite>
- 2
Conversation
Talk it through. <cite index="21-12,21-13">The conversation is the discussion around the story, where the team clarifies details, explores options and agrees what is really needed.</cite>
- 3
Confirmation
Write down how you will know it is done. <cite index="21-14,21-15">Confirmation is the acceptance criteria, meaning the measurable conditions that confirm the story was completed successfully.</cite>
Tip
Keep the card short. Put the details in the talk, then write the agreed checks down so nobody forgets them.
Check Each Story With INVEST
Mike Cohn helped popularize INVEST in his book User Stories Applied. Use the six letters as a quick test. A story that fails a test may need rewording or splitting.
Independent
A story that leans on another story makes planning harder. <cite index="14-4">Stories should not depend on each other, because that can cause prioritization and planning problems.</cite>
Negotiable
It starts a talk rather than locking terms in place. <cite index="18-12">The story is a conversation starter, not a contract.</cite>
Valuable
It should help a real user or customer, and the reason should be clear. <cite index="18-15">The story delivers value to a real user or customer.</cite>
Estimable
A team should be able to guess its size with reasonable confidence. <cite index="17-8">Estimable means the team can judge the size to a good approximation.</cite>
Small
It should fit inside one iteration, which is a fixed short work cycle. <cite index="17-8">Small means the story fits within an iteration.</cite>
Testable
A tester should be able to check it without asking the writer. <cite index="18-22">Acceptance criteria exist and a tester can verify them without asking the author.</cite>
Why should you avoid vague words?
Vague words give testers nothing firm to check. <cite index="14-14">Avoid using criteria like easy to use, fast or bug-free.</cite> Replace a word like fast with a clear target, such as a time the page must load within, and write it as an acceptance check.
Write Your First Story
- 1
Pick the person
Choose a specific role, such as trial user or shopper.
- 2
Name the goal
Write one action the person wants to take.
- 3
Add the reason
Finish with so that and a real benefit. If the reason just repeats the goal, dig for the true motive.
- 4
Run INVEST
Check all six letters. Reword or split the story if one fails.
- 5
Add acceptance criteria
Write the checks that confirm the story is done.
Quick check
In 'As a shopper, I want to save my cart, so that I can finish buying later', which part is the benefit?
Key Takeaways
A user story names a role, a goal and a reason in one short sentence. Use the three Cs to grow it through talk and written checks. Then use INVEST to test it before work begins.
Sources
- Agile Modeling: User Stories: An Agile Introduction
- Mountain Goat Software: User Story Template: What It Is and Why It Works So Well
- Wikipedia: User story
- Agile Alliance Glossary: What does INVEST Stand For?
- Agile Business Consortium: What are User Stories?
- Visual Paradigm: Applying the INVEST Criteria in Daily Practice
- Docsio: User Story Template: Format, Examples, and INVEST Criteria
- Dal Mijn: Revisiting INVEST 20+ Years Later
- Airfocus: What are card, conversation, and confirmation (3 C's)?
- The Kaizenko: The 6 Attributes of Effective User Stories
- Nick Arora: User Stories Applied by Mike Cohn
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.