A growing business is always concerned with the needs of its users. And creating a user persona, however fictional, provides business teams the information they need to make real decisions considering the needs, experiences, and goals of their users.
Connecting with users requires uncovering information about their attitudes, behaviors, characteristics, and desires using qualitative and quantitative information. To put it simply, to get a 360-degree view of your users, you’ll need to pull together quantitative information to understand scope and scale—as well as intent and preferences—and qualitative stories that breathe life and make the persona feel real.
But before we dive into the practicalities, let’s first make sure we’re on the same page.
In 1999, Alan Cooper popularized the concept of personas in his book; The Inmates are Running the Asylum.
Personas are, as he puts it, “... a precise description of our user and what he wishes to accomplish.” Rather than going out and talking to actual users about every little detail, and taking their feedback literally, “...we discover them as a byproduct of the investigation process.” Instead of building for “averages,” we conduct research to understand user archetypes and build a precise and accurate representation of someone who represents the unique combination of needs, expectations, and behaviors that we are targeting.
Since Cooper formalized personas, researchers, developers, designers, and marketers alike have made use of his model to make sure their users have a seat at the table during the design and development process.
Personas have also proven especially crucial as we’ve integrated more inclusive design principles and processes into our work. Personas help extend our view of users to encompass people who represent the full range of human perspectives so we can create services, products, environments, etc. that address those needs. Surfacing these needs pushes us to create products that are more usable for everyone.
Over time, several different approaches to defining and implementing personas have evolved. Remember, personas are more than just people. They’re fictitious models of a target user’s real behaviors, motivations, attitudes, goals, and more, related to your business’ product or experience.
The goal-driven persona is most likely the concept that people are most familiar with. (It’s also based upon the perspectives of Alan Cooper, mentioned earlier.) It gets right to the point and focuses on what the user wants to do with your product or experience. In other words, your business has a product that people use, so the objective of this persona is to examine how a user would go about achieving their objectives while interacting with your product.
The role-based persona is also behavior-focused, but slightly different. This persona seeks to examine the role(s) that users typically play in real life, their organization, community, and the like. Examining the roles people play in their everyday lives can help inform product and design decisions.
The engaging persona is different from the others because the idea is to create a 3D rendering of a user through the use of personas. It might sound unusual, but the more people engage with the persona and actually perceive them as real, the more likely they are to consider them during the design process. This persona examines the emotions of the user and uses their psychology to inform decisions for the task at hand.
User personas are grounded in research—both qualitative and quantitative. Typically, analytics and surveys support a better understanding of how many and who. This data can be used to build personas of segments that represent many users and provide demographics that help to inform the scope and magnitude of trends and patterns you see in data.
However, interviews address why and how. The narrative and storytelling facilitated through 1:1 conversation help drive the creation of a precise and accurate portrait of users as well as scenarios that expose contexts of use.
To begin, you’ll want to employ open, neutrally-framed questions. Questions that you pose during an interview should be open, enabling participants to answer honestly and without fear of judgment. Avoid asking people “in general” questions that have them characterize what they typically do. People are much more capable of answering specific questions about recent experiences and then characterizing that experience as being normal or not.
In addition, recall questions help to set the stage, get people comfortable, and build rapport. And rapport is important for both moderated and unmoderated settings because you want the interviewee to feel they can be honest and upfront. Here are some examples of how to ask people to talk about recent—within the last 1-3 months—experiences:
Some other lines of questioning you might want to consider include:
Now that we’ve laid the groundwork for conducting user interviews to build user personas, it’s important to discuss the different methods for conducting them—moderated and unmoderated. Both approaches are useful to hear customers’ stories, but they differ in some key features. Here are some considerations that might drive your decision-making when electing to use one approach—or both—on the UserTesting platform:
|Minimal moderator bias||X|
|Highly structured "show and tell"||X|
|Flexible handling of PII/access through firewalls||X|
Interviews are essentially guided conversations, and when thinking about how to structure that conversation, there are a few things to keep in mind for unmoderated interviews:
Consider using some creative options to keep your participants engaged, like mixing in tasks where you ask people to show you how they navigate a site, look for information, or their environment. Alternatively, ask them rating scale or multiple choice questions to get a sense of how they feel about a concept. By setting up a more engaging and interactive set of prompts, you will get richer feedback that is more efficient to review.
Moderated interviews can be free-form. Because you can ask people whatever you wish, it is possible to move between show and tell, nuanced discussion, and even have an element of concept testing. While planning for 30- or 60-minute sessions, ensure that you estimate how long you expect each question and response to take. The best way to test this is to pilot test with a colleague. A few other pointers:
Remember that interviews are a time to make a connection with people who represent the users that you want to understand better. The personas—or deliverables—that reflect what you learned from those conversations are meant to be a tangible means of aligning expectations and understanding around what your users truly need. So, the research that you do to support them should also include the stakeholders who will be using them. This is the best way to allay their fears that the deliverable is “made up” and connect them to persona value. Seeing where the data comes from will build trust.
About the author:
Lija is a Customer Experience Consultant at UserTesting. When she's not helping UserTesting customers understand the wide variety of topic areas they can cover using the platform, she teaches a usability research methods class to undergraduates at the University of Michigan - Ann Arbor.