Persona is a simple tool to create your product with a specific target user in mind rather than a generic one. It’s a representation of the real target audience data, gathered in previous research such as user interview.

1. Goal-directed Personas

This persona cuts straight to the nitty-gritty. “It focusses on: What does my typical user want to do with my product?”. The objective of a goal-directed persona is to examine the process and workflow that your user would prefer to utilize to achieve their goals in interacting with your product or service. There is an implicit assumption that you have already done enough user research to recognize that your product has value to the user and that by examining their goals, you can bring their requirements to life. The goal-directed personas are based upon the perspectives of Alan Cooper, an American software designer and programmer who is widely recognized as the “Father of Visual Basic.”

2. Role-Based Personas

The role-based perspective is also goal-directed, and it also focuses on behavior. The personas of the role-based perspectives are massively data-driven and incorporate data from both qualitative and quantitative sources. The role-based perspective focuses on the user’s role in the organization. In some cases, our designs need to reflect upon the part that our users play in their organizations or wider lives. An examination of the roles that our users typically play in real life can help inform better product design decisions. Where will the product be used? What’s this role’s purpose? What business objectives are required of this role? Who else is impacted by the duties of this role? What functions are served by this role? Jonathan Grudin, John Pruitt, and Tamara Adlin are advocates for the role-based perspective.

3. Engaging Personas

“The engaging perspective is rooted in the ability of stories to produce involvement and insight. Through an understanding of characters and stories, it is possible to create a vivid and realistic description of fictitious people. The purpose of the engaging perspective is to move from designers seeing the user as a stereotype with whom they are unable to identify and whose life they cannot envision, to designers actively involving themselves in the lives of the personas. The other persona perspectives are criticized for causing a risk of stereotypical descriptions by not looking at the whole person, but instead focusing only on behavior.”

4. Fictional Personas

The fictional persona does not emerge from user research (unlike the other personas), but it emerges from the experience of the UX design team. It requires the team to make assumptions based upon past interactions with the user base and products to deliver a picture of what, perhaps, typical users look like. There’s no doubt that these personas can be deeply flawed (and there are endless debates on just how flawed). You may be able to use them as an initial sketch of user needs. They allow for early involvement with your users in the UX design process, but they should not, of course, be trusted as a guide for your development of products or services.

How to create a persona

Engaging personas can incorporate both goal and role-directed personas, as well as the more traditional rounded personas. Engaging personas emphasize how stories can engage and bring the personas to life. This 10-step process covers the entire process from preliminary data collection, through active use, to the continued development of personas.

  1. Collect data. Collect as much knowledge about the users as possible. Perform high-quality user research of actual users in your target user group. In Design Thinking, the research phase is the first phase, also known as the Empathise phase.
  2. Form a hypothesis. Based upon your initial research, you will form a general idea of the various users within the focus area of the project, including the ways users differ from one another – For instance, you can use Affinity Diagrams and Empathy Maps.
  3. Everyone accepts the hypothesis. The goal is to support or reject the first hypothesis about the differences between the users. You can do this by confronting project participants with the hypothesis and comparing it to existing knowledge.
  4. Establish a number. You will decide upon the final number of personas, which it makes sense to create. Most often, you would want to create more than one persona for each product or service, but you should always choose just one persona as your primary focus.
  5. Describe the personas. The purpose of working with personas is to be able to develop solutions, products and services based upon the needs and goals of your users. Be sure to describe personas in such a way as to express enough understanding and empathy to understand the users.
    1. You should include details about the user’s education, lifestyle, interests, values, goals, needs, limitations, desires, attitudes, and patterns of behavior.
    2. Add a few fictional personal details to make the persona a realistic character.
    3. Give each of your personas a name.
    4. Create 1–2 pages of descriptions for each persona.