A Reminder: You're Building for Real People, Not Personas
Here is a simple truth that product management methodology can obscure: the people who will use your product are actual human beings with actual contexts, actual emotions, and actual consequences from whether your product works well or poorly. They are not user personas. They are not aggregated behavioral profiles. They are real people making real decisions in real situations.
This distinction matters because the abstraction that makes product development efficient — the persona, the segment, the user type — can gradually replace the genuine human understanding that good product development requires.
What Personas Do Well
Personas provide the cognitive shorthand that makes it possible to design for a large, heterogeneous user base without requiring every design decision to synthesize an infinite number of individual cases. They capture the patterns across many users — the shared goals, the common workflows, the recurring frustrations — in a form that can be referenced without conducting a new research project for every decision.
When personas are grounded in genuine user research, maintained as living documents that evolve as user understanding deepens, and treated as starting hypotheses rather than settled truth, they provide genuine value.
What Personas Can’t Do
They can’t capture context: The persona describes a type of user; the context of any specific design decision involves a specific type of user in a specific situation with specific constraints. The persona doesn’t tell you what it feels like to try to use your product while managing three vendor calls simultaneously and preparing for a Monday deadline. Real user observation does.
They can’t be surprised: When the user’s response to a design doesn’t match the persona’s expected response, the most common first reaction is to update the design rather than to question the persona. Real users are often surprised; personas never are. That asymmetry produces the systematic failure to update user models that makes personas gradually less accurate over time.
They can’t generate genuine empathy: Empathy — the ability to share someone else’s experience — requires exposure to specific, individual human experience, not to a composite profile. The product manager who has conducted many user interviews develops different intuitions than one who has studied personas constructed from those interviews. The lived experience of hearing a user describe frustration in their own words, with their own emotional weight, creates a different quality of understanding.
Keeping Real Users Present
The most practical antidote to persona-over-people drift is maintaining regular direct contact with actual users: user interviews, contextual inquiry, customer call participation, support ticket review. Each of these reinjects real human specificity into product thinking that abstraction tends to smooth over.
Key Takeaways
User personas are useful abstractions, not substitutes for genuine user understanding. They capture patterns but can’t convey context, can’t generate genuine empathy, and can’t surprise the product team in the ways that real users routinely do. Maintaining regular direct contact with actual users — alongside the analytical benefit of personas — is what keeps product development grounded in the human experience it’s supposed to serve.