HomeFrameworksDesign & UX › Persona Development
// framework

Persona Development

Alan Cooper, 1999

Research-based fictional profiles of your key buyer segments that prevent designing for a fantasy average user — ensuring every product and listing decision serves a real person's real context.

// description

Personas are fictional but research-based character profiles representing key segments of a product's target audience. Each persona has a name, demographic details, goals, frustrations, behaviours, and a brief narrative describing their context. Personas serve as a shared reference point for making design decisions by asking "What would this persona need?" rather than debating abstract user needs.

// history

Alan Cooper, a software designer, introduced the concept in his 1999 book The Inmates Are Running the Asylum. Cooper developed personas as a way to prevent the common practice of designing for an "elastic user" whose needs shift to justify whatever feature the team wants to build. The method was further developed by Kim Goodwin and Robert Reimann at Cooper's consulting firm.

// example

A KDP publisher creates three personas based on her best customer data and reviews: "Sarah, 38, NICU nurse who uses her planner to decompress after 12-hour shifts — she needs the layout to feel calm and uncluttered, and wants to track her sleep and hydration as non-negotiables"; "Marcus, 29, freelance developer who needs income and project tracking integrated into his weekly view"; "Linda, 52, recently retired teacher who journals daily and wants beautiful design more than function." When designing a new product, she checks all three. A highly decorative design with minimal structure serves Linda but not Sarah. The persona check prevents products built for a fantasy average user that actually serves no one.

// katharyne's take

Build personas from real data, not imagination. The best source is your actual customers — look at your review language, your DMs, your customer emails. What phrases do they use? What jobs do they have? What do they say the product helps them with? A persona built from 30 real reviews will serve you far better than one built from demographic statistics. And keep them visible while you're designing: I literally print mine out and stick them next to my monitor when I'm creating a new KDP interior. If both "Sarah" and "Marcus" would love it, I'm on the right track.

// creative uses
// quick actions
// prompt ideas
I sell [type of product] on [KDP/Etsy/Gumroad]. Help me build two distinct buyer personas based on these patterns I've noticed in my reviews and customer messages: [paste 5–10 review excerpts or DM snippets]. Give each persona a name, a job or life situation, their core frustration before buying, what they said the product helped with, and the tone of language they use so I can write listings that speak directly to them.
I'm designing a new [planner/journal/digital download] for [niche]. Here are my two existing buyer personas: [describe them briefly]. Walk me through every key design decision — layout density, colour palette, feature set, page size — and flag any choice where the two personas would want different things. I want to either design for one primary persona or find the overlap that serves both.
Rewrite this Etsy listing description using my primary buyer persona as the filter. My persona is [describe her: job, situation, core need, emotional state when searching]. The current description reads: [paste description]. Make every sentence speak to her specific situation, use the kind of language she'd use herself, and lead with the outcome she cares most about.
See also: Empathy Mapping · Jobs to Be Done · Customer Journey Mapping
← KJ Method Empathy Mapping →