A persona is a user archetype representing a distinct set of behavior patterns and goals, built by triangulating qualitative and quantitative research rather than by guessing. The process starts by identifying the different roles your users occupy, then mapping the behavioral characteristics research participants actually displayed against those roles, looking for clusters that suggest a genuine, distinct pattern rather than one-off individual quirks. Each persona needs both accomplishment goals, what they want to achieve, and an experience goal, how they want to feel while doing it.
Not every persona carries equal weight. A primary persona represents the main target for a given role and drives the initial design focus. A secondary persona is similar with minor differences, accommodated once the primary's needs are met. A supplemental persona has no genuinely unique needs and mainly exists to satisfy stakeholders who want to see their favorite user type represented, it shouldn't actually drive design decisions. And a negative persona explicitly represents a type of user the product is not being designed for, which helps prevent stakeholders from being pulled toward serving someone outside the actual target.
Two personas that differ only in job title but share the same goals, behaviors, and painpoints aren't two personas: they're one persona wearing two different name tags.
1: Erin is the strongest primary persona candidate. Between Erin and Tom, both represent genuinely distinct, well-differentiated behavior patterns, but the scenario describes Erin's efficiency-and-automation-focused pattern as more prevalent among the described solo advisers, and it aligns with what's typically the larger opportunity for a platform aimed at daily client work at scale. Tom remains a legitimate secondary persona: distinct enough in his distrust of automation and desire for manual verification to matter, but representing a narrower slice of the target audience than Erin.
2: Ethan should be a negative persona. He explicitly represents a type of user, an enterprise compliance officer needing a different, enterprise-tier product the team has decided not to build, that falls outside the platform's actual target. Making this explicit as a negative persona helps the team resist stakeholder pressure to add enterprise-compliance features that would serve a user this product was never meant to serve.
Grace's close similarity to Erin in goals and behaviors is exactly the signal that she shouldn't be treated as a separate primary persona, she should be classified as secondary, since her pattern differs from Erin's only in one respect: her added interest in prospecting features. Once that classification is made, the design work should proceed by designing for Erin's needs first, then incorporating whatever prospecting-related additions would serve Grace, as long as those additions don't compromise the experience Erin's design already delivers.This is precisely the discipline the primary/secondary distinction exists to enforce: rather than treating four personas as four equally weighted design targets, the team can focus their core design effort on Erin, extend thoughtfully for Tom and Grace's specific differences, and consciously exclude Ethan's needs entirely.
Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.
Extract significant quotes from user research transcripts and categorize them by theme, sentiment, and relevance for use in personas, journey maps, and stakeholder presentations.