Say it like this
- We need to define our user personas before we start designing.
- This feature aligns well with our primary user persona.
- Let's validate this against our user personas.
- The user persona tells us what problems to solve.
Use it at work
Product
- Our main user persona is a busy engineering manager.
- Let's design for this user persona.
Research
- We built three user personas from interviews.
- Which persona is this feature for?
Pushing back
- This persona isn't based on real data.
- Let's update the personas after the survey.
Don't say this
A persona should be specific and include behavior and goals, not just demographics.
Practice
Try it
4 quick exercises
1. We should _______ three _______ before we start the design phase.
2. Which sentence uses user persona incorrectly?
3. Your team is starting a new product. How would you naturally phrase why you need user personas?
4. Rewrite this in natural tech English using 'user persona': 'We know our customers are busy and want things to be simple and fast.'
Say it out loud
Phrase 1 of 4
"We need to define our user personas before we start designing."
We don't save your recording. The word check uses your browser's speech recognition.
More about user persona
Real examples(4)
- in a design meeting
"Our user persona Sarah checks email multiple times a day, so we should make notifications easy to manage."
- in a standup
"I reviewed the feature request against our user personas and it doesn't match what they actually need."
- in a strategy discussion
"We should build the API based on our developer user persona, who values documentation and clear error messages."
- in a code review comment
"Before we ship this, does it actually solve the problem our main user persona faces?"
More mistakes(2)
Handle with care. Often confused with user profile or target audience; a persona is a fictional representation with specific behaviors and goals, not just demographic data.
- ✕We do not need user personas because we know our users.✓We should create formal user personas based on real data from user interviews.
Assumptions differ from documented personas. Written personas keep teams aligned and reduce bias.
- ✕The user persona wants us to add more features.✓Based on our user persona, we should add this feature because it solves their main pain point.
Personas represent user needs and goals, not demands. Frame decisions around solving actual problems.
Other forms(3)
- user persona noun
"We created five user personas during the research phase."
- user personas noun (plural)
"Our user personas guide every product decision we make."
- user persona's noun (possessive)
"The user persona's primary goal is to save time on repetitive tasks."
Often used with(5)
- create a user persona · to develop or build a persona based on research
- primary user persona · the main or most important persona a product targets
- user persona research · the process of gathering data to develop personas
- align with the user persona · to match or be consistent with a persona's needs
- validate against user personas · to check if something matches what personas need
Similar words(4)
- user profile · Similar but often less detailed; profile may be more data-focused than persona.
- buyer persona · More sales-focused; user persona is broader and applies to all users.
- customer archetype · Similar meaning but archetype is more general; persona is more specific to a product.
- target audience · Broader term; audience refers to demographic group, persona is a detailed character representation.
Opposites(2)
- actual user
- real customer
Questions(5)
- What is the difference between a user persona and a target audience?
- A target audience is a broad demographic group (age, location, income). A user persona is a detailed fictional character based on real research that includes behaviors, goals, pain points, and motivations. Personas are more specific and actionable for product teams.
- How do you create a user persona?
- Create user personas by conducting user research through interviews, surveys, and data analysis. Identify patterns in user behavior and goals. Then develop a fictional character that represents that group, including a name, background, goals, frustrations, and daily routine. Document it clearly so your team can reference it.
- Why are user personas important in tech?
- User personas keep product teams focused on real user needs instead of guesses. They help align designers, engineers, and product managers on who they are building for and why. During meetings and feature decisions, personas provide objective reference points and reduce personal bias.
- How many user personas should a product have?
- Most products have 3 to 5 main personas. One is usually the primary persona that the product is designed for first. Too many personas dilute focus; too few miss important user segments.
- Is user persona formal or informal?
- User persona is neutral and professional, used in both formal presentations and casual team conversations. It is common in business, product, and tech contexts but remains accessible to non-specialists.
