PM User Personas Guide
(2026 Edition)
The 8-part persona structure, a fully worked example, and 6 mistakes that turn personas into wall art nobody uses.
Build User Empathy Daily — Free →8-Part Persona Structure
1. Name and photo
Give them a specific name and photo (even AI-generated). Makes the persona real, not an abstraction.
2. One-line summary
'Priya, 32, delivery partner in Pune trying to smooth out her monthly cash flow.'
3. Core job-to-be-done
What they're hiring the product to do. 'Get paid quickly without paperwork.'
4. Top 3 pain points
Specific, observed pains — not imagined. From user research.
5. Current workarounds
What they do today without your product. Often the real competitor.
6. What they value
Functional (speed, cost) AND emotional (trust, pride, dignity).
7. What they'd reject
Explicit. What solutions/features would push them away?
8. How they discover products like yours
Helps inform acquisition strategy.
Fully Worked Example
Priya, 32, Delivery Partner, Pune
Delivers 20 Swiggy orders/day, earns ₹22-30K/month, supports family of 4.
Job to be done
'I want to smooth out my cash flow so I don't stress about mid-month bills.'
Pain points
- • Income is unpredictable day-to-day
- • Bills are predictable — mismatch creates stress
- • No savings buffer
Current workarounds
- • Borrows from family at month-end
- • Uses credit from local kirana store
- • Delays school fee payment
Values
Dignity (doesn't want to ask family), speed (can't wait days), simplicity (distrusts complex forms)
Would reject
Anything that feels like a loan with paperwork. Anything that charges her fees she can't clearly see.
6 Persona Mistakes
Personas based on demographics only — 'millennial women' isn't a product strategy
Too many personas — most teams can't design for more than 3 in active use
Personas that never change — refresh annually as user base shifts
Personas that don't drive decisions — if two personas get identical product answers, they're one persona
Inventing personas without validation — must come from real user research
Treating personas as marketing artefacts, not product decision tools
FAQ
How many personas should a PM team have?
3 primary personas for most products. Add 1–2 if you truly serve distinct segments (e.g. buyer vs seller in a marketplace). More than 5 and no one remembers the personas — they stop being useful. Start with 3, add deliberately when decisions diverge.
What's the difference between a persona and a segment?
A segment is a measurable group in your user base (e.g. 'users who opened 3+ sessions last week'). A persona is a narrative representation that makes a segment feel human (a name, story, context). Segments are for analysis; personas are for alignment. Great PMs use both: segments for the dashboard, personas for the PRD.
Build User Empathy Daily
Scenarios that force you to design for specific personas, not generic users.
Start Free Trial →