Skip main navigation

User personas and user archetypes

A more detailed discussion of user personas and an introduction to user archetypes.

In step 1.4, we introduced you to user personas. In this step, we will explore personas in more detail, and also introduce you to another type of user profile, called a user archetype.

The myth of the ‘average user’

It is tempting to think that we can design services using a ‘one size fits all’ approach.

The idea here is that it should be possible to meet everyone’s needs by building a service designed to meet the needs of a generic ‘average user’ that represents everyone.

This would certainly keep things simple!

The problem is that this ‘average user’ does not exist. In fact, designing for the ‘middle’ can often exclude many people.

A team designing for the ‘average user’ of a UK government service will certainly have considered that there will be a broad and varied range of people who need to use it, including:

  • people with disabilities
  • people who speak English as an additional language
  • people with varying levels of digital literacy (or levels of understanding and ability to use technology)

They will have designed and implemented different features in the service to ensure all of those users can access the service.

However, trying to create a single user persona to cover all of these characteristics would be very difficult. We must also be cautious here – the list above includes a lot of people, but does it include everyone?

As broad as this range of users is, it does not account for all users and their needs. Users frequently encounter temporary or situational barriers when accessing online services. These barriers and the problems they cause can only be understood through interaction with users, not by designing for an imagined ‘average user’ characterised through the broad categories listed above.

This is why user research is so important, as it discovers the problems users have when trying to use services. As a user researcher, your job is to include a diverse range of users in your user research; test with people who may face more barriers, and avoid designing solely for the majority.

User personas and user archetypes show how different users think, feel, and act. They help your team understand needs, struggles, barriers, and behaviours.

Let’s explore them in more detail.

User personas

As we explained in step 1.4, a user persona is a profile based on characteristics of a user group. The user persona is not a real person who exists, but rather a fictional person that represents real people.

This can be helpful to teams as it helps us to think of our users as real people with real problems that can be solved with the products and services we are building. Referring to named individuals – like John or Jane, who we introduced earlier – keeps real people in mind, in a way that talking about “user type 1” or “user type 2” might not.

Different teams will use personas in different ways. There is no single “correct” way to write them or use them, but personas should generally always include:

  • a name
  • age
  • relevant demographic information such as gender, marital status, or disabilities
  • needs and goals
  • habits and lifestyle, meaning information about the context in which they need to complete their tasks

All of this information comes from the user research that we conduct with users. Nothing should ever be made up or assumed. These details help your team connect with the user and design with empathy. By seeing the service through the eyes of the user, it becomes easier to spot what works and what does not.

Let’s meet some example personas. Please note that these have been made up for the purposes of this course and are not related to any real users or user research.

Ravi is a 35 year old who has lived in the UK for 2 years. He is not totally confident speaking English, especially for complex tasks, and is unfamiliar with how UK government services are structured. He is confident using digital tools, but often relies on translation apps or help from others to understand official information. He prefers services that use plain English, visual cues, and offer multilingual support where possible.

Angela is an 18 year old school leaver who is about to attend university. She only uses a smartphone to complete tasks, and does not like to talk on the phone or wish to interact with people in person. Angela needs to know information about student financing.

Elle is a 52 year old who balances full-time work with caring for an elderly family member with complex health needs. Elle often completes tasks on behalf of someone else and needs services that allow her to act as a proxy. She values clarity around permissions and responsibilities.

These personas can be used to test design ideas and hypotheses by identifying what their needs are and proposing solutions that might meet them. The whole team should review these personas alongside research findings to decide which needs they can meet now, and which may need to be addressed later, depending on technical feasibility and capacity.

This is how personas can support teams in designing services that work well for the people who need them.

User archetypes

User archetypes are very similar to personas, because they are both ways of communicating insights gained from user research, but there is one key difference between them.

While a persona has a name and a ‘back story’, an archetype is identified with a ‘label’ that represents a behaviour or attitude that is shared by a group of users.

Archetypes help us to spot patterns in user behaviour, and can give a broad view that helps shape strategy for a range of users. This can be very useful early in a project when you are still trying to understand the big picture.

Due to the fact that they do not have names or characters attached, some people perceive archetypes as being more broad, and therefore representing more people.

Above, we introduced 3 example user personas. Let’s now express them as archetypes:

The guided seeker needs services that offer clear, structured guidance and support – such as plain English, visual signposting or multilingual help – to build confidence and reduce reliance on others.

The independent digital native prefers to complete tasks online without human interaction. Expects services to be mobile-first, intuitive, and respectful of their desire for autonomy.

The proxy navigator uses services on behalf of others and needs clear pathways for doing so, including guidance on consent and access rights.

These examples show that archetypes and personas are functionally the same thing and communicate the same information – just with different names. You may now be thinking that this is a bit pointless or just unnecessarily confusing things!

However, although they are very similar, there is a very important reason for using both of them – communication.

Which one should you use?

Personas and archetypes communicate the information about users that we discover through conducting user research. They both represent people with needs, so why do we need both?

One of the main reasons for using both is that sometimes people have preferences in how they receive information and data. As a user researcher, you need to be able to communicate effectively to stakeholders, which means adapting your approach when necessary.

Some people simply do not like using personas. These could be very important people, such as senior stakeholders within the organisation who control funding. They may think that personas are too specific, as the ‘back story’ means that the personas do not usefully represent a large group of users. They might prefer archetypes because they think that these more closely reflect the ‘data’ of users, rather than what they see as the ‘fictional’ or ‘invented’ aspects of personas.

Even within the team, some of your colleagues may have found the process of developing personas to be too time-consuming, or they did not find personas helpful in previous projects.

When this happens, it might be easier to talk about user archetypes. This means that you can communicate the same vital information about your users without any ‘unnecessary’ details.

On the other hand, personas have a human connection that creates empathy. For some people, they need a way to understand the value that building a product or service will have for users. Personas help with this – even if “young single mother balancing work and childcare” is more human than “User Group 1”, thinking about ‘Zara’ makes it seem more real, because we can imagine how our service will help Zara as if she were a real person.

As we will learn in the next step, personas can also be very effective when used in user stories, to test ideas and assumptions about design decisions.

Task

Think about a time when you needed to explain something about users to someone else, maybe a colleague, a stakeholder, or a wider team.

Would a persona or archetype have worked better in that situation? Why?

Share your thoughts with your fellow learners and consider how different approaches help teams understand and act on user needs.

This article is from the free online

User Research in Government: Developing Further

Created by
FutureLearn - Learning For Life