Tactic 14 User Stories

User stories are a device for capturing what the user needs from the solution. By explaining what the user needs, it enables a designer and developer to work together to find the best way of meeting this need. This can be preferable to detailed documentation that can inadvertently add extra complexity or fail to explain what you really mean.

A user story has three parts:

  1. As a [type of user]
  2. I want to [a thing the user wants to do]
  3. So that [why they want to do it]

Once you’ve created lots of user stories, you can prioritise which are most important to develop in the next phase. The remainder are valuable to keep for the next stages of development.

For inspiration

Writing good user stories

Written on February 14, 2017


Rate It: