What is User Story?
A user story is a concise statement of a need or feature written from the user's point of view. The classic template is: "As a [type of user], I want [some goal] so that [some benefit]." This framing keeps teams focused on the user's intent and the value delivered, not just the implementation.
Good user stories are small, independent, and testable, and they pair with acceptance criteria that define when the story is "done." They are deliberately lightweight — a placeholder for a conversation between the PM, designers, and engineers rather than an exhaustive spec.
PMs write and refine user stories to break larger initiatives (epics) into shippable pieces. The INVEST checklist — Independent, Negotiable, Valuable, Estimable, Small, Testable — is a common quality bar for well-formed stories.
Examples
- "As a returning shopper, I want to save my payment details so that I can check out faster next time."
- A large "checkout redesign" epic is split into 12 user stories, each independently shippable.
Where PMs use this
Related terms
Epic
A large body of work that is too big for a single sprint and is broken down into multiple user stories.
Acceptance Criteria
The specific, testable conditions a user story must satisfy to be considered complete.
Product Backlog
A prioritized, continuously updated list of everything that might be built for a product.
Story Points
A relative unit for estimating the effort, complexity, and uncertainty of a user story.