A Book Apart · 2019
Most product and design decisions fail not because teams lack ideas, but because they avoid doing disciplined, purposeful research to understand real user behaviour.
Best opened when
You are running interviews or discovery work but feel your insights are too shallow, anecdotal, or hard to defend.
Quick skim
A practical argument for doing just enough structured user research to make decisions defensible — without turning discovery into a slow, academic exercise.
Key ideas
Define what you need to learn before choosing how to research it.
Treat interviews as structured evidence collection, not casual conversations.
Optimise for decision-relevant insight, not exhaustive understanding.
Deep read
This brief emphasises how the book improves interview quality and decision credibility, rather than treating it as a catalogue of research techniques.
Read this as an evidence-discipline book, not a research-methods book.
This brief emphasises how the book improves interview quality and decision credibility, rather than treating it as a catalogue of research techniques.
Covers
Research framing, interview design, bias avoidance, and pragmatic method selection.
Leaves out
Deep synthesis methods and output design, because the book is relatively light in these areas.
Argument arc
Just Enough Research builds its argument by first challenging the implicit assumption that research is either too expensive, too slow, or too specialised to be part of everyday product and design work.
Just Enough Research builds its argument by first challenging the implicit assumption that research is either too expensive, too slow, or too specialised to be part of everyday product and design work. Hall begins by reframing research not as an academic exercise but as a practical tool for reducing uncertainty. This shift matters because it removes the psychological and organisational barriers that often prevent teams from engaging in research at all. If research is seen as optional or "nice to have," it will always be deprioritised. By positioning it as a core decision-making input, the book establishes why it must happen.
From there, the argument moves into a second layer: not all research is equal, and poorly designed research is actively harmful. Hall emphasises that bad research — leading questions, biased sampling, unclear goals — creates false confidence. This is a critical escalation in the argument. It is no longer enough to say "talk to users." The book insists that how you talk to users determines whether your insights are trustworthy. This is where the discipline begins to take shape: defining learning goals, choosing appropriate methods, and structuring interviews carefully.
Waypoint in practice
This book changes how teams approach the very beginning of discovery work. Instead of jumping straight into techniques like journey mapping or ideation, it forces teams to define what they need to learn, design interviews with intent, and treat evidence collection as a disciplined activity. In practice, this means facilitation gets more deliberate before the first participant conversation: learning goals are written down, question design is checked for bias, and the workshop output is judged by whether it could support a real decision rather than by how insightful the themes feel.
Before selecting a discovery method, write down the decision the team is trying to support and the specific unknowns blocking it; if those unknowns are still about user behaviour, delay mapping or ideation and start with interviews.
Build the research plan around learning goals, participant criteria, and question design first, then choose how many interviews and what method shape is enough to reduce uncertainty.
Replace vague insight notes with evidence tagged to observed behaviours, concrete examples, and unanswered questions so later artifacts are built on traceable signal rather than impressions.
Use the evidence to narrow or rewrite the problem frame, and explicitly mark which proposed directions are now supported, unsupported, or still assumption-led.
Continue reading
Discovery gets noisy when stakeholder intuition is treated like field signal. This principle protects technique choice, workshop framing, and outputs from being driven by polite encouragement or internal confidence.
A discovery plan that enters workshops with better evidence discipline and clearer alignment on what counts as real signal.
The final movement of the argument introduces the idea of "just enough." This is not a call to do minimal work, but to align research effort with decision needs. Hall argues that research should be scoped based on what decisions need to be made, not on arbitrary standards of rigor or completeness. This reframing has a direct consequence: teams can move faster without sacrificing credibility, because they are no longer chasing exhaustive understanding. Instead, they are focused on collecting sufficient evidence to support a specific decision — and that is why the book matters as a practitioner lens rather than a methodology guide.
One of the most important shifts the book makes is redefining the purpose of research. Rather than treating research as a general activity for "understanding users," Hall argues that research is only meaningful when it is connected to a decision. This reframing matters because it forces teams to clarify what they are trying to achieve before they begin. Without a decision in mind, research becomes exploratory in the worst sense — broad, unfocused, and difficult to act on.
The book supports this claim by showing how easily research can drift into irrelevance. Teams often collect large amounts of data, conduct numerous interviews, and generate extensive documentation, only to find that none of it directly informs what to do next. This happens because the research was not anchored to a decision. By contrast, when research is scoped around a specific decision — for example, whether to pursue a particular opportunity or how to frame a problem — it becomes easier to determine what questions to ask, who to talk to, and when to stop.
This idea connects directly to the concept of "just enough." If research is decision-driven, then "enough" is defined by whether the team has sufficient evidence to make that decision confidently. This prevents both under-researching and over-researching. However, practitioners often misapply this idea by using it to justify minimal effort. The point is not to do less research, but to do the right amount of targeted research. This requires discipline in defining the decision upfront, which is where many teams struggle — and where Hall's framing is most practically useful.
Most teams don't lack access to users — they lack discipline in what they ask and how they listen.
A central idea in the book is the reframing of interviews. Many teams approach interviews as informal conversations, prioritising comfort and flow over structure. Hall argues that this approach undermines the quality of the data collected. Interviews are not social interactions; they are a method for gathering evidence about behaviour, context, and decision-making.
This matters because human conversation is inherently biased. People want to please, to be liked, and to tell coherent stories about themselves. Without structure, interviews drift toward opinion and speculation rather than observable behaviour. Hall emphasises the need for carefully designed discussion guides, neutral questioning, and a focus on past actions rather than hypothetical scenarios. These techniques are not about making interviews rigid, but about ensuring that the information collected is reliable.
The book reinforces this idea through examples of common mistakes: leading questions, vague prompts, and over-reliance on self-reported preferences. Each of these introduces bias and reduces the credibility of the findings. By contrast, structured interviews that probe for specific examples and contexts produce richer, more actionable insights.
Practitioners often misapply this idea by swinging too far toward rigidity, turning interviews into scripts that limit exploration. The balance is critical: structure should guide the conversation, not constrain it. The goal is to maintain enough control to gather reliable evidence while remaining open to unexpected insights. That calibration is more skill than recipe, which is why the book's emphasis on learning goals and deliberate question design is more durable than any specific script.
"Just enough" is not a timebox; it is a threshold of decision confidence.
One of the book's most forceful claims is that bad research is not neutral — it actively harms decision-making. This is a crucial escalation in the argument because it challenges the common belief that any research is better than none. Hall demonstrates that poorly designed research introduces bias, reinforces existing assumptions, and creates a false sense of certainty.
This idea matters because it shifts the standard for acceptable research practice. If bad research is harmful, then teams cannot afford to treat research casually. They must invest in getting the fundamentals right: clear goals, appropriate methods, and disciplined execution. Otherwise, they risk making decisions based on flawed evidence.
The book illustrates this through examples of common pitfalls, such as confirmation bias and poorly defined samples. These issues are not subtle; they fundamentally distort the findings. For example, interviewing only engaged users may lead a team to overlook critical friction points experienced by less engaged users. Similarly, asking leading questions can produce answers that align with what the team wants to hear rather than what is true.
Practitioners often underestimate this risk because the outputs of bad research can look convincing. Well-presented insights, compelling quotes, and polished reports can create the illusion of rigor. The book's contribution is to make this illusion visible, encouraging teams to scrutinise their methods as much as their findings. This is why the book works as a quality standard rather than just a how-to guide: it changes what counts as acceptable evidence, not just how evidence is gathered.
The concept of "just enough" is central to the book, but it is also the most easily misunderstood. Hall does not advocate for minimal research; she advocates for appropriately scoped research. This requires teams to define what they need to learn and design their research accordingly.
This idea matters because it resolves a common tension in product and design work: the need to move quickly versus the need to make informed decisions. By focusing on decision-relevant evidence, teams can avoid both extremes. They do not need to conduct exhaustive studies to gain confidence, but they also cannot skip research entirely.
The book supports this idea by showing how arbitrary constraints — such as fixed timelines or resource limits — often lead to either rushed or excessive research. Instead, the scope should be driven by the complexity of the decision and the level of uncertainty. Simple decisions may require only a few interviews, while more complex decisions may require multiple methods.
Practitioners often misapply this idea by using it to justify doing less work. This happens when "just enough" is interpreted as "as little as possible." The correct interpretation is "as much as necessary." This requires judgment, which is why the book emphasises planning and scoping as critical skills. In Waypoint terms, the more useful question is not "how much research is enough?" but "what decision does this research need to unlock, and have we collected sufficient evidence to support it?" That shift in framing is where the book has most practical traction.
The book's primary limitation is its relative lack of depth in synthesis and decision translation. While it excels at helping teams gather better evidence, it offers less guidance on how to turn that evidence into actionable outputs. The chapters on synthesis and analysis are noticeably shorter and less developed than those on research planning and interview design, leaving a gap between insight collection and the service or product decisions that follow. Additionally, some of the advice will feel familiar to experienced practitioners. The book's simplicity is a strength for teams new to structured discovery, but it also means that those who already run disciplined discovery work may find themselves reinforcing habits they already hold rather than encountering genuinely new thinking. The book is more useful for raising a team's floor than for extending an expert's ceiling — and Waypoint briefs should frame it accordingly rather than positioning it as advanced methodology.
A final important idea is the democratisation of research. Hall argues that research should not be confined to dedicated researchers or treated as a separate phase of work. Instead, it should be integrated into the way teams operate, with designers, product managers, and others participating in the process.
This matters because it increases both the speed and impact of research. When teams are directly involved in research, they gain a deeper understanding of users and are more likely to act on the insights. It also reduces the bottleneck created by relying on a small number of specialists.
The book supports this idea by showing that many research activities — particularly interviews — can be conducted effectively by non-specialists, provided they follow basic principles. This lowers the barrier to entry and encourages more frequent use of research.
However, this idea is often misapplied by underestimating the value of expertise. While non-specialists can conduct research, they still need guidance and support to avoid common pitfalls. The goal is not to eliminate the role of researchers, but to distribute research capability across the team. For Waypoint, the operative implication is lighter: the techniques and patterns that work well with this book do not require a dedicated researcher, but they do require someone in the session who understands the difference between opinion and evidence and is willing to enforce it.
Read Just Enough Research when your discovery work lacks credible evidence and your interviews feel shallow, biased, or hard to defend in a planning conversation. It is particularly valuable early in the process, before problem framing or mapping, where the quality of your evidence determines everything that follows. Do not reach for it when you already have strong, recent evidence and need help turning that into decisions or service outputs — the book does not take you far enough into synthesis or action translation. Waypoint should carry forward its core discipline: evidence must be intentional, structured, and decision-relevant, or it is not worth collecting at all.
This book reframes the Interview Discussion Guide Workshop from a question-writing exercise into a discipline for protecting evidence quality before the first participant conversation happens.
Before we write questions, let's name the decision this research needs to support and the behaviours we need evidence on. If a question invites opinion, prediction, or approval, rewrite it until it gets us closer to what people actually did, chose, or worked around.
Open method →The book's consistent push toward concrete behaviour, decision context, and evidence over opinion directly explains why JTBD-style interviewing produces more defensible signal than general discovery conversations.
Ready to apply Interview Discussion Guide Workshop?
Start workspace →