How to Write a User Story: 7 Steps for Beginners (Free Templates)

Your team wants a wish list, but what does the shopper actually need? This beginner's guide shows how to find the real user, define the need and the reason behind it, and turn all three into one sentence. It then covers acceptance criteria in Given-When-Then form, priority and estimates, and a team review. You will leave knowing how to write, split and test a story, plus which of four free templates fits.

Written by:

Mustansar Mahmood
9 min read
ellipse

At first, a user story seems simple to write. However, many beginners struggle because they don’t know how long it should be, what information to include, or whether they should use a template to help them.

Luckily, this guide is here to answer these exact questions.

A well-written user story enables a product team to understand what a particular user wants to accomplish and why that outcome matters. Plus, it also gives product owners, developers, designers, and testers a shared starting point for discussing, prioritizing, developing, and testing a feature.

In this article, you will find out the key principles of crafting a well-written user story with the help of 7 simple steps. In addition to that, you will also learn about 4 ready-to-use templates to help you prepare an expert user story professionally.

What Is a User Story?

A user story is a short description of a desired outcome from the perspective of someone who will use or benefit from a product or feature.

It is an internal communication statement that is mostly prepared by the product owner or a person who understands the ideal user’s pain points.

These points are transferred in the form of a user story so that the team can learn the requirements of the customers in a better way and design a feature to cater to these needs.

Agile teams use stories to divide product work into small, user-focused increments that can be discussed, estimated, developed, and tested.

Framework of a user story

Also called the Connextra format, a user story usually has 3 parts:

  1. User role or persona
  2. Customer’s needs or wants
  3. The benefit of that need to that customer

Hence, a widely used formula to develop a user story is

As a [type of user], I want to [perform an action] so that [I receive a benefit].

Example

As a returning shopper, I want to save products to a wish list so that I can find them again without searching.

note

User stories are commonly used by Agile teams, including teams working with Scrum or Kanban, although neither framework requires them.

Core and supporting information in a user story record

A user story record may include the story itself, acceptance criteria, and additional information used for planning and delivery. Look at the following table to understand what a complete user story contains:

InformationWhat it recordsHow to use it
Core storyThe user, goal, and benefitWrite one focused outcome in language that product and technical team members can understand
Completion conditionsAcceptance criteriaDescribe observable conditions that must be met before the story can be accepted.
Planning informationPriority, estimate, tasks, release, dependencies, and similar fieldsComplete the fields your team uses to schedule and manage the work.

Key Concepts for a User Story

Before learning how to write the user story, two concepts explain how user stories are developed and evaluated:

Three Cs

3Cs is a key concept in developing user stories, ensuring that these statements are useful and easier for a team to work with.

Introduced by Ron Jeffries in 2001 as part of Extreme Programming (XP), the concept comprises three Cs: Card, Conversation, and Confirmation. They explain why the written sentence is only one part of the story.

  • Card: The short written description of the customer’s needs. It also gives the team a reminder of what must be discussed or developed.
  • Conversation: These are the discussions among stakeholders, developers, designers, and testers around the story to decide on a technical feature to satisfy the need. It clarifies behavior, scope, exceptions, and possible solutions.
  • Confirmation: It includes the conditions used to verify the results. This also provides acceptance criteria or tests that show whether the need was met.

Example

The card may say that shoppers need a wish list. The conversation determines matters such as whether guests can save products or whether there is a list-size limit. Confirmation records the agreed behavior in a testable form.

INVEST

INVEST is more of a post-writing checklist rather than a writing formula. It helps the writer to ensure that the user story is well-written and ready for development, containing necessary and viable information. If you are a beginner, this concept is a useful criterion to check your stories.

After writing your user story, make sure it answers the following questions:

  • Independent: Can it be delivered without depending heavily on another unfinished story?
  • Negotiable: Does it leave room for the team to determine the solution?
  • Valuable: Does it produce a recognizable benefit?
  • Estimable: Does the team understand it well enough to estimate the effort?
  • Small: Can it be completed within one iteration?
  • Testable: Can the result be objectively verified?
This infographic is about key concepts for a user story.Pin
This infographic is about key concepts for a user story.

How to Write a User Story Step by Step?

Let’s discuss the elephant in the room. We’ll use one running example throughout this section for help:

“Add a wish list to the online store.”

Step 1: Identify the actual user

A good story clearly identifies one user. You have to determine the person who is facing the problem or who needs the feature. A common mistake here is to go with a generic user without a specific role or to target multiple customers with different personas.

The following are some channels to find your user:

  • Customer interviews and surveys
  • Product analytics
  • Support requests
  • Sales or customer-service feedback
  • Existing personas
  • Observations from usability research

Avoid choosing a role only because it fits the sentence format. A role such as “website visitor” is still too broad if signed-in and signed-out visitors receive different wish-list behavior.

Example

Assume customer feedback shows that returning shoppers repeatedly search for products they previously considered. “Returning shopper” is therefore more informative than “user.”

Step 2: Define the user’s needs

The next step is to identify the needs of your user. A good way to find this is to ask what outcomes the person wants, separately from the feature that has already been proposed.

You can ask the following questions to identify the user’s needs:

  • What they are trying to accomplish
  • Where they struggle
  • What prevents them from achieving it 

Mostly, the user role and desired outcome often become clearer together because each provides context for the other.

Write one outcome per story. If the request also includes sharing a list, receiving price alerts, and comparing saved products, treat those as separate needs unless the team determines that they must be delivered together.

Example

A returning shopper’s biggest struggle is that they have to repeatedly search for products on each visit. To avoid this hassle, they need a way to save the products.

Step 3: Determine why the need matters

For a successful story, you have to look beyond the user’s needs. The key concept is to find the hidden pain point, problem, or desired outcome behind the need. You can find this by looking at the user’s goal.

Knowing underlying reasons is also important for the internal team. If they know the pain point or goal behind a need, they may find an effective way to solve the issue.

This distinction leaves room for the team to determine how the saving function should work. Further, it also prevents the story from becoming a list of interface instructions before the team has evaluated the design.

Example

The reason behind having a wish list is that shoppers want a place where they can come and check their saved products without adding or searching for them manually on each visit.

Step 4: Write the user story sentence

Now, combine the three elements that we have discussed till now: user, action, and benefit:

As a returning shopper, I want to save products to a wish list so that I can find them again without repeating my search.

Now, you have your user story. At this point, you have practically transformed the requirement of a wish list into something the internal team can understand and come up with a practical solution.

Minor wording changes are acceptable. For example, the team could write “save products for later” instead of “save products to a wish list.” The sentence works when the user, desired outcome, and reason remain clear.

Note that you do not add every requirement to this sentence. Authentication rules, removal behavior, and data persistence belong in the acceptance criteria.

Step 5: Add acceptance criteria

Acceptance criteria state the observable conditions that must be satisfied before the product owner or relevant stakeholder accepts the story. For the wish-list example, the initial criteria might be

  • A signed-in shopper can save a product from its product page.
  • The saved product appears in the shopper’s wish list.
  • The product remains saved after the shopper signs out and returns.
  • The shopper can remove a saved product from the list.

Acceptance criteria are usually refined through team discussion. For example, the team may need to decide what happens when a shopper is signed out, saves the same item twice, reaches a list limit, or returns after a saved product becomes unavailable. Record only the scenarios that apply to the agreed scope.

There is a common way to write an acceptance criterion using the “Given–When–Then” form. Given is the initial context, when the event occurs, and then is the observable result.

Example

Given that a shopper is signed in, when they select “Save to wish list,” then the product should appear in their wish list.

Step 6: Assign priority and estimate

Priority indicates where the story should be placed relative to other work. As per the 2020 Scrum Guide, the Product Owner is accountable for ordering Product Backlog items in Scrum. However, customer evidence, risk, dependencies, and team input may also influence that decision.

“Estimate” refers to the effort required by the team to convert this story to an observable result. It is mostly defined after discussion with the relevant team.

If the story is too large to estimate, develop, and test within the team’s normal delivery cycle, consider splitting it into smaller user-facing outcomes. For our wish list example, it can be divided into signed-in saving and viewing, item removal, and guest wish list behavior. Each resulting story should still produce something the user can recognize and test.

Step 7: Review the story with the team

Before finalizing the story, it is better to share it with the team, especially those who may own it in the future. The review should answer three questions:

  1. Does the story describe the correct user need and benefit?
  2. Do the acceptance criteria cover the agreed behavior?
  3. Can the team deliver and test the story within the intended iteration?

Revise the wording, criteria, or scope when the discussion reveals uncertainty. An estimate made before resolving a major unknown should be reconsidered after the story is clarified. Product owners and stakeholders should confirm that the refined story still addresses the original need.

This infographic is about writing a user story guide.Pin
This infographic is about writing a user story guide.

Choosing the Right User Story Template

Creating every story record from scratch takes time and may lead to missing fields or inconsistent formats. The free WordLayouts user story templates provide ready-made structures for individual stories, epics, themes, and SAFe teams and scaled Agile environments.

Here is what each template offers and how it can be adjusted in your workflow:

TemplateBest suited forMain distinction
SimpleOne focused user needRecords one story with its priority, estimate, and acceptance criteria
EpicA large outcome containing multiple related storiesBreaks a substantial initiative into smaller stories
ThematicStories connected by a strategic topic or objectiveGroups related stories and connects them with releases
SAFeTeam-level work managed within a scaled Agile environmentAdds fields for value, requirements, tasks, quality, and effort

Benefits of User Stories

User stories keep product work focused on the real user value by complementing the technical documentation with simple and easy-to-understand language. Listed below are some of the perks of creating user stories:

  • They offer the real user requirements that help technical teams to decide the most efficient solution to the problem.
  • They give product, design, development, and testing participants a shared description of the expected outcome.
  • User stories make it easy to track and observe because stories represent specific outcomes that can be refined, developed, and tested.
  • They break down the large idea into smaller units that product owners and stakeholders can easily understand.
  • These stories allow teams to keep high-level goals in the backlog and add specifics only when implementation is near.

How Do User Stories Support Testing?

As the team refines a user story, its acceptance criteria provide the basis for test scenarios:

User story → conversation and refinement → acceptance criteria → development and testing → acceptance

This infographic is about user story structure.Pin
This infographic is about user story structure.

Example

For the wish-list story, the sentence establishes the returning shopper’s goal. The criteria establish that signed-in shoppers can save, retain, view, and remove products. Testers can then prepare scenarios covering the normal action and the agreed boundary conditions.

For example, the criterion about retaining a saved product produces a scenario with these steps:

  1. Sign in as a shopper.
  2. Save a product.
  3. Sign out.
  4. Sign in again.
  5. Confirm that the product remains in the wish list.

Bottom Line

A good user story identifies a real user who is facing a problem, converts these issues to plain, non-technical language, and explains why outcomes matter.

Based on the goal decided by the user story, it allows the team to have discussions and find the optimal solution to solve the user’s issues.

You can create a user story quickly using a template. Based on your requirements, you can choose from Epic, Thematic, SAFe, or Simple templates.

Frequently Asked Questions

Who should write user stories?

Technically, anyone with the relevant knowledge may write a user story. Product owners, customers, business analysts, developers, designers, and testers can all contribute. However, a product owner is often responsible for creating and communicating product backlog items in Scrum.

How long should a user story be?

A user story is usually one or two sentences long. Further, it should provide enough information to identify the users, their desired outcomes, and reasons.

What is the difference between a user story and a use case?

A user story is a short and simple statement of one user’s needs. However, a use case contains more information and lists each step to reach that goal. It may also be used after a user story, where one use case can therefore provide context for several smaller user stories.

Does every user story need Given–When–Then acceptance criteria?

No, Given–When–Then is commonly associated with behavior-driven systems and automation testing under a particular condition. But they can also support manual acceptance criteria. It is beneficial when a complex user behavior is involved or to give a heads-up to record the starting context, action, and expected results.