User persona

What is a user persona?

A persona compresses what you have learned from many real people into one specific character you can argue with. Instead of debating what "users" want, the team asks what Priya, the solo bookkeeper with forty clients and no time to learn new software, would do with the feature in front of her. The character is invented. The behavior behind it should not be.

The technique came out of interaction design in the late 1990s, popularized by Alan Cooper as a way to stop teams from designing for an imaginary average user who does not exist. Averaging a group of very different people produces a profile that matches nobody, which is how products end up with features everyone tolerates and nobody loves.

A persona earns its keep when it changes decisions. If yours has been on the wall for six months and has never settled an argument about scope, pricing, or copy, it is decoration.

What actually belongs in a persona

Skip the stock photo and the fictional hobbies. The parts that change decisions are the job the person is trying to get done, the trigger that makes them go looking for a tool, the workaround they use today (spreadsheet, intern, competitor, nothing), what they are measured on at work, the words they use to describe the problem, and who else has to approve the purchase. Their age and favorite coffee order do not affect a single design or pricing choice.

Keep it to one page and to two or three personas at most. Small teams that maintain seven personas are usually describing a market they have not chosen yet.

Why user personas matter for startups

The real value for a one to five person team is saying no. Every week brings feature requests, channel ideas, and positioning suggestions. A written persona gives you a fast test: does this serve the person we chose? Requests that fail the test get parked without a two-hour debate, and the parked pile itself becomes a useful signal if the same non-target keeps showing up.

Personas also make copy concrete. Landing page headlines written for "businesses" tend to be vague; headlines written for a specific person with a specific trigger tend to convert better because they name the problem in the reader's own vocabulary. That vocabulary should come out of interview transcripts, not brainstorming.

User personas in practice

Say you run a two-person tool for freelance video editors. You interview twelve customers and notice they split cleanly. Six are solo editors who care about delivering client revisions fast and have no budget approval process. Six work inside small agencies where a producer picks the tool, cares about shared storage and permissions, and will not adopt anything without team accounts.

You write two one-page personas from the transcripts, then check your roadmap against them. The next three planned features all serve the agency producer, while roughly two thirds of your revenue comes from solo editors. You reorder the roadmap, rewrite the landing page headline around delivering revisions in a day, and move team permissions to a higher priced plan. Nothing was invented here; the personas just made an existing imbalance visible.

Common mistakes

• Inventing personas in a meeting room. A persona built from assumptions launders guesses into apparent facts. Base each one on at least five to ten real conversations.
• Padding with demographics. Age, income, and hobbies rarely change what you build. Lead with the job to be done, the trigger, and the current workaround.
• Maintaining too many. More than three personas usually means the team is avoiding a positioning decision. Choose a primary one and rank the rest.
• Confusing buyer and user. In B2B the person who signs off is often not the person clicking. Write both, and know which one your marketing speaks to.
• Freezing them. Personas drift as your customer base changes. Revisit after any pivot, price change, or new channel that brings a different crowd.

Related concepts

Personas are the qualitative counterpart to customer segmentation, which groups your existing base by behavior and value, and to market segmentation, which slices the wider market before you have customers. Build them from real evidence gathered during customer validation, then put them to work in customer journey mapping and in the everyday user experience decisions that follow.