Book review: “Just Enough Research”
Back in 2013, Erika Hall, co-founder of Mule Design, wrote “Just Enough Research”. In this book, Hall explains why good customer research is so important. She outlines what makes research effective and provides practical tips on how to best conduct research. Reading “Just Enough Research” reminded me of reading “Rocket surgery made easy” by Steve Krug and “Undercover UX” by Cennydd Bowles, since all three books do a good job at both explaining and demystifying what it takes to do customer research.
These are the main things that I learned from reading “Just Enough Research”:
- What is research? — Right off the bat, Hall makes the point that in order to innovate, it’s important for you to know about the current state of things and why they’re like that. Research is systematic inquiry; you want to know more about a particular topic, so you go through a process to increase your knowledge. The specific type of process depends on who you are and what you need to know. This is illustrated through a nice definition of design research by Jane Fulton Suri, partner at design consultancy IDEO (see Fig. 1).
- Research is not asking people what they like! — I’m fully aware of how obvious this statement probably sounds. However, customer researcher is NOT about asking about what people do or don’t like. You might sometimes hear people ask users whether they like a particular product or feature; that isn’t what customer research is about. Instead, the focus is on exploring problem areas or new ideas, or simply testing how usable your product is.
- Generative or exploratory research — This is the research you do to identify the problem to solve and explore ideas. As Hall explains “this is the research you do before you even know what you’re doing.” Once you’ve gathered information, you then analyse your learnings and identify the most commonly voiced (or observed) unmet customer needs. This will in turn result in a problem statement or hypothesis to concentrate on.
- Descriptive and explanatory research — Descriptive research is about understanding the context of the problem that you’re looking to solve and how to best solve it. By this stage, you’ll have moved from “What’s a good problem to solve” to “What’s the best way to solve the problem I’ve identified?”
- Evaluative research — Usability testing is the most common form of evaluative research. With this research you test that your solution is working as expected and is solving the problem you’ve identified.
- Casual research — This type of research is about establishing a cause-and-effect relationship, understanding the ‘why’ behind an observation or pattern. Casual research often involves looking at analytics and carrying out A/B tests.
- Heuristic analysis — In the early stages of product design and development, evaluative research can be done in the form of usability testing (see point 5. above) or heuristic analysis. You can test an existing site or application before redesigning. “Heuristic” means “based on experience”. A heuristic is not a hard measure; it’s more of a qualitative guideline of best usability practice. Jakob Nielsen, arguably the founding father of usability, came up with the idea of heuristic analysis in 1990 and introduced ten heuristic principles (see Fig. 2).
- Usability testing — Testing the usability of a product with people is the second form of evaluative testing. Nielsen, the aforementioned usability guru, outlined five components that define usability (see Fig. 3). Hall stresses the importance of “cheap tests first, expensive tests later”; start simple — paper prototypes or sketches — and gradually up the ante.
Main learning point: “Just Enough Research” is a great, easy to read book which underlines the importance of customer research. The book does a great job in demonstrating that research doesn’t have to very expensive or onerous; it provides plenty of simple and practical to conduct ‘just enough research’.
Fig. 1 — Definition of “design research” by Jane Fulton Suri — Taken from: https://www.ideo.com/news/informing-our-intuition-design-research-for-radical-innovation
“Design research both inspires imagination and informs intuition through a variety of methods with related intents: to expose patterns underlying the rich reality of people’s behaviours and experiences, to explore reactions to probes and prototypes, and to shed light on the unknown through iterative hypothesis and experiment.”
Fig. 2 — Jakob Nielsen’s 10 Heuristics for User Interface Design (taken from: http://www.nngroup.com/articles/ten-usability-heuristics/)
- Visibility of system status — The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
- Match between system and the real world — The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
- User control and freedom — Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
- Consistency and standards — Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
- Error prevention — Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
- Recognition rather than recall — Minimise the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
- Flexibility and efficiency of use — Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
- Aesthetic and minimalist design — Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
- Help users recognise, diagnose, and recover from errors — Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
- Help and documentation — Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.
Fig. 3 — Jakob Nielsen’s 5 components of usability — Taken from: Erika Hall. Just Enough Research, pp. 105–106
- Learnability — How easy is it for users to accomplish basic tasks the first time they come across the design?
- Efficiency — Once users have learned the design, how quickly can they perform tasks?
- Memorability — When users return to the design after a period of not using it, how easily can they reestablish proficiency?
- Errors — How many errors do users make, how severe are these errors, and how easily can they recover from the errors?
- Satisfaction — How pleasant is it to use the design?