What is a user story in UX design?
A user story is a brief description of a feature or functionality written from the perspective of the person who will use it, following the format: "As a [type of user], I want to [perform some action] so that [I achieve some goal]." User stories are a communication tool used in agile development to describe product requirements in terms of user needs rather than technical specifications. They keep the team focused on why a feature exists, who it serves, and what outcome it should produce, rather than starting from implementation details.
How are user stories used in UX design?
UX designers contribute to and consume user stories throughout the design process. During discovery, research findings are often articulated as user stories that describe what different user types need to accomplish. During design, user stories provide the context for design decisions: every screen and interaction should connect to one or more user stories that explain why it exists. During development, user stories guide engineers in building features that match the intended user outcome. Acceptance criteria attached to user stories specify the conditions under which a story can be considered complete, which can include UX quality criteria alongside functional requirements.
How do user stories relate to jobs to be done?
User stories and jobs to be done address similar questions from different perspectives. A user story describes a specific feature need in the context of a product: "As a project manager, I want to see all overdue tasks in one view so that I can follow up with my team efficiently." JTBD describes the underlying motivation at a higher level of abstraction: "When managing a team, I need to quickly identify what is at risk so I can take action before deadlines are missed." JTBD is more useful for strategic discovery and product direction. User stories are more useful for translating those insights into specific, actionable development requirements.