We find ourselves over a year after most businesses adopted an all-remote workforce for the first time ever. Now, some organizations look to return to an office and incorporate remote work. For software development teams, it has become more critical to ensure we understand our target audiences—whether they be application users, clients, stakeholders etc. To do this you must employ the right tools to gain understanding and ultimately better customize your product or […]
We find ourselves over a year after most businesses adopted an all-remote workforce for the first time ever. Now, some organizations look to return to an office and incorporate remote work. For software development teams, it has become more critical to ensure we understand our target audiences—whether they be application users, clients, stakeholders etc. To do this you must employ the right tools to gain understanding and ultimately better customize your product or services to meet customer needs. To help with this, we are sharing insights gained from Excella’s Change Management consultants’ recent work on user personas with one of our application development teams at a federal healthcare client.
According to usability.gov, the purpose of a persona is “to create a reliable and realistic representation of your key audience segments for reference.” The persona serves as a descriptive profile of the audience that interacts with your product or services and whom you would like to learn more about. Typically, personas are developed early in the product lifecycle to ensure that your product or services respond to the challenges and needs of the main target groups.
Excella has adapted the usability.gov definitions and processes with current and past clients with great success. At the client site mentioned above, our Change Management consultants were tasked with learning more about our users as the tool was in the early stages of development. We wanted to make sure that the development changes we were making made sense to users and that they felt comfortable enough to be able to use the tool on their own.
Before beginning to put together a persona, you need to define concrete questions of value about your target audiences. To figure out if you are in an ideal environment to start the persona-creation process, we recommend you ask yourself:
The second step in creating user personas is developing a Persona Interview Guide (below). Based on the insights and information you are looking to gather, outline the high–level categories. Our team found these themes to be most insightful to highlight:
Next, you will build out your user persona interview guide with questions for each of these general sections for the user research stage. For our federal client, we identified 4 specific groups that we were interested in learning more about. In order to ensure that the personas were consistent across groups, we used the same guide for each interview.
After the user interviews, the team synthesized the major elements to identify the themes for the groups, which were incorporated into each group’s persona.
“Your personas are only as good as the research behind them.” –Usability.gov
Before conducting interviews with users, be mindful that their time is valuable and that your questions should be clear and concise. The goal is to gather as much information as you can during the interview to inform development and your communication, training, and outreach efforts.
It is important to emphasize to participants that:
Reinforce that the themes that are identified will inform future designs and iterations. Ensure a diverse pool of participants by interviewing users outside of the “power user” group which can potentially provide other use cases.
Here are some additional tips for conducting user interviews:
The value of a persona exists in its content, not necessarily in its presentation. However, we recommend considering using a design software to format and add design elements to your final persona draft. In the example discussed here, our team created different sections based on the themes mentioned above. We added anonymous user quotes sourced through the interviews and pull quotes to add dimension and personalize each persona. One of the most frequent comments we hear from users is that the most useful information they hear about our tool is how other others use it; thus, user quotes are very important. They add value to the persona and allow stakeholders using the persona to share those quotes with users in the future.
After the persona is completed, the process is far from over. In fact, the last stage of the persona development process is the most important one! Sharing the persona with stakeholders and other parties involved in your product is where you will see the ultimate payoff. During communications with stakeholders about the value of a persona, make sure to highlight the main elements of the persona and show how they are relevant to the priorities of the stakeholder.
At Excella’s federal healthcare client mentioned earlier, we learned more about our stakeholders from their reactions to the personas. It was clear to see that they were excited about new insights learned from the personas. Additionally:
The development team gained crucial new insights into user behaviors and preferences through the creation of the personas. The personas have the added benefit of informing tool trainings around user needs shared during the interview process. In addition, we were able to use the communication preferences learned about each group we interviewed more broadly for other projects we had with the organization, so the insights weren’t limited to our understanding of users with regards to one tool. Since we were able to focus in on specific user behaviors, we were also able to develop user training more quickly. Thus, through this process, our Change Management Consultants acquired information essential to organizing future interactions with users.
The great thing about personas is that there is always a chance to iterate on what you have done, because there will always be more to learn about your users. Personas should be revisited after a defined period to keep pace with your users’ evolving requirements. We recommend that you align with stakeholders and establish a regular cadence. Personas are meant to be a living artifact and will become more robust and accurate with multiple iterations.
In our last post on Agile scaling, we described some signs that indicate you should...
When is the last time you enjoyed using software? It’s that feeling you get when...
The online customer experience has redefined the way businesses and their customers interact. While these...