Personas are visual stories that describe actual customers. Personas draw a detailed picture of the user, what they want to accomplish, what knowledge or skills they may or may not have, and why certain things may be more important to them. The products or services you design try to solve these customer problems. Personas help the team focus on user-centered design.
Personas work best when everyone on the team, including marketing, sales, product design, and customer support, participate in defining the primary target personas and then using the personas to design product or service features.
This article will take you through six steps toward identifying your target user using personas. These steps include:
First, understand the "supply chain" of your product space, that is, what are all the roles involved in delivering the product or service you imagine. Think in terms of end users, resellers, advocates, partners, policy influencers, and internal users. You might have multiple candidates for each of these categories.
For example, say you are targeting the education market. You might consider personas for students, teachers, administrators, parents, tutors, librarians, or school IT personnel. At the next level, you may consider parents who are technically savvy and those who are not, those who have lots of time and those who do not, and students who have different learning styles, different interests, and different motivators. These would all be personas you could create.
During this phase, you want lots of ideas with few restrictions.
Now that you have your prospective list, you'll want to go out and interview people who fit these descriptions. How do you find these people? The easiest way is to think about where they might be.
If you have an existing business, you can interview some of your own customers. If you have a new business or idea, you can look for people who are using current solutions or who have no solution.
For example, say you are creating a website that helps with wedding planning. You could hang out at a bookstore magazine rack and look for people buying bridal magazines. If you want to sell electric bicycles and scooters, you may visit a community green fair and talk to attendees and vendors. You might also consider including some people who do not want your product or service to understand why.
Once you've found people to interview, you'll want to ask them the same questions. First, ask permission for their time and give them an estimate of how long the questions will take.
Next, you'll want to ask them some demographic questions (although you may want to ask these last) such as general age (provide a range), family situation, etc.
Now ask about their connection or history with the problem you are trying to solve. For example, have they bought this type of product or service in the past, how did they decide on a provider, what were their alternative solutions, and what was the final result?
Finally you want to ask about factors that may influence their ability to solve the problem or use your product. Will they need a certain comfort level with technology? Will they need some domain expertise? Are there physical limitations to consider, like fine or gross motor skills?
Once you complete your interviews, you can use Storyboard That to write your personas. Start with a picture of your person, then add the details. You can use the three-panel template above, or you can use the six-panel template that provides more details.
Create one storyboard for each person. You may end up with as many as a couple dozen personas.
The next step is to define the true target user for your solution.
Start by printing out all your persona storyboards and laying them on a flat surface. You'll need some room to move them around. Bring your entire team into the room. Everyone should be familiar with the personas already.
Now, pick six personas (at random) and put them in a triangle, with one at the top, two in the second row, and three in the third row. These rows represent your primary, secondary, and tertiary users. Team members may then, without the need for discussion, simply replace personas in the triangle or move them from one row to the next.
However, there should only ever be six personas in the triangle. Once the movement stops, you can continue to the next step: Discussion.
Sales may emphasize the difference between the buyer and the user. Marketing may compare revenue for resellers versus end users. Product design and development may consider implementation challenges. Product support may discuss cost of ownership.
Remember, prioritization doesn't eliminate the needs of secondary or tertiary target users, it just prioritizes the needs of the primary user. The discussion may take more than one meeting.
Consider these questions success for embracing a user-centered approach.
Personas are different from User Stories. See our article on User Stories and Agile Development to learn more about User Stories.
Use the three- and six-panel Storyboard That templates above to create your own personas. You can also use our Spider Map template below to create a larger company persona map. Everyone on the team can participate in creating personas. When interviewing, you may team up people based on experience or confidence level. Storyboard That simplifies the process, while the templates ensure some consistency. As the team gains experience, you may want to create your own templates for use in future design and development cycles.