Conducting user interviews requires a lot of planning, it should be conducted after careful preparation. There are the most important steps of this preliminary phase:
- Getting to know the problem space (e.g. by a Stakeholder Interview and domain expert interviews),
- Preparing problem statements (what are the problems we need to solve, what are our hypothesis we need to validate?)
- Creating an interview script with the questions. It needs to be noted that it does not mean that we will read out loud these questions during the interview, and our job is done! The interview script is just a mindmap, which will us remember what areas we need to discover.
- Finding participants (and creating a screener, which basically a document which helps us identify future interviewees who meet all the important criteria - e.g. you don’t want to test your mobile app with someone who does not have a smartphone, and not planning to purchase one in the near future - obviously it is just a basic example, we will list out more specific criteria for your product or service).
- Fieldwork scheduling
We have experience with in-person interviews as well as remote Skype interviews (the latter mentioned has certain limitations, but still a very useful resource). We record the interviews, then we create a transcript.
After conducting the sufficient number of interviews, we utilize UX design methods to organize and analyze the collected data (like Affinity Diagramming, Empathy Mapping, Personas, Journey Mapping, Storyboarding).
As a result, we will not only know a lot about your users' needs and context, user interviews also help to identify assumptions: it is important to keep in mind that we are not designing for ourselves!