A user persona is a fictional yet representative profile of a target user — their goals, frustrations, comfort with technology, and a quote that captures their attitude. Personas keep real human needs front-of-mind during design and product decisions. This free tool assembles plausible personas at random to seed workshops, fill out presentation slides, and kick-start design-thinking exercises.
How it works
The generator draws from curated banks for each attribute and combines them into a coherent profile:
- It picks a name and a random age between 19 and 68, plus an occupation.
- It selects a primary goal and a primary frustration that commonly appear in product research.
- It assigns a tech comfort level (low, medium, or high) and a representative first-person quote.
The pieces are assembled in your browser with no network call, and Reroll produces a fresh combination.
What each field represents and why it matters
Name and age establish the basic human frame. Age in particular shapes technology expectations — someone who adopted smartphones as an adult has different mental models than someone who grew up with them. The generator picks ages across a realistic working adult range (19–68) rather than defaulting to a 25-year-old, which helps teams avoid unconsciously designing for themselves.
Occupation sets context for goals and pain points. A nurse’s frustration with software is different from a freelance designer’s even if both are described as “wanting to save time.” The occupation is deliberately general — it is a starting point for you to sharpen.
Primary goal is the task or outcome the persona wants your product to enable. This is not a feature request (“I want a better search”) but a genuine outcome (“I need to find the right supplier before my deadline”). The distinction matters for product decisions.
Primary frustration is what currently blocks that goal. Frustrations are where design energy is best spent — they are the gap between what users need and what they currently have.
Tech comfort level (low, medium, high) is a summary signal. Low-comfort users need simpler flows, more obvious affordances, and fewer options. High-comfort users tolerate complexity and often prefer power features and shortcuts. When designing, ask: does this interaction work for the lowest-comfort persona in the set?
Representative quote is the most powerful field in a presentation. A first-person sentence that names a tension — “I just want it to work without reading a manual” — makes the persona human to an audience in a way that bullet points do not. Keep the personas whose quote most sharply frames a tension your product must resolve.
How to use generated personas well
- Generate three to five at a time and deliberately seek a spread: at least one low-tech-comfort persona, one high-tech-comfort, a range of ages, and different occupations. Designing for one persona usually means designing for yourself.
- Use them as a discussion scaffold, not a finished artefact. In a workshop, give each participant a persona and ask them to argue for design decisions from that persona’s perspective.
- Replace fields with real findings as your research develops. A generated persona is a placeholder; a research-validated persona has quotes from actual interviews, goals from actual user sessions, and frustrations from actual support logs.
- Do not over-individualise. A persona is a pattern across many users, not a biography. If the generated name and age are distracting the team from the goal-and-frustration pattern, rename the persona or use initials.
- Pair a persona with a customer journey map to trace how that specific goal-and-frustration plays out across the product’s touchpoints.