What it is
Short, user-centered statements of need in the form “As a [user], I want to [action], so that [benefit],” used to define increments of work from the user’s point of view.
When to use it
During Synthesize and Implement, to translate needs into deliverable increments.
Why (value)
Keep development anchored to user value, enable prioritization and estimation, and open a conversation about the real need behind a request.
How to run it
- Identify the user and their goal.
- Write the story: as a [user], I want [action], so that [benefit].
- Add acceptance criteria describing done.
- Keep stories small and independent.
- Prioritize and refine with the team.
Inputs and outputs
- Inputs: Understanding of user needs and goals.
- Outputs: A set of prioritized user stories with acceptance criteria.
Time and effort
Low. Ongoing; each story is quick.
Evidence and limitations
A story is a framing device, not proof of need. The “so that” should trace to evidence where possible; otherwise it is an assumption. See Evidence and limitations.
Tips and pitfalls
- Focus on the benefit, not the implementation.
- Keep stories small and testable.
- Do not let stories become disguised feature specs.
Variations
Job stories (“when… I want to… so I can…”), epics, acceptance-criteria-driven stories.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- User story mapping — Arrange user stories along the flow of activity to see the whole and slice releases sensibly.
- Use cases — Specify the steps of an interaction between a user and system, including alternate and error paths.
- Jobs-to-be-done framing — Frame what people are trying to accomplish, and why, rather than what features they ask for.
