Scenario-Based Design (Quiz 6) Flashcards
Common Uses of Scenario-Based Design
- Interface Design
- Software engineering
also called “Requirements Elicitation” - Marketing and advertising
- Architecture
- Increasingly in many other areas
What do people within a single persona have in common?
- goals
- attitudes
- behaviors
What does persona describe?
user demographics, education, income, technological experience, job description, goals, needs, desires, typical workday, current situations and frustrations, common activities, likes and dislikes, hobbies and interests…
What question does persona seek to answer?
Who are our users?
Identifying user goals
- Goals that are explicitly stated during interviews
2. Goals inferred from user actions
Goals that are explicitly stated during interviews
What is a good or bad day?
What are the most important things you do?
If it were magic, what would it help you do?
Goals inferred from user actions
- How are people behaving currently?
2. What are they trying to accomplish?
Experience goals
how the user wants to feel while using a product
e.g. “Would like to feel confident and in control”
End goals
tangible outcomes of using the product
e.g. “would like to see my emails and Facebook messages in one display”
Life goals
personal aspirations
e.g. “Would like to retire before the age of 50”
Why Use Scenarios?
Descriptions of people using technology are essential in discussing and analyzing how the technology is (or could be) used to reshape their activities.
Advantages of Scenarios
- Can be created before a system is built.
2. Are rapid-rapid-prototypes of the whole experience.
How to Create Personas
- Collect data about users
- Segment the users
- Develop archetypal characters
Step 1: Collect data
Personas should come from real data from users
Data should be collected to answer the question “Who are our users?”
Should help us identify range of behavioral patterns, environmental factors/constraintsq
What type of data could it be?
Data could be of any type
- Qualitative data
- Quantitative data
- Logical categorizations
Qualitative data
from ethnography, observations, and interviews with real uesrs
Quantitative data
from large scale surveys, pre-existing studies, marketing & customer support reports
Logical categorizations
based on the target audience, expert users, opportunity users
Step 2: Segment Users
Analyze data to identify emerging categories of users
Focus particularly on groupings based on user goals or motivations for technology
Methods for segmenting users
- Exploratory statistics
2. Affinity Diagramming
Step 3: Create Characters
Represent each segment with an archetypal character
Describing the archetype
- Find an archetypal image (e.g. a picture or an abstract character)
- Give the persona a name (e.g. a first name starting with the first letter of the segment)
- Describe user goals related to the product (e.g. presented as a quote)
- Describe user end goals
- Create a bio and describe personal information that affects usage
- Describe technology use, emphasizing skills and needs.
Elements of a Storyboard
- Level of detail
- Inclusion of text
- Inclusion of people & emotions
- Number of frames
- Portrayal of time