On this page & study actions
Assessed progress
Sign in and complete the verified MCQs to track mastery.
Unit 2: Empathize9 min read
Personas are powerful tools in design thinking that help teams develop a deep, shared understanding of their target users. By creating these fictional yet research-based representations, designers and engineers can make informed decisions that prioritize user needs and experiences.
Personas are fictional characters created to represent the different user types that might use a service, product, site, or brand in a similar way. They are not real individuals but are synthesized from extensive user research data. Each persona embodies a specific segment of the target audience, reflecting their demographics, behaviors, goals, motivations, pain points, and experiences.
For example, for a budgeting app aimed at students, a persona named "Amy" might represent an 18-year-old college student who has just started online banking, lives in shared housing, works weekends, and has a goal to save money by stretching $70 to cover her week's groceries. This vivid narrative helps the design team empathize with Amy's specific challenges.
Personas are foundational to a human-centered design approach, directly supporting the "Empathize" phase of design thinking.
Creating impactful personas requires a systematic approach based on solid user research.
A well-crafted persona is often presented as a 1-2 page document, with a written story format preferred over simple bullet points to build deeper empathy.
While distinct, empathy maps are closely related to personas and are often used together to deepen understanding.
An empathy map is a collaborative visualization used to articulate what is known about a particular type of user. It externalizes knowledge about users to create a shared understanding of user needs and aid in decision-making. Traditional empathy maps are split into four quadrants, with the user or persona at the center:
+---------------------+---------------------+ | SAYS | THINKS | | What the user says | What the user thinks| | out loud. | (may not vocalize). | +---------------------+---------------------+ | DOES | FEELS | | What actions the | What emotions the | | user takes. | user experiences. | +---------------------+---------------------+
While both are tools for understanding users, they serve distinct purposes:
Personas are not just static documents; they are living tools that feed into subsequent design activities, such as creating user stories and user journey maps.
A user story is a simplified, fictional, one-sentence description of a requirement told from the persona's point of view. It describes the type of user, what they want, and why, inspiring and informing design decisions.
The standard format for a user story is: As a [type of user/persona], I want to [perform an action], so that [I can achieve a goal/benefit].
Example:
User stories act as a checklist to ensure the product addresses key problems and provides clear benefits for the target users.
A user journey map is a visual representation of the entire experience a user (often a specific persona) has while trying to achieve a specific goal. It typically charts the user's path, from their initial contact to the final interaction and beyond, highlighting their actions, thoughts, feelings, pain points, and opportunities for improvement at each stage.
Building on personas and user stories, journey maps help designers:
For example, a user journey map for Amy using the budgeting app might illustrate her path from downloading the app, setting up her accounts, budgeting for groceries, tracking expenses throughout the week, encountering an unexpected bill, and reviewing her spending at the end of the month. Each step would detail her actions (Does), thoughts (Thinks), and emotions (Feels), revealing critical moments where the app can either support or frustrate her.
While personas are primarily a design tool, their attributes can be conceptually represented in code to illustrate how a development team might think about user data or requirements programmatically. This example shows a simple C++ structure for a Persona.
This code snippet defines a Persona structure with relevant attributes like name, age, mainGoal, painPoints, and scenario. It then creates an instance of "Amy" (our college student persona) and prints her details. This demonstrates how a developer might conceptually store and access persona-related data, influencing feature development even at a low level. No complex mathematical operations are present as they are not relevant to the conceptual representation of personas.
Fictional characters created from user research that represent distinct user types who interact with a product or service in similar ways.
To help designers understand users' needs, experiences, behaviors, and goals, fostering empathy and guiding user-centered design decisions.
A collaborative visualization tool that externalizes knowledge about users, typically divided into four quadrants: Says, Thinks, Does, and Feels.
Personas define *who* the user is, providing a holistic profile, while empathy maps detail *what* that persona says, thinks, does, and feels in a specific context.
A short, fictional, one-sentence story told from a persona's point of view, outlining a desired feature or functionality and its benefit.
Test your understanding with 5 questions
What is the primary purpose of creating personas in the design thinking process?
Which of the following is NOT a traditional quadrant of an Empathy Map?
How do user personas primarily differ from empathy maps?
A user story is typically written from whose point of view?
Which of the following best describes the 'Does' quadrant of an empathy map?
6 Modules
6 Modules