It is a truth universally acknowledged, that a project team in possession of a UX budget must be in want of a research question.
Surprisingly, many customer and user studies do not begin with a considered research question. Instead they are motivated by uninteresting and superficial objectives such as the need to "do some research", "get some insights", "hear the voice of the customer", or "find some user needs."
These goals are not only uninspiring and reflect a lack of genuine curiosity, they are also too vague, too broad, and too unfocused to form the basis of an effective investigation. They are guaranteed to result in poor quality 'throw away' research that returns mostly obvious findings.
The first step of any research endeavor should be the development of a research question that will provide the central core around which an investigation, its methodology and its data analysis, can be developed.
Anatomy of a Research Question
By 'research question' I'm not talking about lists of questions you might generate and expect respondents to explicitly answer, either in an interview or in a questionnaire. I'm referring, instead, to the underlying question that describes the purpose of the research, and that guides the design and focus of a study.
For example, your question list may well ask a respondent, "Do you like coffee?" or "How many cups of coffee do you drink in a day?" or, "What's your favorite brand of coffee?" but your underlying research question is, "Does drinking coffee affect employee productivity?" This is not a question you can directly ask of anyone and get a useful answer but it is the focal point and driving force behind your investigation.
Without a specific research question, studies lack the ability to penetrate a problem. They skim the surface and risk becoming purely method driven. Instead of exploring new territory, they simply retread the same worn pathways, collect the same old user responses, and culminate in the same tedious research presentations that are guaranteed to put your design team to sleep.
In contrast, an effective research question will:
- Be interesting.
- Ask something that is important.
- Be focused and specific.
- Lead to a testable hypothesis.
- Allow you to make predictions based on measurable data.
- Advance your company's knowledge by going beyond the obvious.
"Going beyond the obvious" means pushing limits, asking new questions and venturing into new territory, or venturing deeper into territory you may have only tentatively visited before. We've talked previously about thinking like a detective, but at this stage of research planning we must think like an explorer — and as an explorer, you need to break new ground, otherwise you're doing it wrong.
We're often so eager for answers and solutions that we overlook the importance of a strong research question. But it is the question - not the answer - that is the most important part of research. As Jonas Salk put it:
"What people think of as the moment of discovery is really the discovery of the question".
We can avoid recycling the same old questions simply by shifting the starting point for our thinking. I'd like to describe one way to do that.
In a recent article, David Travis used an interesting analogy to differentiate field visits from traditional interviews. Here's what he wrote:
"A field visit is much more than a pop-up user interview in a coffee shop. To use the analogy of animal behaviour, an interview is like a visit to the zoo whereas field research is like going on safari. With field research you observe real behaviour: you see what people do, not listen to what they say they do. In short, you go where the action happens."
It's a good analogy. What's more, it leads us to an interesting way of shifting our research thinking.
Imagine trying to learn something new and interesting about a particular animal by observing it in a zoo. Stripped of its need to fight for survival or hunt for food, it will probably be either pacing its cage or sitting motionless for hours, or sleeping in a corner. Worse still the animal may have developed abnormal behaviour, sometimes called 'zoochosis' — repetitive, invariant behaviour patterns that have no obvious goal or function. Any opportunity for observing natural behaviour is lost because the animal's natural environment is missing.
That's why you never see Sir David Attenborough on his hands and knees observing animals in a zoo.
The same is true of interviews. Just like in a zoo, you typically remove the respondents from their real world environment and put them in a room where their unrepresentative 'made up' behaviours can be observed from a distance.
In contrast, on safari there are no constraints placed on the animals and they are running wild. They are in their natural environment with all of its pressures and dangers, and their natural behaviours and reactions to all kinds of situations are on display. The same is true when we conduct user research and observe people going about their real world activities.
So, the zoo vs. safari analogy works well. But what if we push this analogy a step further? What if we acknowledge the self-evident, though seldom voiced, fact that all customer and user research is actually the study of animal behaviour.
I sense a few raised eyebrows. But let's agree that this at least puts a different spin on things. Now let's see where it might lead…
Tinbergen's Four Questions
In 1963, Nobel Prize winning zoologist Niko Tinbergen published, 'On the aims and methods of ethology' in which he outlined four questions (sometimes referred to as Tinbergen's four problems).
He argued that, far from simply recording any specific behaviour and taking it at face value, the behaviours of animals (including humans) can be characterized by answering each of the four questions. Professors Paul Martin and Patrick Bateson summarize Tinbergen's questions in their own book, 'Measuring Behaviour' (a 'must read' for any user researcher, by the way). As I can't improve on their summary I'm going to paraphrase them here:
- What is the behaviour for?
This question concerns the behaviour's function. What is the behaviour currently used for and what is its survival value? How does the behaviour help the individual to survive and reproduce in its current environment?
- How does the behaviour work?
This question concerns proximate causation or control. How do causal factors control the behaviour? What kinds of stimuli elicit a behavioural response? What are the neurological, psychological and physiological mechanisms that mediate the behaviour?
- How did the behaviour develop?
This question concerns ontogeny — the development of the behaviour for that individual. How did the behaviour arise during the individual's lifetime? What internal or external factors influenced the behaviour's development? How do the developmental processes work? What is the nature of the interaction between the individual and its environment during development?
- How did the behaviour evolve?
This question concerns phylogeny — the evolutionary development of the behaviour in that particular species. What factors could have shaped the behaviour over the course of evolutionary history?
These seem like very good questions, and it is clear that they will help us avoid easy, quick and superficial explanations, and guide us towards a more thorough, insightful and detailed understanding of a specific behaviour. But, before we consider how we might use these questions in our user research, let's apply them to a specific everyday behaviour and see how they produce different kinds of answers.
Why do you Stop at red Traffic Lights?
Because it's the law. The answer is obvious — and not very interesting. But what would the answer be if we explained this behaviour in terms of Tinbergen's four questions?
I want to avoid causing an accident, being injured or injuring someone else. I also want to avoid being pulled over by a cop and getting a ticket.
I perceive a visual stimulus that excites my colour receptors and I process this information in my central nervous system, which triggers a specific response. The response results in me taking my foot off the accelerator pedal and pushing it down on the brake pedal.
I learned this rule by reading the Highway Code, and from my driving instructor, and by noticing that other cars, including cars on TV and in movies, also stop at red lights.
Historically, a red light has come to be an almost universal signal for controlling traffic at road junctions. They were first used in 1868 in London and involved gas lighting and semaphore arms. The first electric traffic light was employed in Salt Lake City in 1912.
All of these answers are correct, all of them are valid, but all of them are different. The resulting explanations complement each other and reveal facets of the specific behaviour that we may otherwise have missed. The four questions are logically distinct, and one way to think about them is as a set of four new tools (tools for probing, lenses for looking through) that you can use to approach a topic from new and different directions.
Behaviour is complicated and it follows that simplistic, trite, unimaginative and uninteresting questions leading to obvious answers won’t do. Tinbergen's four questions can give us a way of revealing insights that we might otherwise miss.
Going Beyond the Obvious
These four questions fit nicely into our field research toolbox. Now, instead of focusing primarily on just observing and recording behaviours, we can get more focused and start to 'unpack' a given behaviour or user interaction, and collect data that our previous 'blunt' questions could not detect.
Let's take a look at each of the four questions again, but this time in the context of a field visit in which the behaviours of interest now include specific product or system interactions.
The 'function' question (What is the behaviour for?)
This is the closest to the kind of implicit question we typically ask.
- What is this solution or interaction about?
- What is the product or system or feature used for?
- What is the user trying to accomplish by using it?
- What user goals are being met?
- How does this behaviour or interaction help the user (and the company, if we are observing a work environment) to be successful?
- Compared to not carrying out this behaviour (or not using this product or system) what advantage does the user now have over competitors or other users?
The proximate causation question (How does the behaviour work?)
This question invites us to ask:
- What triggers the behaviour or interaction?
- How is the interaction being controlled?
- What are the steps or events and actions leading up to it?
- What is the behaviour or interaction a response to?
- What other activities or functions are involved in mediating this behaviour?
- What's going on in the system right now?
- What's going on in the mind of the user?
- What mechanisms are working to support the behaviour and what things are getting in the way?
- Is the user in control?
The ontogenesis question (How did the behaviour develop?)
This question requires us to understand how the behaviour came about.
- How did this particular user learn this particular action or step?
- What training was required?
- How easy or difficult was it to learn this behaviour?
- What level of skill is required?
- Is the user's skill level increasing over time?
- What were those early learning steps like for this user?
- Was he/she anxious or confident during first use?
- At the company level, what support is given?
- Are training courses available?
- What do training materials look like?
The phylogeny question (How did the behaviour evolve?)
We can often move our understanding forwards by first going backwards, and this question invites us to do just that. Thankfully, we don’t have to worry about geological time scales, but we can certainly go back decades, if necessary, and discover the evolutionary history of a product or system and the origin of a behaviour.
- What was the origin of the behaviour/interaction/interface/product?
- What was it originally trying to solve?
- What previous versions have existed?
- When did the problem first appear?
- What behaviour existed before this solution?
- How was the task carried out back then?
- What has prompted design or technology changes over the years?
- Would we have solved the original problem differently?
- If so, where might evolutionary iterations of our original (hypothetical) solution have brought us to by today?
Try including these four questions next time you carry out your field research. Ask them of each example of user behaviour you identify. Use them as a framework around which to design a study that avoids mundane 'top of mind' questions, banal answers, and uninsightful insights — not to mention mind-numbingly dull presentations.
Tinbergen, N. (1963). "On aims and methods of ethology." Zeitschrift für Tierpsychologie, 20.
Martin, P. & Bateson, P. (1986) Measuring behaviour — An introductory guide. Cambridge University Press.
About the author
Dr. Philip Hodgson (@bpusability on Twitter) holds a B.Sc., M.A., and Ph.D. in Experimental Psychology. He has over twenty years of experience as a researcher, consultant, and trainer in usability, user experience, human factors and experimental psychology. His work has influenced product and system design in the consumer, telecoms, manufacturing, packaging, public safety, web and medical domains for the North American, European, and Asian markets.
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 recent articles
- Apr 3: Is Usability a Science?
- 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
Our most commented articles
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
- 11 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
- 53 articles tagged usability testing
- 3 articles tagged user manual