User Stories
Short, structured descriptions of features told from the perspective of the person who wants them.
Definition
A User Story is a short, structured description of a feature or requirement told from the perspective of the person who wants it, typically following the format: "As a [role], I want [goal], so that [benefit]." User stories emphasize conversation and shared understanding over exhaustive upfront documentation, and are commonly used in Agile and iterative delivery approaches.
Inputs
- An identified user role or persona and a goal that role wants to accomplish
- Understanding of the value or benefit the goal delivers to that user
Outputs
- A concise story statement capturing role, goal, and benefit
- Often paired with acceptance criteria that define when the story is considered complete
When to Use
- Iterative, Agile, or incremental delivery environments where requirements evolve through ongoing conversation
- Capturing requirements from a clear user/persona perspective, keeping focus on value delivered rather than implementation detail
- Breaking larger epics or features into smaller, deliverable increments
When Not to Use
- Highly regulated or contractual requirements needing exhaustive, unambiguous specification upfront (a formal requirements document may be more appropriate)
- Complex system-to-system or batch logic with no clear single "user" perspective
See this technique in action with a free RequirementsHub workspace.
Start Free Workspace →