User Story
A concise statement of a desired outcome from a user’s perspective that acts as a prompt for collaborative requirements and delivery conversations.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/user-story/
01What it means
A user story is a small, informal description of valuable behavior from the perspective of a person or stakeholder. Teams often use “As a…, I want…, so that…” as a helpful format, but the sentence is only a reminder; conversation, examples, and acceptance criteria provide the shared understanding needed for delivery.[1][2]
02Why it matters
User stories connect day-to-day work to an identifiable need instead of reducing the backlog to technical tasks. Their small size supports incremental delivery and feedback, while their intentionally negotiable form invites product, design, engineering, and testing perspectives before the team chooses an implementation.
03When to use it
Use stories to represent small slices of user-valued behavior in an iterative backlog. They are useful during discovery, story mapping, refinement, planning, and acceptance. Use another form when contractual precision, complex rules, research work, or infrastructure changes cannot be expressed honestly through a user narrative alone.
04How it works
- Identify a real user or stakeholder and the outcome they need in a specific context.
- Write a short statement that names the goal and value without prescribing the interface.
- Discuss scenarios, evidence, constraints, edge cases, and dependencies with the delivery team.
- Add concise, testable acceptance criteria and split stories that are too large or compound.
- Deliver, observe the result, and revise later stories using what the team learns.
05A practical example
For a commuter rail app, the team writes: “As a rider changing trains, I want disruption guidance for my specific connection so that I can choose an alternative before reaching the platform.” Discussion reveals accessibility and timing needs; criteria cover stale data, canceled services, and screen-reader announcements.
06Where it breaks
A tidy template does not prove a genuine user need. Stories can hide policy, quality, data, or operational requirements when teams force every concern into one sentence. Excessive splitting may also produce fragments that deliver no meaningful outcome. Supporting models and conversations remain essential.
Common mistakes
- Writing a UI component or engineering task as though it were a user outcome.
- Using a generic role such as “user” when context materially changes the need.
- Treating the story sentence as complete requirements and skipping conversation.
07Sources
- What are User Stories?Agile Alliance · Professional glossaryWhat are User Stories?
- User Stories With Examples and a TemplateAtlassian · Professional guideUser Stories With Examples and a Template