第 1 章
The Art and Science of Understanding Users
Have you ever wondered why so many products are frustratingly difficult to use despite companies claiming they prioritize simplicity? Or why tech giants like Apple create such intuitive experiences while others fail miserably? "Think Like a UX Researcher" by David Travis and Philip Hodgson offers a masterclass in understanding users that has become required reading at companies like Google, Amazon, and Microsoft. The book has gained cult status among product teams worldwide, with Elon Musk reportedly keeping a copy on his desk during Tesla's interface redesigns. Beyond its practical applications, the book has sparked a philosophical shift in how companies approach product development-moving from "we know what users want" to "let's discover what users need." At its core, this isn't just a methodology guide but a manifesto for human-centered design in an increasingly digital world.
第 2 章
The Seven Deadly Sins That Plague User Research
Despite the growing emphasis on user experience, many companies struggle to distinguish good UX research from bad. The problem isn't insufficient research but poor quality research that fails to provide actionable insights. Seven deadly sins plague UX research efforts across organizations of all sizes.
Credulity tops the list-blindly believing what users say they want rather than observing what they actually do. Users are notoriously unreliable narrators of their own behavior, often unable to articulate their true needs or predict their future actions. As Henry Ford supposedly quipped, "If I had asked people what they wanted, they would have said faster horses."
Dogmatism manifests when researchers insist there's only one "right" research method, whether it's usability testing, field research, or surveys. Each method has strengths and weaknesses, and the best researchers select techniques based on the specific questions they need to answer.
Bias creeps in when researchers collect data in ways that skew results, such as asking leading questions or selecting unrepresentative participants. Even subtle cues from researchers can dramatically influence participant behavior.
Obscurantism occurs when findings remain trapped in one researcher's head rather than being shared widely with development teams. Research that doesn't reach decision-makers might as well not exist.
Laziness tempts researchers to recycle old findings rather than conducting fresh research for new questions. While building on previous work is valuable, assuming old insights apply to new problems leads to stagnation.
Vagueness manifests in unfocused research that fails to address specific questions. Without clear research objectives, studies become fishing expeditions that waste resources and yield little actionable insight.
Finally, hubris appears when researchers take excessive pride in producing detailed reports rather than focusing on driving action. The value of research lies not in impressive documentation but in its impact on product decisions.
Perhaps the deadliest sin of all is an organization's inability to distinguish quality research from poor research-a fundamental failure that perpetuates all the others and ultimately leads to bad design.
第 3 章
The Detective Mindset: Methodical Investigation of User Behavior
Sherlock Holmes offers the perfect model for UX researchers. Like Holmes, great researchers approach their work as methodical investigations rather than exercises in confirmation bias. The detective mindset involves five critical steps that transform casual observation into scientific insight.
First, understand the problem thoroughly before attempting to solve it. Holmes never rushed to conclusions but instead took time to grasp the full context of each case. Similarly, UX researchers must understand business objectives, user needs, and technical constraints before designing research studies.
Second, collect facts through careful observation without filtering or interpreting too early. Holmes famously noticed minute details others overlooked-a skill equally valuable for researchers observing user behavior. The key is separating observation from interpretation, noting exactly what users do before attempting to explain why.
Third, develop hypotheses based on evidence, not assumptions. Holmes brought specialized knowledge to each case, allowing him to form plausible explanations for the facts he observed. UX researchers similarly apply their understanding of human psychology, interaction design principles, and domain knowledge to interpret user behavior.
Fourth, eliminate unlikely explanations through systematic testing. Holmes methodically ruled out possibilities until only the truth remained. Good researchers similarly test multiple hypotheses rather than becoming attached to their first explanation.
Finally, act decisively on solutions once the evidence is clear. Research without action is merely academic-the goal is improving products through evidence-based design decisions.
As real-life detective Peter Stott advises: "Never, ever, ever, act on assumptions. Search out the facts and act on those." This principle forms the foundation of effective UX research, distinguishing it from opinion-based design approaches that rely on intuition rather than evidence.
第 4 章
The Two Fundamental Questions in UX Research
All UX research ultimately answers one of two fundamental questions, each requiring different methodological approaches. Understanding this distinction helps researchers select appropriate techniques for specific research objectives and ensures research efforts align with product development goals.
The first question-"Who are our users and what are they trying to do?"-requires field research. Like going on safari to observe animals in their natural habitat, field research examines user behavior in context. Researchers visit users' homes or workplaces to observe authentic behaviors, understand workflows across channels, and validate whether the problem they're solving matters to users. This outward-looking research ensures teams build the right product. Field researchers might shadow a nurse during their shift to understand hospital workflows, observe families planning vacation itineraries, or spend time with small business owners managing their finances. These immersive experiences reveal unexpected insights about user needs, pain points, and workarounds that wouldn't emerge in controlled settings.
The second question-"Can people use the thing we've designed to solve their problem?"-calls for usability testing. Like examining specimens under a microscope, usability testing evaluates specific design solutions by observing users attempting to complete tasks. This inward-looking research ensures teams build the product right. Usability testing might involve watching users navigate a new mobile app interface, complete an online checkout process, or configure software settings. Researchers carefully note where users struggle, become confused, or fail to complete intended actions.
Both approaches are essential but serve different purposes at different stages of product development. Field research belongs primarily in the discovery phase, helping teams understand user needs before designing solutions. It answers questions like "What problems are worth solving?" and "How do users currently address these challenges?" Usability testing belongs in the evaluation phase, helping teams refine solutions to meet those needs effectively. It addresses questions like "Can users complete key tasks?" and "Where do they encounter friction?"
Many product failures stem from confusing these approaches or skipping one entirely. Teams often jump straight to usability testing without first conducting field research, resulting in well-designed products that solve the wrong problems. For example, a team might create an elegantly designed expense reporting app that employees can easily navigate but fails to address their actual pain point of gathering receipts. Alternatively, teams conduct field research but skip usability testing, creating products that address real needs but implement solutions poorly, like a banking app that identifies genuine user needs but has an overly complex authentication process.
The most successful products emerge from teams that understand and apply both approaches appropriately-using field research to identify meaningful problems and usability testing to validate their solutions. This dual approach ensures products not only address genuine user needs but also implement solutions in ways that users can effectively utilize. Leading companies often establish regular cycles of both types of research, using field studies to inform product strategy and regular usability testing to optimize execution.
第 5 章
The Psychology Behind User Behavior
While UX job descriptions often require psychology backgrounds, four fundamental psychological principles prove most relevant to researchers. Understanding these principles helps researchers avoid common misconceptions about user behavior.
First, users don't think like you think. They value different things, perceive interfaces differently, and possess different knowledge than designers and developers. This "false consensus effect" leads teams to overestimate how many users share their preferences and abilities. Development teams consistently overestimate users' technical competence, assuming users understand terminology and concepts familiar to insiders.
Second, users lack insight into their own behavior. When asked why they performed certain actions, users often invent plausible but incorrect explanations. This "narrative fallacy" reflects our human tendency to create coherent stories explaining our behavior, even when those stories bear little relationship to reality. This is why asking users "Why did you do that?" often yields misleading information.
Third, past behavior predicts future behavior better than stated intentions. Users' claims about what they would do in hypothetical situations correlate poorly with their actual behavior when those situations arise. This "intention-behavior gap" explains why preference-based research ("Which design do you like better?") rarely predicts which design will actually perform better in real-world use.
Fourth, user behavior depends heavily on context. The same person might interact differently with the same interface depending on their environment, goals, time constraints, and emotional state. This "fundamental attribution error" leads researchers to attribute behaviors to personality traits when they actually result from situational factors.
These principles explain why effective UX research focuses on observing behavior rather than collecting opinions. Watching what users do provides more reliable insights than asking what they prefer or how they would behave in hypothetical scenarios. This observation-based approach helps teams overcome their own biases and build products that match how users actually behave-not how teams think they should behave.
第 6 章
Beyond Iteration: The Path to True Innovation
While iterative design has become standard practice in product development, it excels at creating incrementally better versions of existing products but rarely delivers true innovation. Using the Design Council's Double Diamond model helps explain why, and reveals the crucial differences between improvement and innovation.
The model divides the design process into four distinct phases: Discover (exploring user needs), Define (framing the problem), Develop (creating potential solutions), and Deliver (implementing the chosen solution). Most teams rush to the Develop and Deliver phases while neglecting the crucial Discover and Define phases where innovation actually happens. This eagerness to jump to solutions often results in well-executed products that solve the wrong problems.
Many teams mistakenly believe that usability testing constitutes discovery research. However, usability testing is fundamentally inward-looking, focused on improving existing solutions rather than questioning fundamental assumptions. It can tell you if users can complete tasks with your current design but can't reveal whether you're solving the right problems. For example, a bank might conduct extensive usability testing on their mobile check deposit feature, but miss the larger opportunity to reimagine how people manage their finances in the digital age.
True innovation requires comprehensive field research that explores users' needs, goals, and motivations across a wide spectrum-not just representative users but also edge cases and unexpected user types. This outward-looking research helps teams identify unmet needs and opportunities for disruptive solutions. Methods like contextual inquiry, diary studies, and ethnographic observation can reveal insights that traditional market research might miss. For instance, studying how people manage household emergencies might reveal opportunities for new insurance products that traditional surveys would never uncover.
Consider Uber's innovation in the transportation market. They didn't simply iterate on taxi service interfaces; they fundamentally reconceptualized the transportation experience based on deep understanding of user pain points across the entire journey. This required looking beyond how people used existing services to understand broader transportation needs and frustrations. Their research revealed that uncertainty about arrival times, payment friction, and variable service quality were universal pain points that transcended traditional taxi services.
Similarly, Airbnb's success came from understanding not just how people book accommodations, but how they desire to experience travel and connection. Their extensive research into both hosts and travelers revealed opportunities for creating entirely new categories of travel experiences.
Without proper discovery research, organizations may improve their products incrementally but remain vulnerable to disruptive startups who better understand user needs. The most innovative companies invest heavily in understanding users before designing solutions, ensuring they build products that address meaningful problems rather than simply refining existing approaches. Companies like IDEO and Google's X lab demonstrate this by spending months or even years in the discovery phase before moving to solution development.
The key to breaking free from the iteration trap is to allocate sufficient time and resources to the early phases of the design process, embracing uncertainty and remaining open to unexpected insights that could lead to breakthrough innovations. This might mean conducting research in adjacent markets, studying extreme users, or exploring analogous situations in completely different domains.
第 7 章
The Automation Paradox in UX Research
UX research methods have evolved dramatically over the past two decades, moving increasingly toward automated, unmoderated approaches. While these methods-like remote usability testing, automated summative testing, and online surveys-offer advantages in speed, cost, and scale, they create a problematic distance between researchers and users.
This shift toward automation reflects broader organizational pressures for faster, cheaper research that generates quantitative data. Numbers feel more scientific and objective to stakeholders than qualitative insights. However, this trend blocks researchers from understanding the crucial "why" behind user behavior.
Automated methods show what users do but rarely reveal why they do it. When a participant struggles with a task during unmoderated testing, researchers can't ask follow-up questions to understand the confusion. When survey respondents abandon a questionnaire, researchers can't observe their frustration or ask what went wrong.
This creates what psychologists call the "empathy gap"-the inability to understand or share feelings experienced by others. Direct observation of users interacting with products creates empathy that drives better design decisions. When team members watch real people struggle with their products, they develop emotional motivation to fix problems that statistics alone rarely provide.
Additionally, automated research removes the "teachable moments" where researchers can probe deeper into unexpected user behaviors. These serendipitous discoveries often lead to the most valuable insights-the kind that transform products rather than merely refining them.
Good-quality UX research requires triangulation: combining automated methods (showing what users do) with moderated methods (revealing why they do it). The most effective research programs use automated techniques to identify patterns and moderated techniques to explain them, creating a comprehensive understanding of user behavior that drives meaningful innovation.
第 8 章
From Observation to Insight: Creating Actionable Design Solutions
Identifying usability problems is only half the battle-the real challenge is translating observations into actionable design solutions. This transformation requires a structured three-step process that bridges the gap between what researchers see and what designers create.
The process begins with generating insights-identifying the underlying patterns behind surface observations. After collecting raw observations from usability tests (direct quotations, user actions, pain points), researchers group related items to create an affinity diagram. These groupings reveal deeper patterns that might not be apparent from individual observations.
From these patterns, researchers craft insight statements that capture what they've learned about user behavior. Good insights are provocative, concise, and reveal something non-obvious about users. For example, rather than noting "Users couldn't find the search button," an insight might be "Users expect search functionality to be available throughout their journey, not just on the homepage."
The second step involves developing hypotheses about what's causing these underlying problems. For each insight, researchers ask "Why is this happening?" and generate multiple possible explanations. This prevents jumping to conclusions based on preconceived notions.
Finally, researchers create the simplest possible design solutions that might address each hypothesis. This "tweaking" approach avoids major redesigns and fits well with rapid, iterative development. For example, if users struggle to find important information, solutions might include highlighting key content, reorganizing page elements, or adding contextual help.
As a UX researcher, actively participating in solution development is essential. Your unique perspective from observing users struggling with the product makes you a valuable contributor to the design process. While designers bring creative expertise, researchers bring user understanding that ensures solutions address real problems rather than symptoms.
This systematic approach transforms research from a documentation exercise into a catalyst for meaningful design improvements. By connecting observations to insights, hypotheses, and solutions, researchers ensure their work drives tangible product enhancements rather than collecting dust in detailed reports.
第 9 章
Measuring Success: Translating UX Improvements into Business Value
Success rate and time on task are the two critical metrics that translate usability improvements into financial benefits. These metrics provide compelling evidence for design changes by connecting user experience directly to business outcomes.
For revenue-generating websites, even modest improvements in completion rate yield significant returns. Consider an e-commerce site with $100 million in annual sales where 70% of visitors successfully complete purchases. Increasing that success rate to just 75% (a 5 percentage point improvement) could generate over $7 million in additional revenue annually. This calculation provides powerful justification for investing in user experience improvements.
For internal systems like intranets, reducing time on task creates measurable cost savings. If 100,000 employees spend just 15 seconds less on a daily task (like finding colleagues in a directory), with an average loaded salary of $15/hour, the organization could save over $1.3 million annually. These efficiency gains compound across multiple tasks and systems, creating substantial organizational value.
When calculating these financial benefits, conservative estimates maintain credibility with stakeholders. For example, when calculating revenue improvements, assume that only a portion of increased completions will convert to actual sales. For time savings, consider only the most frequent tasks rather than claiming productivity gains across all activities.
Beyond these direct financial measures, UX metrics help teams track progress throughout development. Setting target values based on competitor benchmarks or previous versions establishes meaningful goals. Remote online usability tests provide an efficient way to gather these metrics regularly, ideally within each development sprint.
This metrics-based approach complements traditional qualitative research rather than replacing it. Online tests capture the "what" of usability problems at scale, while small sample lab tests help understand the "why." The most successful teams combine both approaches to get a complete picture of user experience issues and their business impact.
第 10 章
Building Influence: Making Research Drive Real Change
UX researchers often struggle to get development teams to act on their findings because traditional research reports are too lengthy, arrive too late, and fail to engage teams with the data. The fundamental principle for effective research communication is that "UX research is a team sport"-development teams should be directly involved in planning, observing, and analyzing research rather than just receiving reports.
When direct team involvement isn't possible, researchers should focus on getting teams to engage with real data rather than assumptions. Effective techniques include user journey maps that visualize the entire experience, photo-ethnographies that use images to convey context, affinity diagramming where observers collectively sort findings, screenshot forensics that connect user quotes to interface elements, and hallway evangelism through infographic posters in high-traffic areas.
The most effective UX debrief meetings follow a clear structure that drives action. Rather than rehashing the research report, these meetings focus on open discussion of findings, prioritization of issues, and collective ownership of solutions. Co-chairing with the product owner, ensuring decision-maker attendance, and avoiding PowerPoint presentations all contribute to more effective outcomes.
For stakeholders who don't have time to read detailed reports, user experience dashboards provide concise visual summaries of key metrics. Following ISO's definition of usability, these dashboards should measure effectiveness (success rate), efficiency (task time), and satisfaction (user ratings). Presenting these metrics graphically with confidence intervals and representative user quotes gives managers an at-a-glance assessment without overwhelming them with documentation.
Remember Caroline Jarrett's insight: "User researcher's fallacy: 'My job is to learn about users'. Truth: 'My job is to help my team learn about users'." No presentation will be more persuasive than having the development team directly observe users struggling with their product-creating the emotional motivation that drives meaningful change.
第 11 章
The Reflective Researcher: Continuous Growth Through Critical Analysis
The best UX researchers don't just gain experience through practice-they deliberately analyze their work through conscious reflection. This critical thinking about your performance helps identify why you chose certain approaches, what theory supported your decisions, what constraints you faced, and what alternatives might have worked better.
Reflection is powerful because experience alone doesn't guarantee learning. We've all met people with "ten years of experience" who really have one year repeated ten times. Successful researchers reflect to improve their practice, identify training gaps, create portfolio entries, establish patterns for future research, and develop content for professional sharing.
This process can take many forms-written journals, electronic notebooks, video diaries, peer discussions, or mentor feedback. Unlike project retrospectives that broadly cover team performance, personal reflection focuses specifically on your UX research practice. This should be done continuously throughout projects, particularly after completing research phases or when feeling especially good or bad about an outcome.
A structured reflection might include documenting the specific activity, analyzing why you chose that approach, identifying what went well and poorly, exploring the deeper reasons behind these outcomes using techniques like the five Whys, and determining how to apply these insights to future work. The goal isn't just logging activities but critically analyzing your performance to continuously improve your practice.
Understanding your epistemological bias-whether you lean toward positivism (seeking objective truth through scientific methods) or interpretivism (recognizing that knowledge is subjective and context-dependent)-also enhances self-awareness. The best researchers tend to use mixed methods, combining both traditions to gain comprehensive understanding of user behavior.
This reflective practice transforms experience into expertise, helping researchers develop not just technical skills but also the process and marketing skills that distinguish truly exceptional practitioners. By continuously examining and refining their approach, reflective researchers ensure their work becomes increasingly valuable to both users and organizations.
