Research is a powerful tool, but every project has to move beyond exploration and make progress toward a solution.
While Personas are a pure distillation of research, User Stories are an expansion. Performed well, User Stories help define the contours, giving the product form.
Your clients and peers are eager to see your progress, but movement forward is very different than crafting solutions. Just understanding who the user is and what they value doesn’t generate a product. Without specific tasks, the product lacks shape.
Luckily, you’re prior research documented what users want from the product. You also know enough about user frustrations to steer clear of issues they’ve experienced with other solutions.
When writing your user stories, keep the following concepts in mind:
- All users begin as new users.
- If you do your job, new users become returning users.
- New users and returning users often have different needs.
- Users generally use products in a few different ways (scenarios).
- Each persona has unique goals that should be reflected.
Resources for review
Please use the following items to guide your exercise attempt:
|The scope of your solution emerges||New Pragmatic|
|Tips for writing good user stories||Roman Pichler|
Length: One-to-two hours to complete.
Using the personas and scenarios built in the previous exercise, create at least twenty different user stories that apply to the Public Schools project. Indicate the user, task, and goal associated with each story.
While you could write your user stories in a Google Doc, a spreadsheet is ideal for this task as you may be adding additional columns of information to this data later in the course.
Once complete, update your Program Journal with links to any assets produced in this exercise. Post your Journal in the #Feedback-Loop channel for review.
Up next User Flows