Skip to content
Module
Product and data

User story: definition, format and examples

A user story is a short description of a need, written from the point of view of the person who benefits from it. It often follows the template “As a [type of user], I want [action] so that [benefit]” and comes with acceptance criteria that state when it is satisfied. Born in Extreme Programming, it is above all meant to start a conversation between product, design and engineering.

Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.

Why it matters for a PM

User stories keep the user benefit at the center of work broken into small pieces. For a PM, they are a tool for slicing and for dialogue: each story should deliver verifiable value and stay small enough to ship in one iteration. Naming who the story is for also tends to reveal that different users have different needs.

Example

“As a payroll manager, I want to be alerted when an employee has not approved their hours the day before closing, so that I can follow up before generating payslips.” The acceptance criteria specify when the alert is sent, through which channel, what happens if everything is approved and who can turn the notification off.

Key points

  • The “so that” matters as much as the rest: it explains the value and guides design choices.
  • Acceptance criteria make the story testable, for instance in a Given / When / Then format.
  • Bill Wake's INVEST checklist helps judge its quality: independent, negotiable and valuable, estimable, small and testable.
  • A story that is too big can be split by flow, by business rule or by type of user.

Common mistakes

  • Writing “As a user” everywhere, which erases the differences between profiles.
  • Disguising a technical task as a story with no benefit for anyone.
  • Treating the story as a complete spec and skipping the conversation.

Go further with Module

The courses and lessons that cover this concept:

Guides on this topic