Sample Chapter from DISCOVER: The Moderator’s Mindset
A Head Start
Tom was already at the table when the others arrived, his notebook open in front of him.
“I have a confession,” he said.
Shelton set down his coffee. “Go on.”
“I ran into my buddy, Derek, this weekend. He does a lot of backcountry camping. We were at his place Saturday night, and I thought, he’s exactly the kind of person we’re trying to talk to. So I wanted to try some things out. I started asking him questions, you know, for this project.”
Jenna looked up. “You interviewed him?”
“Yes. Well, I tried to.” Tom turned his notebook toward them. The page was covered in notes, but several lines had been crossed out, and there were question marks scattered through the margins. “Honestly, it was kind of frustrating. Derek wasn’t very helpful.”
Shelton glanced at the notebook. “What do you mean, not helpful?”
“He just kept pushing back on everything. I asked him about the new DCF tents. You know, Dyneema Composite Fabric, the ultralight stuff. He basically dismissed it even though he had actually read about it. Said it was too expensive.” Tom shook his head. “I tried to explain that the weight savings more than justify the cost on longer trips, but he didn’t want to hear it. Just kept saying it wasn’t for him. And then I asked him about carbon fiber poles and…”
Luis frowned slightly and jumped in, “Wait, you tried to explain it to him?”
“It would be better to say that I was trying to help him. These fabrics are a genuine breakthrough. I’ve been following the space for months.” Tom leaned back. “But he just shut down after that. One-word answers. I had to drag everything out of him. We’ll need to find better customers than him to interview.”
The room was quiet for a moment.
Jenna spoke carefully. “Tom, what were you hoping to learn from Derek?”
“Stuff for our project, of course. What backpackers want in a tent. What frustrates them. You know, like we’ve been saying.”
“And did you ask him that?”
Tom opened his mouth, then closed it. He looked down at his notebook. Two pages of notes, most of them about fabric weight and cost comparisons. He flipped forward. Then back.
“I think so. I mean, I thought I did,” he said, more slowly.
“What did you find out frustrates him?” Shelton asked.
Tom stared at the page for a moment. “I have something here somewhere. I can’t remember offhand.”
Shelton nodded, not unkindly. “Derek wasn’t giving you wrong answers,” he said. “He was giving you answers you weren’t expecting. Answers that didn’t seem right to you. And when that happened, you did less interviewing and more advising.”
Tom set the notebook down.
Shelton laughed before continuing, “Tom, you didn’t do anything wrong by getting started or by having some ideas. I mean, but no, that wasn’t a great interview performance. But still, I’m glad you had that experience.”
Tom explained, “I see what you mean by advising. I think you’re right. But why are you glad it happened?”
Shelton replied, “Because it’s time for a talk about our mental frame. And how to not accidentally sabotage these sessions.”
Shelton stood and turned to the whiteboard.
“What happened in that room has a name. And we all have to learn to manage it. All of us,” he said, and wrote two words.
Confirmation Bias.
The Mental Posture
Discovery interviews require a different orientation than most business conversations. In most professional contexts, the goal is to demonstrate knowledge, advance an argument, or persuade someone toward a conclusion. Discovery interviews invert this dynamic. The moderator’s job is to demonstrate curiosity, not expertise. The team’s job is to be attentive, not judgmental. The entire purpose of the session is to learn something the team did not already know.
This is harder than it sounds. Teams entering interviews with a pre-developed Job Success Criteria list and a job map already in hand have formed ideas about what they expect to hear. The pull toward confirmation, toward noticing what fits the existing framework and discounting what does not, is a cognitive tendency that operates below the level of conscious intention.
A moderator who believes setup speed is the most important issue in the backpacking tent market will, without intending to, ask more follow-up questions about setup speed than about other topics, spend more time on answers that confirm that belief, and remember those answers more vividly during synthesis.
The corrective is not to pretend that preconceived ideas don’t exist. They do exist, and they are useful. The corrective is to treat them explicitly as possibilities rather than conclusions. The discussion guide, the subject of a future chapter, is a structural tool for doing this. But the disposition must come first. A team that approaches interviews with genuine openness to being wrong will produce better discovery than a team that approaches them looking for confirmation, regardless of how well the guide is written.
The Moderator’s Orientation
Conducting a discovery interview well begins not with technique but with orientation, with how the moderator understands their role and what they are trying to accomplish.
The moderator’s role in discovery is the inverse of the expert role. The moderator is not the authority in the room; the customer is. The moderator’s job is not to demonstrate what they know but to uncover the customer’s experience. The questions should be simple, almost naive, because naive questions invite expansive answers. Silences should be tolerated, because silence gives the customer space to keep talking. The moderator’s reactions should be neutral, because neutral reactions do not indicate which answers are more welcome than others.
One nuance deserves attention here. Neutrality does not mean coldness. Many customers arrive at a discovery interview with quiet uncertainty: they are not sure whether their experience is relevant, whether they are speaking at the right level of detail, or whether what they have to say is useful at all. A moderator who responds to everything with silence or a blank expression can inadvertently suppress the very openness they are trying to create.
Small, carefully chosen encouragements, such as “that’s helpful” or “interesting,” serve a different purpose than substantive reactions. They are not a commentary on the content of what was said. They are signals that the customer is doing the right thing by talking, that the conversation is going well, and that they should keep going. Used sparingly and applied broadly rather than in response to specific answers, they help maintain the customer’s confidence and keep them in a talkative, exploratory state.
The risk is real, however. The same phrase that reassures a hesitant customer can also, if timed carelessly, signal that one answer was more welcome than another. The discipline is to offer encouragement in response to the act of sharing, not the substance of what was shared.
This orientation, curiosity combined with humility about what the team does not yet know, is the foundation on which every other moderating skill is built. Technique without this orientation produces technically competent conversations that nonetheless miss the most important things. Orientation without technique produces open conversations that fail to cover the right territory. Both are necessary. But orientation comes first.
Understanding Confirmation Bias
Confirmation bias is the tendency to notice, remember, and interpret information in ways that confirm what we already believe. It is not a character flaw or a sign of intellectual dishonesty; it is a fundamental feature of human cognition that affects everyone, including experienced researchers who are actively trying to avoid it.
Tom’s conversation with Derek is a clean illustration of how it operates. He entered the conversation with a strong view that ultralight fabrics represent a genuine breakthrough, and that view shaped everything that followed. He steered the conversation toward it, pushed back when Derek didn’t agree, and came away with two pages of notes that reflected his own beliefs more than Derek’s experience. Derek’s actual issues never surfaced. The conversation became frustrating for both.
The answers we did not expect are often the ones that teach us the most.
In discovery, confirmation bias operates through several distinct mechanisms that practitioners should be able to recognize and counter.
The first is selective questioning. Moderators who have strong notions tend to ask more follow-up questions in areas that confirm those hypotheses and fewer in areas that do not. A moderator convinced that fabric weight is the primary purchase driver will probe weight-related comments extensively and move quickly past comments about setup difficulty or overnight stability. The transcript will appear to confirm the hypothesis, not because the data supports it, but because the moderator created more data about weight than about anything else.
The second is selective noticing. Even when customers raise topics that contradict the team’s expectations, those topics register less vividly than topics that confirm them. A customer who mentions in passing that they have never once thought about tent weight because they care far more about how quickly it goes up will register less strongly in the moderator’s memory than a customer who confirms that weight matters. Confirming data feels significant. Disconfirming data feels like an outlier.
The third is selective interpretation. Ambiguous customer statements, which are most of them, tend to be interpreted in ways that fit preexisting ideas. When a customer says, “I want a tent that performs,” a moderator focused on weather protection will hear that as being about weather protection. A moderator focused on setup speed will hear it as being about setup speed. The statement supports whatever the moderator already believes.
The fourth is selective recall. When the team debriefs after a session, the comments that get remembered and repeated tend to be the ones that fit the prevailing ideas. The surprising or contradictory remarks, which are often the most analytically valuable, fade more quickly from memory and receive less airtime in the debrief.
Understanding these mechanisms is the first step toward countering them. Awareness alone does not eliminate confirmation bias, but it does create a productive skepticism: a habit of reflecting, when a pattern begins to emerge, on whether that pattern exists in the data or in the questions that produced it.
Practical Strategies
Because confirmation bias cannot be eliminated through good intentions alone, practitioners need a plan to counteract it during conversations and during synthesis.
The most powerful in-conversation strategy is to treat unexpected or contradictory responses as clues to something significant rather than anomalies. When a customer says something that does not fit the team’s hypotheses, the instinct is to move on, to note it briefly and return to more familiar territory.
The disciplined response is the opposite: pause, probe, and seek to understand. What exactly did the customer mean? In what context does this arise? How important is it relative to other things they have described? The unexpected response may be an outlier. It may also be the most important thing said in the session. The moderator cannot know which until it has been explored.
A second strategy is to structure the discussion guide so that the customer’s unprompted commentary is captured before the moderator’s hypotheses can shape the conversation. Chapter 12 addresses this in detail, but the principle is simple: ask open, broad questions first and let the customer determine what is worth discussing before introducing any specific topics.
A third strategy is to rotate moderators across sessions when the team has more than one person capable of leading interviews. Different moderators have different assumptions and different attentional biases. A pattern that appears consistently across sessions led by different moderators is more likely to reflect something real in the data than a pattern that appears only in sessions led by the same person.
A fourth strategy is to compare independent observations during the debrief before group discussion begins. The debrief, covered as a logistics practice in Chapter 9, is also one of the most effective defenses against selective recall.
Body Language and Non-Verbal Signals
Confirmation bias does not operate only through questions and verbal responses. It also works through body language. And customers are highly attuned to non-verbal signals about which answers are welcome.
A moderator who leans forward slightly when a customer mentions a particular topic, raises their eyebrows when a specific concern comes up, or nods more enthusiastically in response to certain answers is signaling interest, which encourages the customer to provide more of what triggered the signal. The reverse is equally true: a moderator who glances at their notes, shifts in their seat, or responds with shorter follow-ups when a topic does not align with their expectations signals disinterest, which discourages the customer from pursuing that direction.
These signals are largely unconscious on both sides. The moderator is not deliberately communicating preference, and the customer is not consciously adjusting their responses. But the dynamic is real, and its effects on the data are meaningful.
The practical discipline is to maintain consistent body language across all responses, the same level of attentiveness, the same quality of eye contact, the same pace of follow-up, regardless of whether the customer is saying something expected or unexpected, confirming or contradicting.
This is not about being expressionless or clinical. Warmth and genuine interest are entirely compatible with consistency. The goal is to be equally interested in everything the customer says, which is the appropriate orientation for discovery. Every response is valuable, and the ones that feel least relevant in the moment could ultimately be the most important.
In remote (web conference) interviews, the same principle applies. Camera presence, facial expressions, and response timing are all visible to the customer and carry the same signaling risk as in-person body language.
What Comes Next
The practical foundation is now in place, and so is the mental frame that makes it useful. Two things are both true: the team has done real preparation, and that work has inevitably produced assumptions. The work from here is to hold those theories lightly, using them as a starting point for curiosity rather than a destination to confirm.
The next task is to return to the Market Lens and refine who to talk to. A sample plan that is thoughtfully built, one that reflects the range of customers whose experiences define the market, is what ensures that the mental frame developed here gets applied to the right conversations. That is the subject of the next chapter.
Key Takeaways
· Confirmation bias is not a character flaw. It is a feature of human cognition that affects everyone. Confirmation bias operates through selective questioning, selective noticing, selective interpretation, and selective recall. Understanding the mechanisms is the first step toward countering them.
· The moderator’s role is the opposite of the expert role. The goal is not to demonstrate knowledge, advance an argument, or steer toward a conclusion. The goal is to be curious about the customer’s experience.
· Unexpected or contradictory customer responses are evidence, not anomalies. When a customer says something that does not fit the team’s presumptions, the disciplined response is to pause, probe, and understand, not to move on.
· Hypotheses formed during preparation are useful starting points, not destinations to confirm. The team should enter every conversation aware of its presuppositions and deliberately hold them loosely, using them to know what to listen for rather than what to find.
· Structural defenses against confirmation bias, such as open-ended questions before specific ones, independent debrief notes before group discussion, and rotated moderators across sessions, are more reliable than good intentions alone. The guide and the debrief process are tools for keeping bias from corrupting the research.
This has been a sample chapter from DISCOVER: From Customer Noise to Product Signal, A Jobs-to-be-Done Guide to Customer Interviews and Product Insight, available on Amazon.