mentioned user interviews, basically, we ask questions, and users answer questions. If a little refinement, the interview can be divided into two stages, namely the interview stage and the experience stage. The main purpose of interview is to acquire valuable problems from the user experience and knowledge, and experience stage is to allow users to experience the part of the design we give, stimulate their evaluation, observe their experience, looking for problems from.

let’s assume that an ideal user interview, if shown in a diagram, should be like this:



hosts the controls, leaving plenty of conversation space to the user, and the user closely follows the theme, each of which directly reflects the need.

, but the reality is cruel, the user will not be so much in tune with us, many times due to our own problems, the effect of interviews will be greatly reduced. Experienced people may be able to control the entire interview with their powerful control skills, but for most inexperienced interviewers, there are some of the following problems.

one, warm up awkward

in most interviews, warming up is the task of setting out user background information. We usually faithfully perform the responsibility of taking background information to the user. In fact, warming up is intended to allow users to open the box, allowing users to enter the state. This is the beginning of the interview, the interview to determine the tone and atmosphere, many users will be mistaken for investigation or interview, thought it was a satisfaction survey, and even thought it was the headquarters sent correspondent to solve user confusion…… This is a conversation with the relationship, but there are several points: be sure to cover their identity, their position in the team, the purpose of the interview, we want the user to play the role, and some of the background. Let the user to start a conversation in a certain range of topics, which can provide ideas to let the user to open the topic, also can avoid later digress.


two, too lengthy questions,

in the ideal state, of course, our problem can not be long. But when users don’t understand our problems, we have to start a long explanation.


problems are easy for users to get distracted, and even make their own God, users will give up listening after trying to understand, after the interview in the organization of language to help the user to explain the problem, usually there is no way to get back to the problem quickly.


so we have to pay attention to the problem in setting up the problem

Written by 

Leave a Reply

Your email address will not be published. Required fields are marked *