π Lecture 20 β User Research Part-II
π Overview: This lecture continues the study of qualitative research techniques, focusing specifically on the ethnographic field study method. It explores the user-centered design philosophy and provides detailed guidance on conducting ethnographic interviews, including preparation, frameworks, and practical implementation strategies for gathering rich user data in natural contexts.
ποΈ Topics Covered
The lecture covers the user-centered approach and its three core principles, ethnographic field study methods including the three dimensions framework (distributed coordination, plans and procedures, awareness of work), contextual design and contextual inquiry techniques, and the comprehensive process of preparing for ethnographic interviews including persona hypothesis development, identifying candidates, and creating interview plans.
π Lecture Summary
20.1 User-Centered Approach
The user-centered approach means that real users and their goals, not just technology, should be the driving force behind product development. A well-designed system should make the most of human skill and judgment, be directly relevant to the work at hand, and support rather than constrain the user. This is less a technique and more a philosophy.
In 1985, Gould and Lewis laid down three principles they believed would lead to a "useful and easy to use computer system":
- Early focus on users and tasks: Understand who the users will be by directly studying their cognitive, behavioral, anthropomorphic, and attitudinal characteristics through observing users doing normal tasks and studying the nature of those tasks.
- Empirical measurement: Early in development, observe and measure the reactions and performance of intended users to printed scenarios and manuals. Later, users interact with simulations and prototypes while their performance and reactions are observed, recorded, and analyzed.
- Iterative design: When problems are found in user testing, fix them and carry out more tests and observations. Design and development cycles of "design, test, measure, and redesign" are repeated as often as necessary.
Applying ethnography in design
Ethnography is a method that comes originally from anthropology and literally means "writing the culture." It displays the social organization of activities to understand work. It aims to find the order within an activity rather than impose any framework of interpretation. Observers immerse themselves in the users' environment, participate in day-to-day work, join conversations, attend meetings, and read documents. The aim is to make the implicit explicit.
π Definition β Ethnography: A broad-based approach where users are observed as they go about their normal activities, with observers immersing themselves in the users' environment to understand the social organization of work and make implicit practices explicit.
Beynon-Davies suggested ethnography can be associated with development as:
- Ethnography of development: Studies of developers themselves and their workplace
- Ethnography for development: Studies that can be used as a resource for development
- Ethnography within software development: Techniques integrated into methods for development
π‘ Why this matters: The ethnographic experience reveals information missed by other methods, such as how people do "real" work versus formal procedures, the nature of collaboration, awareness of others' work, and implicit goals not recognized by workers themselves.
π Example: Heath et al. studied dealers in a stock exchange to see whether proposed technological support for market trading was suitable. They observed the process of writing tickets to record deals. While others suggested introducing touch screens and headphones, Heath et al. discovered these proposals were misguided β touch screens would reduce information availability to others, and headphones would impede dealers' ability to monitor one another. They recommended pen-based mobile systems with gesture recognition instead.
"In some way, the goals of design and the goals of ethnography are at opposite ends of a spectrum. Design is concerned with abstraction and rationalization. Ethnography, on the other hand, is about detail."
20.2 Ethnography Framework
The ethnographic framework has been developed specifically to help structure the presentation of ethnographies in a way that enables designers to use them. This framework has three dimensions:
1. Distributed coordination Focuses on the distributed nature of tasks and activities, and the means and mechanisms by which they are coordinated. This has implications for the kind of automated support required.
2. Plans and procedures Focuses on organizational support for work, such as workflow models and organizational charts, and how these support the work. Understanding this impacts how the system is designed to utilize this kind of support.
3. Awareness of work Focuses on how people keep themselves aware of others' work. Being aware of others' actions and work activities can be a crucial element of doing a good job. Implications relate to the sharing of information.
An alternative approach is to train developers to collect ethnographic data themselves, giving designers first-hand experience of the situation. Two methods provide support for this:
Coherence
The coherence method combines experiences of using ethnography to inform design with developments in requirements engineering. It is intended to integrate social analysis with object-oriented analysis from software engineering.
π Definition β Viewpoints: Within Coherence, these are focus questions for each of the three framework dimensions, intended to guide the observer to particular aspects of the workplace.
π Definition β Concerns: A kind of goal representing criteria that guide the requirements activity. These are addressed within each appropriate viewpoint. The concerns are:
- Paper work and computer work: Embodiments of plans and procedures, and mechanisms for developing and sharing awareness of work
- Skill and the use of local knowledge: The "workarounds" developed in organizations that are at the heart of how real work gets done
- Spatial and temporal organization: The physical layout of the workplace and areas where time is important
- Organizational memory: Formal documents are not the only way things are remembered β individuals may keep their own records, or there may be local gurus
Contextual design
Contextual design was developed to handle the collection and interpretation of data from fieldwork with the intention of building a software-based product. It provides a structured approach to gathering and representing information from fieldwork.
Contextual design has seven parts:
- Contextual inquiry
- Work modeling, consolidation
- Work redesign
- User environment design
- Mockup
- Test with customers
- Putting it into practice
Contextual inquiry
Contextual inquiry is based on a master-apprentice model of learning: observing and asking questions of the users as if she is the master craftsman and he interviews the new apprentice. Four basic principles for engaging in ethnographic interview:
- Context: Interact with and observe the user in their normal work environment, filled with the artifacts they use each day
- Partnership: The interview should take the tone of a collaborative exploration, alternating between observation and discussion of its structure and details
- Interpretation: Much of the designer's work is reading between the lines of facts gathered about user's behaviors, their environment, and what they say β but avoid assumptions without verifying with users
- Focus: The designer needs to subtly direct the interview to capture data relevant to design issues
Improving on contextual inquiry
Process improvements for a more highly leveraged research phase:
- Shortening the interview process: Interviews as short as one hour are sufficient with about six well-selected users for each hypothesized role
- Using smaller design teams: More effective to conduct interviews sequentially with the same designers (two or three)
- Identifying goals first: Ethnographic interviews should first identify and prioritize user goals before determining tasks
- Looking beyond business contexts: Ethnographic interviews are also possible in consumer domains
20.3 Preparing for Ethnographic Interviews
Ethnographic interviews take the spirit of anthropological research and apply it on a micro level β understanding the behaviors and rituals of people interacting with individual products.
Identifying candidates
Designers must capture an entire range of user behaviors regarding a product. Based on information from stakeholders, SMEs, and literature reviews, designers create a hypothesis that serves as a starting point for determining what sorts of users to interview.
Kim Goodwin coined this the persona hypothesis, the first step towards identifying and synthesizing personas. The persona hypothesis is based on likely behavioral differences, not demographics, but takes into consideration identified target markets and demographics.
π Definition β Persona hypothesis: A first cut at defining the different kinds of users (and sometimes customers) for a product in a particular domain. It serves as a basis for an initial set of interviews and attempts to address three questions:
- What different sorts of people might use this product?
- How might their needs and behaviors vary?
- What ranges of behavior and types of environments need to be explored?
Roles in business and customer domains
For business products, roles β common sets of tasks and information needs related to distinct classes of users β provide an important initial organizing principle. For example, in an enterprise portal: people who search for content, people who upload and update content, and people who technically administer the portal.
Unlike business users, consumers don't have concrete job descriptions. Their roles map more closely to lifestyle choices, and it is possible for consumer users to assume multiple roles even for a single product.
Behavioral and demographic variables
Beyond roles, a persona hypothesis seeks to identify behavioral variables that might distinguish users based on their needs and behaviors. Examples: frequency of shopping, desire to shop, motivation to shop.
Another helpful approach is making use of demographic variables such as ages, locations, gender, and incomes of target markets.
Domain expertise versus technical expertise
Important behavioral distinction: technical expertise (knowledge of digital technology) versus domain expertise (knowledge of a specialized subject area pertaining to a product). Domain support may be a necessary part of the product's design, as well as technical ease of use.
Environmental variables
Cultural differences between organizations, especially for business products. Examples: company size (small to multinational), IT presence (ad hoc to draconian), security level (lax to tight).
20.4 Putting a Plan Together
After creating a persona hypothesis with potential roles, behavioral, demographic, and environmental variables, create an interview plan that can be communicated to the person in charge of providing access to users.
Each identified role, behavioral variable, demographic variable, and environmental variable should be explored in four to six interviews (sometimes more if a domain is particularly complex). However, interviews can overlap β interviewing a female in her twenties who loves to shop counts for multiple variables. By cleverly mapping variables to interviewee screening profiles, the number of interviews can be kept manageable.
β Key Takeaways
The user-centered approach demands that real users and their goals drive product development through early focus on users, empirical measurement, and iterative design cycles. Ethnography is the most immersive qualitative technique, making implicit workplace behaviors explicit by observing users in their natural context. The three-dimensional ethnographic framework (distributed coordination, plans and procedures, awareness of work) helps structure ethnographic data for design use, while contextual design and coherence provide structured approaches for translating fieldwork into design specifications. Successful ethnographic interviews require careful preparation through persona hypothesis development, identifying diverse user types across behavioral, demographic, and environmental variables, and planning 4-6 interviews per variable with overlapping coverage.
π§ Quick Revision Questions
- What are the three principles laid down by Gould and Lewis for creating useful and easy-to-use computer systems?
- What is the fundamental difference between the goals of design and the goals of ethnography?
- What were Heath et al.'s findings regarding proposed technological support for stock exchange dealers, and what alternative did they recommend?
- What are the four concerns in the Coherence method, and what does each represent?
- What is a persona hypothesis, and what three questions does it attempt to address?
π Lecture 21 β User Research Part-III
π Overview: This lecture completes the user research series by focusing on ethnographic interview techniques and other qualitative research methods. It explains how to conduct effective interviews that reveal user goals, behaviors, and workflows, while also introducing alternative research approaches like focus groups and market demographics for comprehensive user understanding.
ποΈ Topics Covered
The lecture covers methodologies for conducting ethnographic interviews including securing interviews, interview team structure, and timing. It details the three phases of ethnographic interviews (early, mid, late-phase) with their respective questioning approaches. Basic interview methods are presented along with four categories of interview questions: goal-oriented, system-oriented, workflow-oriented, and attitude-oriented. The lecture also surveys types of qualitative research, other research types including focus groups and market demographics, and concludes with a comparison table of different research techniques.
π Lecture Summary
21.1 How to conducting ethnographic interviews
Securing interviews can be achieved through three primary channels: stakeholders, market or usability research firms, and friends and relatives. These sources help researchers gain access to appropriate interview participants.
For interview teams and timings, the recommended structure involves 2 interviewees per day, with each interview lasting 1 hour, allowing for a maximum of 6 interviews per day when working in pairs.
21.2 Phases of ethnographic interviews
The interview process moves from beginning to end along two dimensions: from structural issues to specific issues, and from goal-oriented issues to task-oriented issues.
Early-phase interviewing is exploratory, focused on gaining domain knowledge through open-ended questions that allow participants to share broad perspectives without constraint.
Mid-phase interviewing shifts toward identifying patterns of use by asking clarifying questions and more focused questions that build on initial findings.
Late-phase interviewing aims to confirm patterns of use and clarify user roles and behaviors through closed-ended questions that validate or challenge emerging hypotheses.
21.3 Basic interview methods
Effective interviews follow several key principles: interview where the action happens (in the user's natural environment), avoid a fixed set of questions (remain flexible), focus on goals first, tasks second (understand intent before actions), avoid making the user a designer (don't ask users to solve design problems), avoid discussions of technology (focus on user experience), encouraging storytelling (narratives reveal context), ask for a show-and-tell (demonstrations provide rich data), and avoid leading questions (don't bias responses).
Goal-oriented questions explore user objectives:
- Opportunity: "What activities currently waste your time?"
- Goals: "What makes a good day? A bad day?"
- Priorities: "What is the most important to you?"
- Information: "What helps you make decisions?"
System-oriented questions examine product interaction:
- Function: "What are the most common things you do with the product?"
- Frequency: "What parts of the product do you use most?"
- Preference: "What are your favorite aspects of the product? What drives you crazy?"
- Failure: "How do you work around problems?"
- Expertise: "What shortcuts do you employ?"
Workflow-oriented questions reveal process and sequence:
- Process: "What did you do when you first came into today? And after that?"
- Occurrence and recurrence: "How often do you do this? What things do you do weekly, monthly but not every day?"
- Exceptions: "What constitutes a typical day? What would be an unusual event?"
Attitude-oriented questions probe emotions and motivations:
- Aspiration: "What do you see yourself doing five years from now?"
- Avoidance: "What would you prefer not to do? What do you procrastinate on?"
- Motivation: "What do you enjoy most about your job (or lifestyle)? What do you always tackle first?"
π‘ Why this matters: These question categories systematically uncover different layers of user experienceβfrom surface-level tasks to deep-seated goals and attitudesβensuring comprehensive understanding.
21.4 Types of qualitative research
The lecture identifies several types of qualitative research:
- Stakeholder interview β interviewing people with vested interest in the product
- Subject matter experts (SME) interviews β gathering specialized domain knowledge
- User and customer interviews β direct feedback from end users
- Literature review β studying existing documentation and research
- Product/prototype and competitive audits β examining existing solutions
- User observation/ethnographic field studies β watching users in natural settings
21.5 Others types of research
Focus groups are used by marketing organizations for traditional product marketing. In this method, representative users are gathered in a room, shown a product and reactions gauged, with reactions recorded by audio/video. The lecture notes limitations of this approach (such as group dynamics potentially skewing individual opinions).
Market demographics and segments research asks "What motivates people to buy?" This is determined by market segmentation that group people by distinct needs and determines who will be receptive to what marketing message or a particular product. Data includes:
- Demographic data: Race, education, income, location
- Psychographic data: Attitude, lifestyle, values, ideology
Usability and user testing is mentioned as a third type of research, though not elaborated in this lecture.
21.6 Comparison of different techniques
The lecture provides a comparison table evaluating different research techniques:
Interviews:
- Good for: Exploring issues
- Kind of data: Some quantitative but mostly qualitative data
- Advantages: Interviewer can guide interviewee if necessary; encourages contact between developers and users
- Disadvantages: Time consuming; artificial environment may intimidate interviewee
Studying documentation:
- Good for: Learning about procedures, regulations and standards
- Kind of data: Quantitative
- Advantages: No time commitment from users required
- Disadvantages: Day-to-day working will differ from documented procedures
Naturalistic observation:
- Good for: Understanding context of user activity
- Kind of data: Quantitative
- Advantages: Observing actual work gives insights that other techniques can't give
- Disadvantages: Very time consuming; huge amounts of data
Focus groups and workshops:
- Good for: Collecting multiple viewpoints
- Kind of data: Some quantitative but mostly qualitative data
- Advantages: Highlights areas of consensus and conflict; encourages contact between developers and users
- Disadvantages: Possibility of dominant characters
Modeling Research: Use ethnographic research techniques to obtain qualitative data:
- User observation
- Contextual interviews
Qualitative data derived from this research informs:
- Usage patterns: Sets of observed behaviors that categorize modes of use
- Goals: Specific and general desired outcomes of using the product
- Personas: (implied as the ultimate output of synthesizing this data)
β Key Takeaways
The ethnographic interview process is a structured yet flexible methodology that progresses through three phasesβearly (exploratory, open-ended), mid (pattern identification, focused), and late (confirmation, closed-ended)βeach requiring different questioning approaches. Effective interviews prioritize goals over tasks, avoid making users designers, and use storytelling and show-and-tell techniques to capture rich contextual data. The four categories of interview questions (goal-oriented, system-oriented, workflow-oriented, and attitude-oriented) systematically uncover different dimensions of user experience. Alternative research methods like focus groups and market demographics serve different purposes and have distinct advantages and disadvantages compared to interviews and observation. Ultimately, all ethnographic research aims to produce qualitative data that reveals usage patterns and user goals, which form the foundation for creating personas and designing user-centered products.
π§ Quick Revision Questions
- What are the three phases of ethnographic interviewing, and what type of questions is each phase characterized by?
- List at least five of the basic interview methods discussed in the lecture (principles for conducting effective interviews).
- What are the four categories of interview questions, and give one example question for each category?
- What are the advantages and disadvantages of using naturalistic observation compared to interviews?
- How does market demographics and segmentation research differ from ethnographic interviews in terms of what it measures and why?
π Lecture 22 β User Modeling
π Overview: This lecture introduces the concept of user modeling as a powerful interaction design tool, focusing on personas as composite archetypes based on behavioral data from real users. It explains why models are necessary, how personas overcome common design problems, and provides a detailed framework for constructing and using personas to create user-centered products.
ποΈ Topics Covered
The lecture covers the importance of modeling in design, the concept and strengths of personas as user models, how personas resolve user-centered design issues like the elastic user and self-referential design, the relationship between personas and other user representations, the role of goals in driving behavior including life, experience, and end goals, and a step-by-step process for constructing personas with various types.
π Lecture Summary
22.1 Why Model?
Models are powerful tools for representing complex structures and relationships, helping designers make sense of unstructured raw data. Good models emphasize salient features and de-emphasize less significant details. Because we design for users, we must understand and visualize their relationships with each other, their social and physical environment, and the products we design.
Just as physicists create models of the atom from observed data, designers create models of users based on observed behaviors and intuitive synthesis of patterns in the data. Personas provide this formalization, allowing designers to systematically construct patterns of interaction that match user behaviors, mental models, and goals.
π‘ Why this matters: Without models, designers have no organizing principle for user data, leading to unfocused design decisions.
22.2 Personas
To create a product for a broad audience, logic suggests making it as broad in functionality as possible. This logic is flawed. The best way to accommodate a variety of users is to design for specific types of individuals with specific needs. Broadly extending functionality increases cognitive load and navigational overhead for all users.
π Example: Designing an automobile that pleases every possible driver results in a car with every feature that pleases nobody. Designing different cars for different people with specific goals creates satisfying designs for others with similar needs.
The key is choosing the right individuals whose needs represent a larger set of key constituents and prioritizing design elements to address the most important users without inconveniencing secondary users.
Strengths of personas as a design tool:
- Determine what a product should do and how it should behave
- Communicate with stakeholders, developers, and other designers
- Build consensus and commitment to the design
- Measure the designβs effectiveness
- Contribute to other product-related efforts like marketing and sales
Personas and user-centered design: Personas resolve three issues:
The elastic user: The term "user" is impreciseβevery team member has their own conception. This "user" becomes elastic, bending to fit whoever has the floor. Designing for the elastic user gives developers license to code as they please. Real users and personas are not elastic; they have specific requirements based on goals, capabilities, and contexts.
Self-referential design: This occurs when designers project their own goals, motivations, skills, and mental models onto a product. Most "cool" product designs fall into this category. Programmers apply self-referential design when creating implementation-model products that only they understand.
Design edge cases: Personas help prevent designing for edge casesβsituations that might happen but usually won't for target personas. Edge cases must be programmed for but should never be the design focus.
Personas are based on research: The primary source of data must be from ethnographic interviews, contextual inquiry, or similar dialogues with actual and potential users. Supporting data includes interviews outside use contexts, stakeholder information, market research, market segmentation models, and literature reviews. However, nothing replaces direct interaction with and observation of users in their native environments.
Personas are represented as individuals: Personas are user models represented as specific, individual humans, synthesized from observations of real people. They engage the empathy of the development team toward the human target of design. Empathy is critical for designers making decisions based on both cognitive and emotional dimensions.
Personas represent classes of users in context: Personas encapsulate a distinct set of usage patterns identified through analysis of ethnographic interviews. They are composite user archetypes assembled by clustering related usage patterns observed across individuals in similar roles.
Personas and reuse: Personas must be context-specificβfocused on behaviors and goals related to a specific product domain. They cannot easily be reused across products, even closely linked ones, because behavioral focus may differ.
Archetypes versus stereotypes: Don't confuse persona archetypes with stereotypes. Stereotypes represent designer biases and assumptions, not factual data. Personas developed with inadequate research risk becoming stereotypical caricatures. Personas must be developed and treated with dignity and respect.
Personas explore ranges of behavior: Personas do not seek an average user but identify exemplary types of behaviors along identified ranges. Designers must identify a collection or cast of personas associated with any given product.
Personas must have motivations: All humans have motivations that drive behaviors. Personas capture these motivations in the form of goals. Understanding why a user performs certain tasks gives designers power to improve or eliminate those tasks while still accomplishing the same goals.
Personas versus user roles: User roles are abstractions defining relationships between a class of users and their problems. Problems with user roles include difficulty identifying relationships in the abstract, focus on tasks while neglecting goals, and difficulty bringing models together as a coherent tool. Personas incorporate the same relationships but express them in terms of goals and examples in narrative.
Personas versus user profile: User profiles are often a name attached to brief demographic data with a short fictional paragraph. This is likely a user stereotype and not useful as a design tool. Personas use names and details sparingly as narrative tools to communicate real data.
Personas versus market segments: Market segments are based on demographics and distribution channels; design personas are based on behaviors and goals. Marketing personas shed light on the sales process; design personas shed light on the development process.
User personas versus non-user personas: A frequent error is targeting people who review, purchase, or administer the product but are not end users. Designing for the purchaser is a frequent mistake. For enterprise systems requiring administrators, it's appropriate to create non-user personas with expanded research.
22.3 Goals
If personas provide context for observed behaviors, goals are the drivers behind those behaviors. A persona without goals can serve as a communication tool but is useless as a design tool. User goals serve as a lens through which designers must consider product functions.
Goals motivate usage patterns: Goals provide the answer to why and how personas desire to use a product and serve as shorthand for complex behaviors.
Goals must be inferred from qualitative data: You cannot ask a person directly what their goals areβthey either cannot articulate them or won't be accurate. Designers must reconstruct goals from observed behaviors, answers to other questions, non-verbal cues, and environmental clues.
22.4 Types of Goals
Goals come in many varieties. The most important from a user-centered design standpoint are user goals, which are first priority, especially for consumer products.
User goals:
- Life goals
- Experience goals
- End goals
Life goals: Represent personal aspirations that typically go beyond the product context. They represent deep drives and motivations explaining why the user seeks to accomplish end goals.
π Examples: Be the best at what I do; Get onto the fast track; Learn all there is to know about this field; Be a paragon of ethics, modesty, and trust.
Life goals rarely figure directly into interface design but are worth keeping in mind.
Experience goals: Simple, universal, personal goals expressing how someone wants to feel while using a product or the quality of their interaction.
π Examples: Don't make mistakes; Feel competent and confident; Have fun.
Experience goals represent unconscious goals that people bring to any software product without consciously realizing it.
End goals: Represent the user's expectations of tangible outcomes from using a specific product.
π Examples: Find the best price; Finalize the press release; Process the customer's order; Create a numerical model of the business.
End goals must be met for users to think a product is worth their time and money.
Non-user goals:
- Customer goals
- Corporate goals
- Technical goals
Customer goals: Consumer customers often have concerns about safety and happiness. Enterprise customers (IT managers) often have concerns about security, ease of maintenance, and customization.
Corporate goals: Business requirements at a high level.
π Examples: Increase profit; Increase market share; Defeat the competition; Use resources more efficiently; Offer more products or services.
Technical goals: Goals that ease the task of software creation, often taking precedence at the expense of users' goals.
π Examples: Save money; Run in a browser; Safeguard data integrity; Increase program execution efficiency.
22.5 Constructing Personas
Creating believable and useful personas requires detailed analysis and creative synthesis. The process involves seven steps:
1. Revisit the persona hypothesis: Compare patterns in the data to assumptions made in the persona hypothesis. Were possible roles distinct? Were behavioral variables valid? If data varies from assumptions, add, subtract, or modify roles and behaviors, potentially conducting additional interviews.
2. Map interview subjects to behavioral variables: Map each interviewee against each variable range that applies. The precision is less critical than identifying placement of interviewees in relationship to each other. The way multiple subjects cluster on each variable axis is significant.
3. Identify significant behavior patterns: Look for clusters of subjects occurring across multiple ranges or variables. A set clustering in six to eight variables likely represents a significant behavior pattern forming the basis of a persona. For a pattern to be valid, there must be a logical or causative connection between clustered behaviors.
4. Synthesize characteristics and relevant goals: For each significant pattern, synthesize details describing the potential use environment, typical workday, current solutions, frustrations, and relevant relationships. Use bullet points based on observed behaviors. Add a persona's first and last name (evocative, not stereotypical). Goals are the most critical detail, derived from analyzing the group of behaviors.
5. Check for completeness: Ensure the cast of personas covers the range of behaviors and user types identified in research.
6. Develop narratives: Third-person narrative is powerful for conveying attitudes, needs, and problems. A typical narrative should be one to two pages, not a short story. It quickly introduces the persona and briefly sketches a day in their life, including peeves, concerns, and interests relevant to the product. Choose photographs to make personas feel more real.
7. Designate persona types: There are six types, typically designated in this order:
- Primary: The primary target for the interface design. Only one per interface, though products may have multiple interfaces with different primary personas.
- Secondary: Satisfied by the primary persona's interface if one or two specific additional needs are addressed. An interface typically has zero to two secondary personas.
- Supplemental: User personas that are not primary or secondary, completely satisfied by the primary interface. Political personas often become supplemental.
- Customer: Address needs of customers, not end users. Typically treated as secondary personas, though may be primary for administrative interfaces.
- Served: Not users of the product but directly affected by its use. Track second-order social and physical ramifications. Treated like secondary personas.
- Negative: Not users of the product, used rhetorically to communicate who should not be the design target. Good candidates include technology-savvy early-adopter personas for consumer products and IT specialists for enterprise products.
β Key Takeaways
The most critical concept is that personas are composite archetypes based on ethnographic research, not stereotypes or fictional characters, and they serve as the foundation for user-centered design by providing a precise, empathetic design target. Goalsβspecifically life, experience, and end goalsβare the drivers of user behavior and must be inferred from qualitative data, not asked directly, making them essential for translating observed behaviors into design decisions. Personas resolve critical design problems including the elastic user, self-referential design, and designing for edge cases, while providing a common language for communication across the development team. The persona construction process follows seven systematic steps from revisiting hypotheses through designating persona types, with primary, secondary, and other types each serving specific roles in the design framework. Finally, personas must be context-specific, based on behavioral data (not demographics), and treated with dignity to avoid degrading into stereotypes.
π§ Quick Revision Questions
- What are the three user-centered design issues that personas help resolve, and how does each issue typically manifest in product development?
- What are the three categories of user goals, and why must goals be inferred from qualitative data rather than asked directly?
- How do personas differ from user roles, user profiles, and market segments in terms of their basis and purpose in design?
- What are the seven steps in constructing personas, and what is the significance of the "clustering" step in Step 2?
- List and briefly describe the six types of personas, explaining the primary distinction between primary, secondary, and supplemental personas.