Presented at Agile2013 in August 2013 Abstract: “What do you think?” and “How does this look?” are easy questions to ask when presenting users with potential design concepts, but they rarely give way to meaningful feedback. Using scenarios (workflow-based stories that provide a framework for getting user feedback) allows the user to give more honest, relevant feedback more closely related to the work they do on an everyday basis. It’s essential to gather user feedback during all stages of an iterative design process, and using scenarios to support design assessments works well within an Agile environment. In this workshop session, geared towards designers and product owners, we will explore what goes into creating meaningful scenarios and how they can be used. We will practice writing scenarios based on provided user workflows and paper prototypes. Scenarios can be a great tool in your toolbox for gathering requirements that your users will appreciate.

1. Strength In scenarios
getting meaningful user feedback on designs
Thomas Piggott
High-Tech Anthropologist®
Renee Pinter
High-Tech Anthropologist®

2. What will you learn
in the Next 75 minutes?

3. But first, who are we?

4. What is a scenario to you?

5. Our design process
Potential User
Observations &
Interviews
Define the
Problem &
Project Scope
Determine
Target Users
(Persona Map)
Create
Conceptual
Designs
Design
Assessments
with Scenarios
Refine
Designs

6. So What DO WE MEAN BY scenario?
A scenario is a story that provides the framework
for getting user feedback on mockups or
prototypes.
It follows a high-level workflow that is based on prior
observations of target users.

7. Client: MyWedding.com

8. Kathleen Tober
52 years old
Homemaker in Dexter, Michigan
• Planning her youngest
daughter’s upcoming wedding
• Embarrassed because she
doesn’t understand much
about computers
• Worried about keeping track of
wedding planning while
traveling on vacations
Your PRIMARYPERSONA:

9. What a design assessment
Might look like

10. When CREATING A SCENARIO
• Decide what features you want feedback on
• Use realistic data
• Avoid using overly similar language to what’s in
the designs (it defeats the purpose!)
• One scenario can cover several features
• Scenarios present the opportunity for the user to
work across tasks

11. When using a scenario
• Keep it short
• It’s just a guideline: “Make mistakes faster”
• Answer questions with questions like:
– “What would you expect?”
– “How do you do it now?”
• Use the same scenario across contrasting
design concepts

12. Now you try it!
Using the provided designs,
let’s try writing a scenario

13. Now you try it!
Got your scenarios?
Now you’ll practice using them!
Decide who wants to play what role:
• Kathleen, the user
• the “CPU”, the person delivering the scenario
• the “DVR”, the person taking notes

14. What thoughts and questions do you have?

15. Strength In scenarios
thank you for coming to
Thomas Piggott
@tjpiggott
Renee Pinter
@repinter
Get in touch with us!