Planet RoadmapUser personas are one of the most common artifacts in product management, and also one of the most commonly ignored. The problem is not the concept—it is the execution. Too many personas are fictional composites based on assumptions rather than research. A useful persona is grounded in data, focused on behavior, and referenced regularly in product decisions.
What Makes a Persona Useful
A useful persona answers a specific question: "Who are we building for, and what do they need?" It should describe behaviors, goals, and pain points—not just demographics. Knowing that your user is a 34-year-old marketing manager tells you very little. Knowing that they juggle three tools to track campaign performance and wish they could see everything in one view tells you a lot.
Limit yourself to three or four personas. If you have twelve, none of them will be remembered. Each persona should represent a distinct behavioral pattern that requires different product considerations.
Gathering Data for Personas
Start with quantitative data from your product analytics. Identify clusters of users who behave differently—power users versus occasional visitors, self-serve versus sales-assisted, single-player versus team accounts. These behavioral segments form the skeleton of your personas.
- Analyze usage patterns to find natural behavioral clusters.
- Conduct 5-8 interviews per cluster to understand motivations.
- Review support tickets and feature requests for recurring themes.
- Cross-reference with sales and customer success notes.
Writing the Persona Document
Keep it to one page. Include a name, a one-sentence description, three to five key behaviors, their primary goal, their biggest frustration, and how they evaluate success. Skip the stock photo and the fictional backstory—they add charm but not clarity.
Add a "product implications" section that explicitly states what this persona means for your roadmap. For example: "This persona needs a simplified onboarding flow because they evaluate tools in under ten minutes." This bridges the gap between research and action.
Keeping Personas Alive
Personas go stale fast. Review them every quarter against fresh data. When you collect feedback through channels like Planet Roadmap, tag submissions by persona so you can see which persona is asking for what. This turns personas from a static document into a living filter for prioritization.
Reference personas in roadmap reviews, design critiques, and sprint planning. If the team never mentions personas in daily work, they are decoration, not tools.