What a User Persona Really Is
A user persona is not a demographic profile. It is not age 25-34 female living in urban areas. That is a target segment, not a persona. A user persona is a fictional but realistic character that represents your ideal customer. It includes their goals, frustrations, behaviors, and decision-making process.
The purpose is empathy. When you are making product decisions -- which feature to build next, what copy to write, how to price your product -- you should be able to say this is what Sarah would want or this would frustrate Mark. If your persona is just a demographic range, it cannot guide decisions.
The best personas come from real conversations with real customers, not from assumptions at your desk. Talk to 10-15 people who fit your target market before creating a persona. Everything in the persona should be grounded in something someone actually said to you.
The Template
Here is the template. Below it, we have filled in two examples to show what good personas look like.
Example 1: SaaS Product Manager
Name & Role: Sarah Chen -- Senior Product Manager at a B2B SaaS company (50-200 employees). Manages a product used by 500+ businesses.
Demographics: 32, San Francisco, $145K salary. CS degree. Lives with partner, no kids.
Goals: Ship features faster without sacrificing quality. Reduce the time from idea to deployed feature. Get promoted to Director of Product within 2 years.
Frustrations: Too many tools that do not talk to each other. Spends 3 hours/day in meetings instead of doing actual product work. Engineering estimates are always wrong but she has no way to verify them.
Current Solutions: Jira for tickets ($14/user/mo), Notion for docs (free), Figma for design (free), Slack for communication. Frustrated with the fragmentation.
Buying Triggers: New quarter planning. A major feature ships late. Engineering team grows and coordination gets harder.
Objections: Another tool? My team has tool fatigue. Will this actually integrate with what we already use? I do not have budget authority for tools over $500/mo.
Preferred Channels: Lenny Newsletter, Twitter/X product community, Product Hunt, peer recommendations in PM Slack groups.
Example 2: Miami Restaurant Owner
Name & Role: Carlos Mendez -- Owner of two casual dining restaurants in Doral, Miami. 12 years in the restaurant industry.
Demographics: 41, Miami-Dade County, $180K combined revenue. Venezuelan-American, bilingual English/Spanish. Married, two kids.
Goals: Increase delivery revenue without hiring more staff. Open a third location within 18 months. Spend less time on operations and more time on the food.
Frustrations: Managing 4 delivery tablets simultaneously. Order errors cost $800+/month. Cannot get a clear picture of which delivery platform is most profitable. Staff turnover means constant retraining.
Current Solutions: Manually checking each tablet. Uses a notebook to track daily orders. Wife handles the accounting in QuickBooks. Pays an extra staff member $2,400/mo to manage delivery operations.
Buying Triggers: A bad week of delivery errors. Seeing a competitor using a solution that works. Delivery platform raising their commission rates.
Objections: I have been burned by tech promises before. Will this actually work with all my delivery platforms? I do not have time to learn a new system. Can someone explain this in Spanish?
Preferred Channels: WhatsApp groups with other restaurant owners. Miami restaurant association events. Word of mouth from other owners. Does not read newsletters or blogs.
How to Build Personas from Real Conversations
Step 1: Identify 10-15 people who fit your target customer profile. They do not need to be customers yet -- in fact, it is better if some are not, so you hear unbiased feedback.
Step 2: Have 30-minute conversations. Ask open-ended questions: What is the biggest challenge in your day? How are you solving it now? What have you tried that did not work? What would a perfect solution look like?
Step 3: Look for patterns. You will notice 2-3 distinct types of people emerging. Each type becomes a persona. Focus on the patterns, not the outliers.
Step 4: Write the persona using the template above. Use direct quotes from your conversations -- they make the persona feel real.
Step 5: Update quarterly. Your understanding of your customer should deepen over time. If your persona has not changed in 6 months, you are not talking to customers enough.
The most important rule: never build a persona from assumptions alone. Every field should be grounded in something a real person told you. If you are guessing, you are projecting your own biases onto your customer.
Ready to build a product for your target persona? Email us at partners@awasero.com or learn about our venture studio model.