ďWhat do you want?Ē
ďWeíve developed this thing! Would you use it?Ē On the face of it, this seems like a simple question for users to answer. Run some customer interviews! Hold a focus group! Send out a survey!
But this approach is fraught with difficulty:
- Starting with a solution encourages users to discuss the solution rather than the underlying need you are trying to solve. So you may get what seems like helpful answers — "Yes, but it needs to work on my iPhone", or "No, I hate the colour scheme" — when in practice these answers are superficial. A solution-based customer interview does not address what users actually need.
- Techniques like focus groups and surveys highlight opinions. As a consequence, these techniques tend to uncover what’s easy for users to put into words. But what’s easy for users to put into words is not necessarily whatís important to them. The consequence of this is that the underlying need remains unarticulated. Itís not that peopleís opinions are of no value; itís just risky to make design decisions based on them.
- A problem with surveys in particular is that you need to know the questions you want to ask before you can start. Now itís true that a survey will give you a larger sample size ó but sadly, having†a large number of respondents in a survey will never help you if you donít know the right questions to ask in the first place.
- When you ask people what they want, you are asking people to predict their future behaviour. People arenít very good at predicting future behaviour. In fact, we are so bad at it that you are better at predicting other peopleís behaviour than your own. Asking people what they want will encourage confabulation, not tell you what is actually going on.
Thatís where field visits and user observation comes in. The best way of predicting future behaviour is not to†ask people, but to observe them. You need to observe how they go about solving their problem at the moment and then make a decent guess about the underlying need.
Testing the user need
But once youíve made a guess at the underlying need, how do you know if youíre right?
Iíve tried various techniques over the years, and this is my current approach. Itís kind of a mash-up of a cognitive interview and a jobs-to-be-done interview. If you do have a user need, youíll find that the interview results in a rich narrative describing the userís problem in depth.
Here are the steps.
|Step||Question to ask|
|1. Express the user need.||"As I understand it, you need/want/would like to…"|
|2. Get behind the user need.||"Why is that important to you?"|
|3. Test to see if the need is an important one. If itís not, thereís no point trying to solve it.||"Is this an issue that keeps you awake at night, or that you think about regularly?"|
|4. The next few questions attempt to put people back ďin the momentĒ since this will enhance their memory of the need.||"When did you first realise you needed something to solve that problem?"
"Where were you?"
"What were you doing, or trying to do when this happened?"
|5. Now letís see if people have tried to solve the problem themselves.||"Did you try to solve the problem yourself (a DIY solution)?"
"What kind of solutions did you try? Or not try? Why or why not?"
"Did any of them work?"
|6. Now letís see if people have attempted to buy a solution to the problem.||"Have you tried to buy something to solve this problem?"|
|7a If people answer "No" to Q6, it could be because they think there isnít a solution, or it may not really be a user need. So if your participant says, "No" to Q6, ask these questions to clarify their response. (Note: The last question about payment isnít a marketing question: it's another check to confirm this is a real user need. If people say, "I wouldnít pay much," or they would only use a free solution, itís probably not a real issue for them).||"Whatís prevented you from looking for a solution?"
"How much does the problem cost you in time and money?"
"If there was a solution to your problem, what would you pay for it?"
|7b If people answer "Yes" to Q6, letís find out more about their search for a solution.||"What specifically happened to make you start looking for a solution?"
"Tell me about how you looked for a solution to solve your problem."
"What solutions did you try?"
"What solutions did you reject?"
"How did you decide between one solution and another?"
"Are you happy with the solution youíve found?"
I've tried this technique now on dozens of interviews and it does seem a great way of getting to the heart of the user's problem. Try it out and let me know what you think in the comments.
About the author
Dr. David Travis (@userfocus on Twitter) holds a BSc and a PhD in Psychology and he is a Chartered Psychologist. He has worked in the fields of human factors, usability and user experience since 1989 and has published two books on usability. David helps both large firms and start ups connect with their customers and bring business ideas to market. If you like his articles, you'll love his online user experience training course.
Love it? Hate it? Join the discussioncomments powered by Disqus
Foundation Certificate in UX
Gain hands-on practice in all the key areas of UX while you prepare for the BCS Foundation Certificate in User Experience. More details
Every month, we share an in-depth article on user experience with over 10,000 newsletter readers. Want in? Sign up now and download a free guide to usability test moderation.
User Experience Articles
Our most popular articles
Our most commented articles
Our most recent articles
- Mar 6: Why iterative design isnít enough to create innovative products
- Feb 6: The Beginners' Guide to Contextual Interviewing
- Jan 9: The 8 competencies of user experience: a tool for assessing and developing UX Practitioners
- Dec 5: Non-UX books that every UX practitioner should read
- Nov 1: What one UX skill or ability is the most important to master?
Search for articles by keyword
- 7 articles tagged accessibility
- 4 articles tagged axure
- 5 articles tagged benefits
- 16 articles tagged careers
- 8 articles tagged case study
- 1 article tagged css
- 8 articles tagged discount usability
- 2 articles tagged ecommerce
- 14 articles tagged ethnography
- 14 articles tagged expert review
- 1 article tagged fitts law
- 4 articles tagged focus groups
- 1 article tagged forms
- 6 articles tagged guidelines
- 10 articles tagged heuristic evaluation
- 7 articles tagged ia
- 14 articles tagged iso 9241
- 10 articles tagged iterative design
- 3 articles tagged layout
- 2 articles tagged legal
- 11 articles tagged metrics
- 3 articles tagged mobile
- 7 articles tagged moderating
- 3 articles tagged morae
- 2 articles tagged navigation
- 9 articles tagged personas
- 15 articles tagged prototyping
- 7 articles tagged questionnaires
- 1 article tagged quotations
- 4 articles tagged roi
- 16 articles tagged selling usability
- 12 articles tagged standards
- 44 articles tagged strategy
- 2 articles tagged style guide
- 4 articles tagged survey design
- 5 articles tagged task scenarios
- 2 articles tagged templates
- 21 articles tagged tools
- 52 articles tagged usability testing
- 3 articles tagged user manual