Scenario-Based Design (Quiz 6) Flashcards

1
Q

Common Uses of Scenario-Based Design

A
  1. Interface Design
  2. Software engineering
    also called “Requirements Elicitation”
  3. Marketing and advertising
  4. Architecture
  5. Increasingly in many other areas
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What do people within a single persona have in common?

A
  1. goals
  2. attitudes
  3. behaviors
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What does persona describe?

A

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…

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What question does persona seek to answer?

A

Who are our users?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Identifying user goals

A
  1. Goals that are explicitly stated during interviews

2. Goals inferred from user actions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Goals that are explicitly stated during interviews

A

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?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Goals inferred from user actions

A
  1. How are people behaving currently?

2. What are they trying to accomplish?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Experience goals

A

how the user wants to feel while using a product

e.g. “Would like to feel confident and in control”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

End goals

A

tangible outcomes of using the product

e.g. “would like to see my emails and Facebook messages in one display”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Life goals

A

personal aspirations

e.g. “Would like to retire before the age of 50”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Why Use Scenarios?

A

Descriptions of people using technology are essential in discussing and analyzing how the technology is (or could be) used to reshape their activities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Advantages of Scenarios

A
  1. Can be created before a system is built.

2. Are rapid-rapid-prototypes of the whole experience.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

How to Create Personas

A
  1. Collect data about users
  2. Segment the users
  3. Develop archetypal characters
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Step 1: Collect data

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What type of data could it be?

A

Data could be of any type

  1. Qualitative data
  2. Quantitative data
  3. Logical categorizations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Qualitative data

A

from ethnography, observations, and interviews with real uesrs

17
Q

Quantitative data

A

from large scale surveys, pre-existing studies, marketing & customer support reports

18
Q

Logical categorizations

A

based on the target audience, expert users, opportunity users

19
Q

Step 2: Segment Users

A

Analyze data to identify emerging categories of users

Focus particularly on groupings based on user goals or motivations for technology

20
Q

Methods for segmenting users

A
  1. Exploratory statistics

2. Affinity Diagramming

21
Q

Step 3: Create Characters

A

Represent each segment with an archetypal character

22
Q

Describing the archetype

A
  1. Find an archetypal image (e.g. a picture or an abstract character)
  2. Give the persona a name (e.g. a first name starting with the first letter of the segment)
  3. Describe user goals related to the product (e.g. presented as a quote)
  4. Describe user end goals
  5. Create a bio and describe personal information that affects usage
  6. Describe technology use, emphasizing skills and needs.
23
Q

Elements of a Storyboard

A
  1. Level of detail
  2. Inclusion of text
  3. Inclusion of people & emotions
  4. Number of frames
  5. Portrayal of time