Before you even launch your application, you often check the feasibility of your product. It means talking to your target customers and taking information about what they need. When you do that interview, you need to ask all the right questions and make the meeting worth your user’s time.
Here are 10 important reminders you should consider when checking with user views
Do not ask hypothetical questions
A priority in any business venture would always be the return of investment but never check with your customers by directly asking, because they would usually say yes. This answer is often not accurate and ultimately not helpful. Ask in a different method instead of creating a hypothetical situation, taking in factual information from user feedback.
“Would you buy our app?”
“What do you need from our app?
Do not stack your questions
When doing an interview, we have multiple questions readied for our customers. But that is not the top priority in making a good app. It’s more important to hear the feedback of the customers who will be using it. For this reason, you ask one question at a time, then follow through with that. It would naturally set the pace of questions according to priorities.
“What would work for your needs? What are the major markets? What would benefit your clients?”
“What would work for your needs? Can you explain?”
Do not use closed questions
Closed questions remove any opportunity for gaining more information. The customer would be limited to yes or no answers. They will not help you see what the user is thinking, what kind of struggles they are facing, and what they are enjoying with the app. It would be best if you had answers with a lot of information the users have thoroughly thought through.
“Do you want this feature?”
“What features do you need?”
Do not ask a general question
When asking about the right question, go for the recent-experience instead of a general answer. Prefer using items like ‘when was the last time’ over ‘how often.’ It gives you a definite idea, and you can check if users have consistency in their answers.
“How often do you use this app?”
“When was the last time you used this app?”
Do not ask questions that are too detailed
Sometimes we need a lot of results. The questions pile up, and you need the customer to answer all of it. Before it gets overwhelming and too technical with the user, try asking about their experience. Let them describe the situation according to their perspective. Users can have their freedom to express and give emphasis to the part they find essential.
“What did you like in the app? Why did you like that? Can you specify?”
“Tell us about your experience with the app”
Do not use leading questions
Leading questions remove the effectivity of your inquiries. Often the users would answer to the favor your app, if not to directly offend you. If you give them an idea of an answer, most would agree instantly, because they would not need to think too hard in finding their solutions. It will not be helping your product get any better.
“Do you use the app frequently?”
“How often do you check your app?”
Be conscious of your presentation
Often any developer would be proud of their product and naturally claim ownership. But when delivering services, you want your customers to have that ownership. Always use neutral words to describe the app. Being conscious of the difference can help make your users comfortable with their answers and deliver unbiased responses.
“How useful is our app?”
“How useful is this app?”
Try to look through the user’s eyes
Often as the creator, you would know best how to operate the app, but it is not the same for the user. When you ask your user, be prepared to question what they do, not what you think they do. The difference is in the impression. It is essential to note the user’s first impression. How they operate your app would eventually be how a bigger crowd might view your app too.
“What do you do in the dashboard?”
“Can you demonstrate how you use the dashboard?”
Ask for explanations
One important thing that happens when you direct the question is creating the technical language barrier with your customer. Instead, the app should speak for itself to the audience without any prompting. Always prefer the user’s explanation in their discoveries because it becomes the honest feedback of a first-time user.
“Do you see the logo of the app? What do you think about it?”
“Explain what you see the app’s front page?”
Do not settle for abstract notions as answers. Words like “frequently,” “always,” “all,” and “never” should be avoided as answers. What you’re aiming for should be quantifiable results, as the number of hours or days. Communicate and discover why your user would come to that answer. Help the audience find their solution.
“What do you find ‘good’ in the app?”
Use this as a guide for the best questionnaire that draws out all your app’s information. Remove the misleading questions and help bring out the best of your user’s answers.