For product managers, the most fearful thing when designing a product is to work behind closed doors. The product manager does not understand the real needs of users and cannot find the pain points of users? When it comes to how to understand users, the first thing we think of is questionnaires.
What do we need to know about how to prepare a questionnaire? What issues should I pay attention to?
1. Before doing the questionnaire, we need to make a list first.
Before doing a questionnaire, you should first have an operation process plan. That is, before doing any research, you must first draw up a detailed list of the results you want to obtain, as well as a Make an analysis plan on how to use the data, dismantle it based on the results you want to obtain from the research, design a specific outline of the research process, and then design questions based on the outline.
Just like we want to make a product for users’ free time when commuting to and from get off work, then we first need to be clear, what do we want to know? If we are targeting a mobile APP where commuting time is the dominant time, what we need to know is: What means of transportation does the user use to get to and from get off work? How much time do users spend commuting to and from get off work every day?
As for data analysis, it is a process of reversely investigating the problem from the results. For example: if we consider whether the product should add offline caching function, then we need to consider the user's network speed during commuting time? What should we do if the user traffic is not enough?
2. Ensure that users can answer questions smoothly.
It is to allow users to be accurate and not get entangled in the accuracy of the answers to your questions. For example: What is the speed of the mobile phone network mentioned above when the user is commuting to work? If you ask the user like this, the user will definitely not know how to answer you. But if you ask the user: How fast do you watch videos, information, and pictures on your mobile phone during commuting and get off work hours? You can get an accurate answer.
3. During the survey, try to ask as few hypothetical questions as possible.
Do not provide users with hypothetical questions, because the user himself does not know what he would do if he encountered such a scenario. Many times people will give the time that did not happen. Beautification, such as: If I make a paid product, will you be willing to pay?
4. Don’t trick your users.
Don’t trick your users, and don’t provide users with a scenario to guide them to answer the answer you want. For example: A lot of free time is wasted during commuting every day. Are you willing to use this time to study?
5. Jump out of your questionnaire.
? As mentioned before, sometimes even if it is not a hypothetical question, users will beautify their answers when answering. I often The same is true. Many times, the ideal answer from the mind and the actions taken by the body are not consistent. Therefore, it is often necessary to jump out of the questionnaire you set to observe the user's behavior. Observing the user's behavior will be more accurate than simply asking the user what they think.
6. Summary.
? Previously in Geek Time, Erye mentioned his own principle for questionnaires: if the overall behavioral data can be used to make inferences, usability testing will not be done. If you can do usability testing, you don’t need questionnaires.