2. Problem
• User gets lost without clear pathways to
accomplish tasks
• Persistence of contextually-inappropriate controls
makes finding right control difficult
8. Scenario-based Design
• Design a solution around how a user accomplishes
a task
• Rather than drowning a user in a sea of controls,
provide the controls that a user is looking for in that
step of the task
• Given that people approach accomplishing tasks
differently, provide multiple entry points for users to
accomplish a specific task
9. Scenario-based Design
Applied to Maps
• What are the scenarios within which a user will be
performing certain planning actions
• How are different users going to go about
accomplishing their tasks?
10. For Example
• If a user has not created a location, they should not
be shown a delete button
• Contextually-appropriate controls
11. Multiple Entry Points:
Users may want to approach planning by…
• Finding a location then drawing a custom shape
• Finding a location then repositioning an already
constructed shape
• Uploading floor plans then associating them with a
location
12. Now lets look at the
design…
References:
• “Five Reasons for Scenario-based Design” HCI at Virginia Tech, http://faculty.washington.edu/gdemiris/MEBI554/
readings/carroll1999.pdf
• “Are multiple entry points good or bad?” http://ux.stackexchange.com/questions/5015/are-multiple-entry-points-
good-or-bad
17. Conclusion
From task-based to scenario-based design
• Simplify workflows by providing contextually-
relevant controls
• Allow multiple entry points to accommodate for
different scenarios / personas
• Design with interaction to bring playfulness to the
UI