User Research - Personas Flashcards
Semi-structured Qualitative Interviews
- Applied when you need to understand users’ point of view while naturally interacting
- Possible to understand users’ values, perceptions and experiences
- Prepare a set of topics to be covered and allow the introduction of new ones or to go deeper in some topics
Semi-structured Qualitative Interviews - Pros
- Can be very informative and helpful, but only if they are used correctly and for the right things.
- It is possible to ask why but sometimes difficult to achieve the what
Semi-structured Qualitative Interviews - Cons
Not to good to ask about unremarkable activities
When should Semi-structured Qualitative Interviews be used?
In exploration phase, in order obtain better understanding of your users and their routine.
Context is important because it is easier to capture the meaning and needs in tasks. This kind of thread raises the opportunity to identify personas and scenarios.
Semi-structured Qualitative Interviews - Concept Exploration
- Explore concept ideas during the early stages of the development process by using low fidelity prototypes
- Ask users about problems and desires they have about your problem space, avoid asking for evaluation
- When asking about areas concerned with your concept but not revealing the one
In addition, with observations
* If you are in the context with the user, you can ask them for clarification after they do a specific task
Steve Portigal about Follow-up Questions
ideally—”you should only ask one kick-off question and allow the rest of the interview to flow naturally from there”
Persona: what is?
Used to characterise users of an interactive system during design.
A persona is a short description of a fictional character that illustrates a known group of a product’s users. The character is named, pictured and given biographical details.
Their pattern behaviours, needs and goals when interacting with the product are outlined.
All these are derived by the user research!
Persona: Characteristics
- Are not real people, but they represent them throughout the design process
- Are hypothetical archetypes of actual users
- Although they are imaginary, they are defined with significant rigor and precision
- Make up their names and personal details
How to create a persona:
Personas are defined by their goals.
Start with a reasonable approximation and quickly converge on a believable population of personas.
Give your persona a name.
Stereotypical personas are more effective if the stereotyping lends more credence to the persona.
When to create a persona?
- Do it early on the project
- Can be used to inform requirements, ideation, user
journeys, visual design, etc. - Should be developed by the whole team!
Personas’ Generation Process
- Understand your product’s users with research and statistics
- Examine data for themes and patterns
- Arrange those patterns around individual characters
- Bring characters to life with biographical information and imagery
What to include in a Persona:
- Name and Gender
- Image
- Age
- Biography
- Location
- Occupation
- Salary
- Personal Quote
- Description of User Segement
- Attitude to Technology
- Context of Use
- Customer Segmentation Data
- Key Drivers
- Key Goals and Needs
- Pain Points
What is the Primary Persona?
- The primary persona is the individual who is the focus of the design.
- To be primary, a persona is someone who must be satisfied but who cannot be satisfied with an interface designed for any other persona.