Perfecting your personas

A persona is a user archetype you can use to help guide decisions about product features, navigation, interactions, and even visual design. By designing for the archetype—whose goals and behavior patterns are well understood—you can satisfy the broader group of people represented by that archetype. In most cases, personas are synthesized from a series of ethnographic interviews with real people, then captured in 1-2 page descriptions that include behavior patterns, goals, skills, attitudes, and environment, with a few fictional personal details to bring the persona to life. For each product, or sometimes for each set of tools within a product, there is a small set of personas, one of whom is the primary focus for the design.

It’s easy to assemble a set of user characteristics and call it a persona, but it’s not so easy to create personas that are truly effective design and communication tools. If you have begun to create your own personas, here are some tips to help you perfect them

Personas represent behavior patterns, not job descriptions

A good persona description is not a list of tasks or duties; it’s a narrative that describes the flow of someone’s day, as well as their skills, attitudes, environment, and goals. A persona answers critical questions that a job description or task list doesn’t, such as: Which pieces of information are required at what points in the day? Do users focus on one thing at a time, carrying it through to completion, or are there a lot of interruptions? Why are they using this product in the first place?

There is seldom a one-to-one correlation between personas and job descriptions. In some cases there will be multiple personas with the same job description; in others, a single persona can represent people with a wide range of jobs. If you were creating software used by call center agents, for example, you might have an experienced agent persona who is very familiar with the product, as well as an inexperienced agent who needs more prompts and written information. If, on the other hand, you were designing an e-mail application, one persona could represent people with hundreds of very different job descriptions, as long as they all shared similar goals and behavior patterns related to communication.

Keep your persona set small

If you’ve ever read a book or watched a movie with an enormous cast of characters, you may have found it hard to remember who was related to whom, who said what, and so on. You probably didn’t feel like you knew any of the characters very well. If you were designing a product for such a large cast of characters, could you predict how so-and-so’s cousin (whose name you forget) would behave in a certain situation? Probably not. That’s why a large set of personas is problematic—the personas all blur together.

Ideally, you should have only the minimum number of personas required to illustrate key goals and behavior patterns. There’s no magic number, but if you’re designing a consumer product and you have a dozen personas, then you may be making distinctions that aren’t very important. For example, if you were creating an electronic family calendar, your persona set might include a career mom, a stay-at-home mom, a career dad, and a teenager. If the career mom has the same needs as the career dad, and also does all the family management the stay-at-home mom does, you may be able to eliminate both the dad and stay-at-home mom personas.

Your marketing and sales targets may not be your design targets

Many product managers and executives are surprised when there isn’t a direct correlation between market segments and personas. The people who bring in the most revenue may not be the best design target. If you were designing an in-flight entertainment system, a frequent business traveler—every airline’s most valued customer—would be a tempting design target. A business traveler would actually make a poor design target, though, because he would be too familiar with flying and with using computers and other gadgets. If you design for the business traveler, the retired bricklayer going to see his grandchildren won’t be able to use the system. If you design for the bricklayer, the business traveler will also be happy.

Add life to the personas, but remember they’re design tools first

Sometimes it’s easy to focus too much on a persona’s biography. Personal details can be the fun part, but if there are too many of them they just get in the way. To avoid this problem, focus first on the workflow and behavior patterns, goals, environment, and attitudes of the persona—the information that’s critical for design—without adding any personality.

Once you have the critical design information, add just one or two personal details, such as what your persona does after work (she goes home to watch old movies with Claude, her cat), or what personal touches there are in her workspace. You can also add life to the persona by using environmental details to reinforce important characteristics. For example, if someone tends to be incredibly busy at work, don’t just say he’s incredibly busy; instead, say there’s a sandwich on his desk that he’s been trying to find time to eat for three hours. Without a little bit of personality, personas can easily turn into generic users instead of precise design targets.

Use the right goals

Each persona should have three or four important goals that help focus the design. Keep in mind that goals and tasks are different: tasks are not ends in themselves, but are merely things we do to accomplish goals. Not just any goals will do, though, so it’s important to understand which types will help you make design decisions.

Life goals are only occasionally useful in design. For example, "Retire by age 45" would be of little use if you were designing a word processor, mobile phone, or PDA, but it may offer valuable insight when you’re designing a financial planning tool.

Experience goals describe how the persona wants to feel when using a product; having fun and not feeling stupid are experience goals. Not every persona needs an experience goal; in most persona sets, there is one persona who represents people with a lot of anxiety about technology. One of this person’s goals is to avoid feeling stupid. Other experience goals might center on the product domain. A persona using an online banking site, for example, might want to feel confident that his transactions are secure.

Most persona goals should be end goals that focus on what the persona could get out of using a well-designed product or service. End goals may involve the work product that results from using the tool. For example, a graphic designer using a layout tool might want to create an award-winning ad. End goals can also involve indirect benefits from using a product. If a manager wants to be more proactive, a better spreadsheet tool can help her achieve this goal if it makes her more efficient.

Personas must be specific to the design problem

Organizations with more than one product often want to use the same personas over and over ("We have a salesperson persona already—why can’t we use her for the spreadsheet as well as the contact management software?"). Unfortunately, this doesn’t work because effective personas must be context-specific—they should be focused on the behaviors and goals related to the specific domain of a product. A persona’s behaviors and goals related to contact management have very little to do with those related to manipulating financial data. You could keep the same name and personal details, but you’d have to throw away the rest of the persona and start over. It’s better to start with a new set of personas for each product.

Want to know more?

Hopefully, these tips will help you refine your personas so you can get the most out of them. Look for more on personas, principles, and other aspects of interaction design in future issues of the Cooper Journal, and keep up the good work!

Related Reading

16 Comments

Steffen Konrath
Kim, I found the article well written. It covers all relevant aspects and raises appetite to read more. - Steffen Konrath
Curious
Hi, Could you also share the differce between User Profile and Persona
Titash
Yes, It would be great if you could share the difference between User Profile and Persona.
Gloria Bastian
Easy to read and I do totally agree with the reommendations made of keeping simple and light on the personal information. I am currently in the process of developing personas and having a difficult time adding personal characteristics to our personas. I am able to tell you what these individuals do and want their pain points are however who they are I am not sure I truly know. Thank you for answering some of the questions I had.
Juvenal
I am conducting a research on Personas and the text is quite enlightening.
Luis Alveart
Amazing guidelines. This article is helpful for all those UX Designers and Information Architects that want to improve their skills with this kind of tool. Luis Alveart Information Architect
Matthew Winick
Some great insights here, I especially find it interesting and true that often the best marketing and sales targets aren't always the best design targets.
[SDC] 가상인물은 위대하다! « vinyl c
[...] 부서간의 일치된 사용자에 대한 관점을 유지&집중하도록 도와줌:제품이나 서비스가 탄생하기까지는 많은 부서 간의 협업이 반드시 필요하다. 물론! 한 배를 탄 사람들은 목적지에 대한 일치된 관점과 생각을 가지고 있어야 한다. 페르소나는 사용자에 대한 일치된 관점을 가지게 도와주며 프로젝트가 진행되고 규모가 커짐에 따라 자칫 흐려질 수 있거나 방향을 잃을 수 있는 사용자에 대한 관점을 유지할 수 있도록 도와준다. 페르소나를 크게 프린트 하여 모두가 볼 수 있는 곳에 붙여놓는 것도 좋은 방법이라고 한다.“A persona is a user archetype you can use to help guide decisions about product features, navigation, interactions, and even visual design.”- 출처 : Kim Goodwin, Cooper.com [...]
Personas and the five W's: Content that Meets Reader Needs, Pt. 1
[...] Goodwin, K. 2001. Perfecting your personas. [...]
Vinay Dabholkar
I am building material for delivering a training on developing personas. I found this article useful. Especially about differentiating between job roles and behavior patters, keeping the number small and finally using the right foals. Thanks.
가상인물은 위대하다! | VinylC Blog
[...] 부서간의 일치된 사용자에 대한 관점을 유지&집중하도록 도와줌:제품이나 서비스가 탄생하기까지는 많은 부서 간의 협업이 반드시 필요하다. 물론! 한 배를 탄 사람들은 목적지에 대한 일치된 관점과 생각을 가지고 있어야 한다. 페르소나는 사용자에 대한 일치된 관점을 가지게 도와주며 프로젝트가 진행되고 규모가 커짐에 따라 자칫 흐려질 수 있거나 방향을 잃을 수 있는 사용자에 대한 관점을 유지할 수 있도록 도와준다. 페르소나를 크게 프린트 하여 모두가 볼 수 있는 곳에 붙여놓는 것도 좋은 방법이라고 한다.”A persona is a user archetype you can use to help guide decisions about product features, navigation, interactions, and even visual design.”- 출처 : Kim Goodwin, Cooper.com [...]
Are Personas Still Relevant to UX Strategy? | donw00 + experience
[...] can satisfy the broader group of people represented by that archetype.”—from “Perfecting Your Personas,” by Kim [...]
Readings – Pruitt & Kolko | Designer Flaw
[...]      Initially this report was difficult to understand simply because I’ve never heard of a ‘persona’ before. A design team creating imaginary users? Why not use real users you’re designing for? To further understand this process I researched information regarding the Alan Cooper persona technique. (Check out the Cooper blog here.) [...]
Para comenzar | DCU para principiantes
[...] Personas (Goodwin;2001) [...]
How-to Guide for Creating Intranet User Personas | ThoughtFarmer Blog
[...] Perfecting your personas — explains the difference between experience goals and end goals [...]
Saker jag lärde mig på kurs i effektkartläggning | Helt Sonika
[...] här var i sig inget nytt. Tanken med att sätta namn på en samling beteenden är samma i Coopers Personas. Men jag tror man kan tjäna på att använda begreppet användarbeteenden snarare än målgrupper. [...]

Post a comment

We’re trying to advance the conversation, and we trust that you will, too. We’d rather not moderate, but we will remove any comments that are blatantly inflammatory or inappropriate. Let it fly, but keep it clean. Thanks.

Post this comment