Personas are researched groupings of behavioural user traits. They are developed to narrow the scope when designing or developing a product. We all know you can’t design for everyone but how can you create an effective, scalable product that translates for a wide range of users?
A persona represents a cluster of users who exhibit similar behavioral patterns in their purchasing decisions, use of technology or products, customer service preferences, lifestyle choices, and the like. Behaviors, attitudes, and motivations are common to a type regardless of age, gender, education, and other typical demographics. – Kevin O'Connor
Personas are a great reference for the whole team when developing a feature on an existing product or when diving into a totally new venture. By creating archetypes of different user segments you can design with purpose to help achieve specific end goals.
A user persona can act as a touchpoint for your team, making sure your project is on track to solve problems with the real users in mind. It allows your team to practice empathy when creating features for one persona knowing that it will satisfy the needs a much larger group of users.
The purpose of personas is to create reliable and realistic representations of your key audience segments for reference.– usability.gov
Using personas will allow your team to prioritise the work based on achieving the end goals of your users on a more manageable scale. It can also help to uncover opportunities for product features during the interview process. Designing for personas helps to keep the team focused and can aide in user testing throughout the project lifespan.
In his article A Closer Look At Personas: A Guide To Developing The Right Ones (part 2) Shlomo Goltz outlines the process of creating user personas. Here is a summarized version to get you started in your research.
In an existing company this is where you can look at your traditional market research as a starting point. If you are starting fresh check out your competition – who is using their product?
Write out your interview questions beforehand. Open-ended questions are better, but actually observing your user complete a task is best. This will give you insight into not only what the user is saying they need but what is actually going on when that need arises.
Side-by-side testing is of the utmost importance. You can gain valuable insight by sitting next to your users while they are testing your product. This also opens the door to practicing empathic design. Once you’ve watched your users struggle with a task you aren’t likely to put the same barriers in their way again.
Go through your research and determine which users have similar attributes or behaviours. What commonalities did you see that kept coming forward? What common goals or use cases were there? Once you’ve analyzed each subject you can take a step back and look at any patterns that emerge. Each different pattern represents a separate persona.
Your personas should include a name or descriptive title, demographic, and dominant traits. It can include their typical day, but most importantly it addresses their end goals. Knowing their goals helps to ascertain what is most relevant when considering your design.
Create a concise document for your team to review and have on hand. It will help gain focus across the different disciplines.
Creating user personas should be done at the onset of a new product or feature. It will help guide the decision making as well as act as an evaluation tool. A new set of personas should be created for each new product you develop.
Persona development belongs at the beginning of the project, as personas can inform site functionality, help uncover gaps, or highlight new opportunities. – usability.gov
By developing personas you are insuring that you’re addressing the needs of a wide range of users but in a manageable, focused manner. Working with user personas creates better communication within your organization as your user’s goals become that of the team.