Design and product work
User story
Also calledStory, Acceptance criteria, Requirements
A short description of a piece of work from the user's point of view, such as 'As a traveller, I want to save a search so I can book later', plus the criteria that say when it is done.
User stories keep requirements anchored to who benefits and why, rather than to a technical task. The common template is: as a type of user, I want some goal, so that some benefit.
Acceptance criteria are the testable conditions that make a story done. They are where vague requests turn into decisions, which is why product owners and analysts spend so much of their week writing them.
Common mistake
Writing the solution into the story. 'As a user, I want a dropdown' fixes the design before anyone has looked at the problem.