A persona taped to the wall that nobody references during a roadmap debate isn't a research artifact — it's office decoration.
1Behavior Over Demographics
It's tempting to define a persona by age, income, and job title because that data is easy to gather. But two 35-year-old product managers can have completely different goals, tools, and frustrations. What makes a persona actionable is behavioral: what task are they trying to accomplish, what's currently stopping them, and what would make them switch tools. Demographics are supporting color, not the core of the persona.
2The Proto-Persona Trap
Most teams start with a proto-persona — a quick sketch built from internal assumptions, useful for aligning a kickoff conversation. The trap is letting it calcify into 'the persona' without ever validating it against real users. Before a persona drives a roadmap decision, it should be checked against actual interviews, support tickets, or usage data — otherwise the team is optimizing for a character that was never based on anyone real.
3Step-by-Step Breakdown
Introduction. A user persona is a composite archetype representing a distinct group of real users, built from research, not a marketing mood board. Its job is to keep every roadmap conversation grounded in 'what does Maria actually need' instead of 'what do we assume users want.'
Anatomy of a Persona. A useful persona centers on goals and motivations, behaviors and habits, and frustrations — demographics like age or job title are context, not the point. A one-line representative quote pulled from an actual interview does more to align a team than a full page of invented backstory.
Research-Backed vs. the Proto-Persona Trap. A proto-persona — built purely from internal assumptions before any research — is a fine starting hypothesis, but it becomes dangerous the moment it's treated as fact. Every persona should be validated against real interviews, support data, or usage patterns before it drives roadmap decisions.
Knowledge Check. Two personas are both '28-year-old marketing managers,' but one describes a completely different set of goals and frustrations. Why is that fine?
- →Personas are defined by behavior and goals, not demographics — two people with the same job can have very different needs
- →One of the two personas must be wrong since they share the same age and job title
Summary. Personas earn their place on the wall only when they're built from real behavioral research and actually get referenced in prioritization debates. A persona nobody mentions after the kickoff meeting was never really used — it was decoration.
