Nellie LeMonier shares firsthand experience with persona research and why its time and cost are well worth everyone's effort. By making sure that everyone is on board with persona research and is aware of its importance, you will help ensure that your project's UX is truly something special.
Noel : I've been focusing a lot on the UX lately, mainly because it feels like so many companies have bumped the UX of their website or mobile app higher up their ladder of importance. I think users are expecting more out of software these days, and I'm wondering if persona research could be the key to really nailing that perfect UX. Why would companies think they didn't have time for this research—or worse, that they "already know enough about their users," as you state? This seems like a horrible error to make!
Nellie : During the process of hiring a new UX manager for my group I asked the candidates how they did their research to back up their persona hypothesis, and I was shocked to learn that at least three out of four said they did no research for various reasons. This prompted me to ask your same questions and inspired me to conduct a survey of UX practitioners. The results are posted here: wp.me/p1zgeU-T, and under question 8 I added all the reasons people cited. If you have the time, please read through these. I think it boils down to fear and lack of experience or understanding of research methods and the knowledge that can be uncovered. The main thing I want people to take away from my talk is that research is important and you should not develop a product without it.
Noel : Your abstract for your session "A UX Strategy for Persona Research" mentions that persona research can often be done in as little as two weeks. That sounds very fast! What are some of the ways that this can be accomplished this quickly?
Nellie : When your development team is nimble, quick, and ready to start coding, they don't have time to wait for your research results, so we can't afford to be slow in UX, either. The way to achieve quick results is to be very focused on what you want to find out. Once you have a solid hypothesis for a product persona, you find two or three people that match the profile and interview each one for an hour or so about their daily tasks, their skills, background, and what's important to them. These interviews validate that the persona you envision actually does the tasks you think they do and you're not completely off. Plus, you'll learn a lot more about the users than you may expect. During my presentation I speak about a case study where one of my colleagues reworked the product personas in a two-week period and gave the team a significant amount of details that they did not have about the type of users for which they were developing.
Noel : You presented this session at the 2013 Agile Development/Better Software Conference West. Does persona research have a special place in agile development? Are there any specific strategies that should be used when incorporating persona research with agile?
Nellie : There are a number of strategies and each should be adjusted to the needs of the project and team. Quantitative methods such as user surveys can be good to identify key path use cases or priorities of features to users. For more detailed information, I've been successful at doing one-hour sessions with existing or prospective users where I provide an overview of the product, demo current functionality, and conduct a Q&A session to validate that the need we're trying to address is perceived as a success.