User Persona Generator

Alan Cooper Invented Personas in 1983. We're Still Getting Them Wrong.

Alan Cooper was consulting for a software company and kept arguing with stakeholders about what "the user" wanted. Everyone had a different user in their head. So Cooper made one up — a fictional woman named Kathy who was a busy office manager. Suddenly, the arguments stopped. "Would Kathy do this?" became the tiebreaker for every design decision.

That was 40 years ago. And yet most personas I see in 2026 are glorified demographic profiles that tell you nothing useful about what to build.

The Persona Problem: Demographics Without Decisions

"Sarah, 34, lives in Brooklyn, works in marketing, drinks oat milk." That's not a persona. That's a dating profile. A persona should change how you make product decisions. If you can swap one persona for another and your roadmap doesn't change, the personas aren't doing their job.

The research backs this up. According to a Nielsen Norman Group study, teams using behavior-based personas (goals, frustrations, decision patterns) made 22% fewer usability errors in design than teams using demographic-based personas. The difference isn't trivial — it's the difference between building for who someone *is* versus what someone *does*.

Here's what good looks like, from a real example. Spotify doesn't just say "casual listener, age 25-34." They build personas around listening contexts: the commuter who wants hands-free discovery, the dinner party host who needs a reliable playlist, the runner who needs BPM-matched tracks. Each persona implies different features, different UI patterns, different success metrics.

How This Prompt Helps

This prompt generates personas from the data you actually have — interview notes, analytics patterns, support tickets — rather than asking you to guess demographics. It pushes you toward behavioral dimensions: What triggers this person to use your product? What's their "job to be done"? What would make them switch to a competitor? These are the questions that drive product decisions.

The output includes decision-making criteria for each persona, so you can immediately use them in prioritization conversations. "Would this feature matter to Persona A or Persona B?" becomes a concrete question with a concrete answer.

When to Reach for This

• You've completed a round of customer interviews and need to synthesize findings into actionable archetypes
• Your team keeps saying "the user" in meetings and meaning different people each time
• You're entering a new market segment and need to build empathy before building features
• Design reviews are stalling because nobody agrees on who they're designing for
• You want to validate whether your current personas still reflect your actual user base

What Good Looks Like

A strong persona has a name, a quote that captures their core frustration, specific behavioral patterns (not just demographics), 3-5 goals tied to your product, and clear "won't tolerate" boundaries. You should be able to hand the persona to a new engineer or designer and have them make better decisions without further context.

Sources

• Personas: Practice and Theory — Nielsen Norman Group
• The Inmates Are Running the Asylum — Alan Cooper
• How Spotify Builds Products — Harvard Business Review