Back to all posts

How to create and use personas as part of a UX process

Personas provide meaningful archetypes which you can use to assess your design development against. Constructing personas will help you ask the right questions and answer those questions in line with the users you are designing for. For example, “How would Peter, Joe, and Jessica experience, react, and behave in relation to feature X or change Y within the given context?” and “What do Peter, Joe, and Jessica think, feel, do and say?” and “What are their underlying needs we are trying to fulfill?”

Personas in Design Thinking

In the Design Thinking process, designers will often start creating personas during the second phase, the Define phase. In the Define phase, Design Thinkers synthesise their research and findings from the very first phase, the Empathise phase. Using personas is just one method, among others, that can help designers move on to the third phase, the Ideation phase. The personas will be used as a guide for ideation sessions such as Brainstorm, Worst Possible Idea and SCAMPER.

Four Different Perspectives on Personas

In her Interaction Design Foundation encyclopedia article, Personas, Ph.D and specialist in personas, Lene Nielsen, describes four perspectives that your personas can take to ensure that they add the most value to your design project and the fiction-based perspective. Let’s take a look at each of them:

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 utilise in order to achieve their objectives in interacting with your product or service. There is an implicit assumption that you have already done enough user research to recognise 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”.

Author/Copyright holder: Smashing Magazine. Copyright terms and licence: All rights reserved. Img Source

2. Role-Based Personas

The role-based perspective is also goal-directed and it also focusses on behaviour. The personas of the role-based perspectives are massively data-driven and incorporate data from both qualitative and quantitative sources. The role-based perspective focusses on the user’s role in the organisation. In some cases, our designs need to reflect upon the part that our users play in their organisations 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.”
– Lene Nielsen

Engaging personas can incorporate both goal and role-directed personas, as well as the more traditional rounded personas. These engaging personas are designed so that the designers who use them can become more engaged with them. The idea is to create a 3D rendering of a user through the use of personas. The more people engage with the persona and see them as ’real’, the more likely they will be to consider them during the process design and want to serve them with the best product. These personas examine the emotions of the user, their psychology, backgrounds and make them relevant to the task in hand. The perspective emphasises how stories can engage and bring the personas to life. One of the advocates for this perspective is Lene Nielsen.

One of the main difficulties of the persona method is getting participants to use it (Browne, 2011). In a short while, we’ll let you in on Lene Nielsen’s model, which sets out to cover this problem though a 10‑step process of creating an engaging persona.

Author/Copyright holder: Terri Phillips. Copyright terms and licence: All rights reserved. Img Source

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.

10 steps to Creating Your Engaging Personas and Scenarios

As described above, engaging personas can incorporate both goal and role-directed personas, as well as the more traditional rounded personas. Engaging personas emphasise 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 continued development of personas. There are four main parts:

  • Data collection and analysis of data (steps 1, 2),
  • Persona descriptions (steps 4, 5),
  • Scenarios for problem analysis and idea development (steps 6, 9),
  • Acceptance from the organisation and involvement of the design team (steps 3, 7, 8, 10).

The 10 steps are an ideal process but sometimes it is not possible to include all the steps in the project. Here we outline the 10-step process as described by Lene Nielsen in her Interaction Design Foundation encyclopedia article, 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 a such way so as to express enough understanding and empathy to understand the users.

  • You should include details about the user’s education, lifestyle, interests, values, goals, needs, limitations, desires, attitudes, and patterns of behaviour.
  • Add a few fictional personal details to make the persona a realistic character.
  • Give each of your personas a name.
  • Create 1–2-pages of descriptions for each persona.

6. Prepare situations or scenarios for your personas. This engaging persona method is directed at creating scenarios that describe solutions. For this purpose, you should describe a number of specific situations that could trigger use of the product or service you are designing. In other words, situations are the basis of a scenario. You can give each of your personas life by creating scenarios that feature them in the role of a user. Scenarios usually start by placing the persona in a specific context with a problem they want to or have to solve.

7. Obtain acceptance from the organisation. It is a common thread throughout all 10 steps that the goal of the method is to involve the project participants. As such, as many team members as possible should participate in the development of the personas, and it is important to obtain the acceptance and recognition of the participants of the various steps. In order to achieve this, you can choose between two strategies: You can ask the participants for their opinion, or you can let them participate actively in the process.

8. Disseminate knowledge. In order for the participants to use the method, the persona descriptions should be disseminated to all. It is important to decide early on how you want to disseminate this knowledge to those who have not participated directly in the process, to future new employees, and to possible external partners. The dissemination of knowledge also includes how the project participants will be given access to the underlying data.

9. Everyone prepares scenarios. Personas have no value in themselves, until the persona becomes part of a scenario – the story about how the persona uses a future product – it does not have real value.

10. Make ongoing adjustments. The last step is the future life of the persona descriptions. You should revise the descriptions on a regular basis. New information and new aspects may affect the descriptions. Sometimes you would need to rewrite the existing persona descriptions, add new personas, or eliminate outdated personas.

Author/Copyright holder: Lene Nielsen. Copyright terms and licence: All Rights Reserved. Reproduced with permission. See section "Exceptions" in the copyright terms.

Lene Nielsen’s poster covers the 10step process to creating engaging personas which participants are the most likely to find relevant and useful in their design process and as a base for their ideation processes.

You can download and print the “Engaging Persona” template which you and your team can use as a guide.

Example of How to Make a Persona Description – Step 5

Author/Copyright holder: phot0geek. Copyright terms and licence: CC BY-SA 2.0

We will let you in on the details about our persona’s education, lifestyle, interests, values, goals, needs, limitations, desires, attitudes, and patterns of behaviour. We’ve added a few fictional personal details to make our persona a realistic character and given her a name.

Hard Facts

Christie is living in a small apartment in Toronto, Canada. She’s 23 years old, single, studies ethnography, and works as a waiter during her free time.

Interests and Values

Christie loves to travel and experience other cultures. She recently spent her summer holiday working as a volunteer in Rwanda.

She loves to read books at home at night as opposed to going out to bars. She does like to hang out with a small group of friends at home or at quiet coffee shops. She doesn’t care too much about looks and fashion. What matters to her is values and motivations.

In an average day, she tends to drink many cups of tea, and she usually cooks her own healthy dishes. She prefers organic food, however, she’s not always able to afford it.

Computer, Internet and TV Use

Christie owns a MacBook Air, an iPad and an iPhone. She uses the internet for her studies to conduct the majority of her preliminary research and studies user reviews to help her decide upon which books to read and buy. Christie also streams all of her music and she watches movies online since she does not want to own a TV. She thinks TV’s are outdated and she does not want to waste her time watching TV shows, entertainment, documentaries, or news which she has not chosen and finds 100 % interesting herself.

A Typical Day

  • Christie gets up at 7 am. She eats breakfast at home and leaves for university at 8.15 every morning.
  • Depending on her schedule, she studies by herself or attends a class. She has 15 hours of classes at Masters level every week, and she studies for 20 hours on her own.
  • She eats her lunch with a study friend or a small group.
  • She continues to study.
  • She leaves for home at 3pm. Sometimes she continue to study 2-3 hours at home.
  • Three nights a week she works as a waitress at a small eco-restaurant from 6pm to 10pm.

Future Goals

Christie dreams of a future where she can combine work and travel. She wants to work in a third world country helping others who have not had the same luck of being born into a wealthy society. She’s not sure about having kids and a husband. At least it’s not on her radar just yet.

Know Your History

The method of developing personas stems from IT system development during the late 1990s where researchers had begun reflecting on how you could best communicate an understanding of the users. Various concepts emerged, such as user archetypes, user models, lifestyle snapshots, and model users. In 1999, Alan Cooper published his successful book, The Inmates are Running the Asylum, where he, as the first person ever, described personas as a method we can use to describe fictitious users. There are a vast number of articles and books about personas, however a unified understanding of one single way to apply the method doesn’t exist, nor does a definition of what a persona description should contain exactly.

The Take Away

Personas are fictional characters. You create personas based on your research to help you understand your users’ needs, experiences, behaviours and goals. Creating personas will help you identify with and understand the user you’re designing for. Personas make the design task at hand less complex, they will guide your ideation processes, and they will help you to achieve the goal of creating a good user experience for your target user group. Engaging personas emphasise how stories can engage and bring the personas to life. The 10-step process covers the entire process from the preliminary data collection, through active use, to continued development of personas.

References & Where to Learn More

Nielsen, Lene, Personas. In: Soegaard, Mads and Dam, Rikke Friis (eds.). The Encyclopedia of Human-Computer Interaction, 2nd Ed. Aarhus, Denmark: The Interaction Design Foundation, 2013:

Alan Cooper, The Inmates Are Running the Asylum, 1999

Silvana Churruca, Introduction to User Persona, June 27, 2013:

Silvana Churruca, DIY User Personas, June 28, 2013:

Personas can be used in conjunction with empathy mapping to provide a snapshot of a Persona’s experience as described in a Persona Empathy Mapping article by Nikki Knox on the Design & Strategy Agency’s Journal.

Atlanta based Photographer Jason Travis has created a series of Persona Portraits with their artifacts which illustrates the power of visually representing archetypal users, customers or personalities.

Hero Image: Author/Copyright holder: Teo Yu Siang and Interaction Design Foundation. Copyright terms and licence: CC BY-NC-SA 3.0

This article was originally posted at:

Can we take you from stuck to unstuck?

We'd love to hear from you

Product Design

The ‘Product’ is the website, service, application, interactive thing being worked on by the business. The practice of Product Design is similar in a lot of ways to UX Design. It involves the coming together of many specific design disciplines...

Call to action (CTA)

A call to action is a marketing term that refers to a prompt that invokes a response leading to a sale. When referring to a call to action (CTA) in the digital design world we usually mean the interactive element that leads to the next step in the experience - something that needs to be clicked or tapped.

User testing

User testing refers to a technique used in the design process to evaluate a product, feature or prototype with real users. There are several reasons why you might want to undergo usability testing, the most common is that it allows the design team to identify friction in a user experience they are designing, so that it can be addressed before being built or deployed.


WYSIWYG (pronounced WIZ-ee-wig) is an acronym for "What You See Is What You Get". It helps identify an an interface that allows user input resulting in an output that is rendered in a similar way. For example; a word processor application interface might resemble a piece of paper,so when printed the user can see how the output will appear.

Content Management System

A content management system (CMS) is an tool that allows a website editor/administrator to manage the content that is displayed. Websites are made of HTML and CSS to create pages. Pages can be hard-coded but would require technical development skills to make changes. A CMS usually allows a person without coding knowledge to amend existing and add new content to a website using a WYSIWYG interface.

Responsive Web Design

Responsive web design refers to a web page that dynamically adapts its layout to fit the size and orientation of the device on which it is viewed. A responsive design allows for a more optimised user experience across desktop and laptop computers as well as smartphones and tablets of varying sizes.

User Stories

User stories allow the functionality of a product or service to be expressed as written descriptions of an experience as seen from the users perspective. The writing of user stories creates a list of design and development tasks to complete in order to create any required functionality.

User Interface

A user interface (UI) is a conduit between human and computer interaction - the space where a user will interact with a computer or machine to complete tasks. The purpose of a UI is to enable a user to effectively control a computer or machine they are interacting with, and for feedback to be received in order to communicate effective completion of tasks.


A persona in UX Design is the characterisation of a user who represents a segment of your target audience. On a project you might create any number of personas to be representative of a range of user needs and desires. The solutions you design must answer these needs in order to deliver value to your target audience.

Card sorting

A great, reliable, inexpensive method for discovering patterns in how users would expect to find content or functionality. Card sorting is used to test the taxonomy of data with a group of subjects, usually to help inform the creation of the information architecture, user flow, or menu structure on a project.


A technique used to generate ideas around a specific topic. Often done in groups, but can be done individuals. The process usually involves writing down all ideas around a topic onto paper, a whiteboard or stickies often implying some kind of association.

Minimum Viable Product

An MVP is a product that has the minimum set of features to prove the most essential hypothesis for a product. Businesses building a new product can create a Minimum Viable Product to prove that an idea is viable and warrants further investment. A further benefit being that the next stage of development can be informed by feedback obtained from testing that MVP.


A sitemap is a diagrammatic representation of a hierarchical system. It usually depicts the parent-sibling relationship between pages in a website, showing how sub pages might be arranged underneath their parent groupings. This arrangement forms a map of the site.

User journey

A user journey represents a sequence of events or experiences a user might encounter while using a product or service. A user journey can be mapped or designed to show the steps and choices presented as interactions, and the resulting actions.


A prototype is draft representation built to test ideas for layout, behaviour and flow in a system. Prototypes are an indispensable tool for resolving a large number of potential issues in a concept or business before too many resources are deployed to put a design into production.


A Wireframe is a visual schematic that conveys a basic level of communication, structure and behaviour during the design of a system. Wireframes are low-fidelity designs that bypass including a detailed user interface or visual design, conveying just enough to get across the core idea.


To say something is usable is a qualitative statement about how easy that thing is to use. Usability is an assessment of how learnable a system is and how easy a user finds it to use. The usability of a system or product is a key factor in determining whether the user experience is a good one.

Information Architecture

Information architecture is the design and organisation of content, pages and data into a structure that aids users understanding of a system. A more organised system enables users to more easily find the information they require and complete the intended tasks.

UI Design

User Interface Design is the discipline of designing software interfaces for devices, ideally with a focus on maximising efficiency, responsiveness and aesthetics to foster a good user experience.

UX Design

The practice of User Experience (UX) Design is the coming together of many specific design related disciplines to improve the usability, responsiveness, uptake and aesthetics of a product or service.

User Experience

A general term that covers all aspects of a user's participation while engaging with something that has been designed. Usually when talking about User Experience in the digital design field it refers to the interactions, reactions, emotions and perceptions while using an app, service, website or product.