Your SlideShare is downloading. ×
AC4D design library worksheet scenarios
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

AC4D design library worksheet scenarios


Published on

Austin Center for Design is an …

Austin Center for Design is an
educational institution in Austin, Texas,
teaching Interaction Design and Social Entrepreneurship
- See more at:

All content is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. This license means that, while the author retains the copyright to the work, you are permitted to a) share this work with anyone you like, as long as you don't charge money for it; b) change this work and re-release it under your own name, with attribution to the original source; and c) integrate this work into your own work in small or large portions.

Published in: Design

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Scenarios About this activity: Before Starting This Activity: A scenario is a written story that explains how a person will use a product, service or system to achieve a goal. 1 2 Identify the people who will be using the system. Create a persona page for each distinguishable user. What are their names? Where do they work? What level of technical experience do they have? What level of technical competence can you assume with this system? Do they have any physical or cognitive limitations? Name 3 Identify the starting state / context. List as many details as possible. Where will the people using your system be, physically, when they encounter it? Will the people using your system have any other limitations because of there they are at? What state is the actual product or service in when they first acknowledge it? Name Distinguishing Characteristics Required: Participants should have an understanding of a topic, built off contextual research. Is an individual and/or group activity Preparation: None Takes 15 - 20 min Materials required: · 8.5 x 11 Paper · Sharpie Markers · Post-It Notes 4 List the goals the user may have, as they pertain to your product or service. Put each goal on a post-it note. A goal is about a fundamental want, need, or desire that is presently unattained. Activity Details: 5 Prioritize the goals, based on your understanding of your users. Stack rank the goals, putting them in order from “most important to achieve using this system or service” to “least important to achieve using this system or service.” Goals rarely change, even when technology evolves. On a separate piece of paper, craft a narrative that explains how a person will use your system to achieve their goals. Don’t try to achieve all of the goals in a single epic story; instead, create multiple stories, one for each goal. Keep the conversation at a high, behavioral level, rather than a low user interface level. A Good Scenario: List as many goals as you can think of. Fred grabs his phone. He opens the beer-finding App., and locates a beer nearby. He chooses to have it delivered, enters his payment information, and completes his order. Name Name Distinguishing Characteristics Distinguishing Characteristics Distinguishing Characteristics Context / Starting State Context / Starting State Context / Starting State User Goals User Goals A Good Scenario: • Acts as a bridge between an initial design idea and a solution • Advances the fidelity of an idea • Stands on its own, without explanation • Does not prescribe interface elements in any great detail • Includes a rich description of a person • Includes a rich description of a goal