User Story
A user story is a brief, plain-language description of a desired feature written from the user's point of view, capturing who wants it, what they want, and why.
Most teams write user stories in a simple template: 'As a [type of user], I want [some goal], so that [some reason].' The format keeps the focus on outcomes rather than implementation, so the team discusses the value being delivered before deciding how to build it. A good story is small enough to finish in one iteration and comes with acceptance criteria that define when it's done.
User stories matter because they translate fuzzy requests into shared, testable intent. They give engineers, designers, and product managers a common reference point, and they make trade-offs explicit: if a story doesn't clearly serve a real user need, it's worth questioning whether it belongs on the roadmap at all.
Stories are a natural bridge from feedback to delivery. A recurring request in your feedback inbox becomes a user story, gets refined with acceptance criteria, and enters the backlog. Linking the story back to the original feedback closes the loop, so you can tell customers exactly which of their asks shipped.