I firmly believe that your research outcome depends a lot on how much preparation you have done. I have seen many research projects fail to give real outcomes only because they were poorly planned and documented. Documenting research findings in a report is as important as conducting the research itself. Anyone can gather data but there are very few good researchers who have the ability to analyze these findings to give real valuable insights to bring change.
Sometimes I can be a real pain in the neck for my researchers when I ask them to work on their documents but I am glad they now understand the importance of it.
Even unstructured research needs structured moderator guide
We all know that structured user research surely needs a lot of planning, preparation, and documentation but it is a misconception that purposeful unstructured research doesn't need any of these things.
I give utmost importance to creating a good Moderator Guide so that any moderator with some experience can conduct research sessions.
No matter which user research method you are using for conducting research, you need a good Moderator guide.
Following are some examples of the Moderator Guide I have designed.
Following images show some screenshots from the Moderator guides I have prepared. I will present the documents to you upon request.
Market research for Instant Mobile Website Creator - Interview questions (2008)
Contextual inquiry for Travel Operators - Office Tour and Closing (2019)
Usability Testing Moderator Guide of Visitor Management System (2019)
It is extremely important to track all the recommendations in one sheet at least for a quarter. Once the research is completed researchers take up the next project and recommendations from the previous research are forgotten. To avoid this we created a sheet to track all the research recommendations, and this helped not only stakeholders but also researchers to understand how useful their research was.
All research recommendations in one place for a particular quarter
Personas help drop your ego and work for the betterment of others.
I think most companies and their leadership don't really understand the hidden power of personas and know how to use them. I have seen many persona documents never referred to after they are created.
The best thing to do is print your personas and paste them on the walls. This definitely generates a lot of discussion and everyone knows who is the target user.
Generally speaking, hypothesis personas are created first based on the current understanding of the product.
After that, user research is conducted to gather data about user goals, aspirations, pain points motivations, etc. I think these user research sessions should be used as an opportunity to understand the 'why' behind all that is mentioned above and try to understand deeper and unconscious aspects of user behavior. Techniques such as 5 why, and active listening need to be used by a skilled researcher. Also, I think conducting interviews or focus groups is one thing and analysis is another. a LOT depends on how good qualitative data analytical skills you have.
Once user research is completed, hypothesis personas are validated and updated based on the data gathered. I have found User Interviews and Focus group sessions to be very useful for validating hypotheses and then making updates to the personas.
Following are some of the personas I have created from various products I have worked on. Note that these personas are created after a good research.
Persona for Personal Loan Provider Company (2019)
NGuru - Parent Persona (2018)
NGuru - Student Persona (2018)
NGuru - Teacher Persona (2018)
NGuru Personas (2018)
Personas have helped our teams to be focused on the users we are designing products for. One of the best things to do is take big printouts and paste them on the walls of the office where everyone can easily see them.
In one of my companies, I have seen this generating many conversations over tea time and slowly building empathy in the team for our users.
Sometimes I think it is unfortunate that most people ignore personas once they go through the initial research findings and start working on the product. I have seen products taking different directions and slowly losing focus on the target users' goals, motivations and needs.
It helps team members remain focused on users' needs if we keep all our conversations during the brainstorming around the personas created.
If you don't start your product with a UX strategy, you are probably never going to launch it
Typical components of UX strategy. These may very as per the project requirements - Airport kiosk UX Strategy (2019)
A strategy would include User research and Design activities list - Airport kiosk UX Strategy (2019)
Hypothesis personas are refined after user research - Airport kiosk UX Strategy (2019)
Analysis and reporting of findings defines success of your research
A typical Usability Testing report slide will have findings for each task, analysis, user comments or short video, and recommendation - Large British Telecommunications company (2007)
A reserach session may include an 1-on-1 interview and a quick validation of existing design - ISI EMIS (2007)
A typical Usability Testing report will clarify Objectives in the beginning (2006)
An Executive Summary will highlight the key findings (2006)
Maps are simply put, visualization of user experience
User journey map is a visualization of an individual’s relationships with a product/brand over time and across different channels. - Zupee - Ludo Supreme Game - Journey Map (2020)
A service blueprint is a diagram that visualizes the relationships between different service components — people, props (physical or digital evidence), and processes - Emxcel Airport Kiosk - Service Blueprint - Hypothesis (2020)