Personas: Build for a Specific 'Who', Not a Vague 'Everyone'

THE MENTAL MODEL: Personas are fictional characters created to represent a specific user type for your product. Instead of designing for a generic "user," you design for a concrete individual with a name, goals, and pain points. This creates empathy and a shared focus for the entire team, from engineers to marketers.

HOW IT WORKS: Personas are built from user research, not imagination. You collect data through interviews, surveys, and analytics to identify common patterns in behavior, goals, and motivations among your users. These patterns are then synthesized into a few distinct character profiles. Each persona typically includes a name, a photo, a short bio, key goals, and frustrations related to your product's domain. For example, a project management tool might have a "Project Manager Pete" persona and a "Developer Dana" persona.

WHEN TO USE IT: Use personas to guide product strategy and design decisions. They help prioritize features ("Would Pete find this useful for his daily stand-up?"), resolve design debates ("This layout helps Dana focus, which is her main goal"), and ensure consistent user experience across the product. They are especially valuable in Agile teams to keep user needs at the forefront of every sprint.

WHEN NOT TO USE IT: Avoid personas when they are not based on real data. "Proto-personas" created from assumptions can be a starting point, but they are dangerous if not validated. Also, avoid creating too many personas (the "persona zoo"). A handful of primary personas (3-5) is usually most effective. If you're building a highly technical tool for a single, well-defined role, a detailed job description might be more useful than a full persona.

ONE CANONICAL EXAMPLE: A team building a fitness app discovers two main user groups: one focused on weight loss and another on performance training. They create "Weight-Loss Wendy," a 35-year-old office worker who wants to lose 15 pounds and struggles with motivation. They also create "Performance Paul," a 28-year-old amateur cyclist who wants to track his power output and race times. When deciding whether to build a calorie tracker or a power meter integration, the team can ask which feature best serves Wendy's or Paul's primary goals.