Picture your last team meeting. Someone shares an idea. What happens next?
If your team is like most, people respond in one of two ways. They judge it (“That won’t work because…”) or they interrogate it (“Why would we do that?”). Both feel productive. Neither is.
What’s missing is dialogue. Not discussion, not debate. Dialogue. The kind of conversation where new thinking emerges that nobody walked in with.
David Bohm, the physicist who spent decades studying how groups think, drew a sharp line between the two. Discussion shares a root with “percussion” and “concussion.” It’s ideas being batted back and forth. Someone wins, someone loses. Dialogue comes from the Greek dialogos. Dia means “through.” Logos means “meaning.” A stream of meaning flowing through a group, not between opposing sides.
Most meetings are discussions disguised as collaboration. Everyone’s listening, but they’re listening for their turn to respond. Narrative dialogue is the practice that breaks that pattern.
What Narrative Dialogue Actually Is
Narrative dialogue is the broader practice of using questions that invite stories instead of justifications. It draws on three core techniques:
- Replace “why” with “how” and “what”
- Loop for understanding instead of leading
- Suspend your verdict
None of these are complicated. All of them are hard. Because they require you to give up the thing most professionals are trained to do: demonstrate expertise by having answers.
Technique 1: Replace “Why” with “How” and “What”
Larry King once reflected on what carried him through over 60,000 interviews: “I asked good questions, I listened, and I followed up.” His secret was almost comically simple. He started with basic questions and he was, in his own words, “insanely curious” about people.
But the type of question matters enormously.
“Why did you negotiate with them?” demands justification. It puts someone on defense. “How did you come to the decision to negotiate?” invites the story. When King asked Mandela the second version, he got one of the most profound answers in broadcast history, about prisoners preparing themselves for freedom long before it arrived.
There’s neuroscience behind this. Angus Fletcher, a professor at Ohio State who studies narrative cognition, describes an exercise called “Delay the Why.” Instead of asking someone why they do something, you ask: Who do you do it with? Where did you first try it? What do you use? When did someone introduce you to it? You gather every detail except the motive. Then you hypothesize the why from the story.
The result is almost always richer than what a direct “why” would produce. Fletcher’s research shows that “why” pushes people toward logical abstraction. Labels. Categories. Things that feel like answers but strip out meaning. “How” and “what” keep people in narrative mode, where empathy, perspective-shifting, and creativity live.
Harvard Business Review confirmed this from a different angle. Organizational psychologist Tasha Eurich found that “why” is a surprisingly ineffective question even when we ask it of ourselves. We don’t have access to most of our unconscious motivations, so we invent answers that feel true but often aren’t. “What” questions keep us objective and forward-looking. “What happened?” beats “Why did this happen?” every time.
Here’s what this looks like in practice.
I run workshops where I ask someone to describe a colleague in one word. In one session, a participant said “people pleaser.” The room immediately filled in the meaning: pushover, can’t say no, wants approval.
Then I asked the group to tell the story behind the label. The actual person was a luxury tour guide who deeply personalizes experiences for guests. Repeat requests. Glowing reviews. The drive to please wasn’t weakness. It was craftsmanship.
Same label. Completely different meaning. The word “people pleaser” was logical classification. The story was narrative understanding. You cannot get from one to the other with “why.” You need “tell me about a time when…”
Technique 2: Loop, Don’t Lead
Most people think good conversation means asking great follow-up questions. That’s partly true. But the pressure to formulate the next question creates its own problem: you stop listening to the current answer.
Looping for understanding solves this. The technique is simple:
- Listen to what someone says
- Paraphrase it back in your own words
- Ask: “Do I have that right?”
That’s it.
Charles Duhigg, in his book Supercommunicators, found that the most effective communicators in group settings asked 10 to 20 times more questions than the average person. But more importantly, they repeated what others said. The repetition wasn’t filler. It was proof of listening.
Looping works because the correction is where the gold lives. When someone says “Actually, it’s more like…” they’re giving you information that a follow-up question would never have reached.
Example. A prospect says: “We need our ICs to communicate better.”
You could ask: “What does better communication look like?” That’s a decent question.
Or you could loop: “So the challenge is that individual contributors aren’t influencing stakeholders effectively. Do I have that right?”
The response: “Yes, but it’s more specific than that. They’re great with their direct teams, but cross-functional is where it breaks down.”
The loop didn’t just narrow the problem. It surfaced a distinction the prospect may not have articulated before. Ursula K. Le Guin captured this well: “Listening is not a reaction, it is a connection. Listening to a conversation or a story, we don’t so much respond as join in.”
Technique 3: Suspend Your Verdict
This is the hardest one.
Bohm identified three conditions necessary for dialogue. The first: participants must “suspend” their assumptions. Not suppress them. Not pretend they don’t exist. Hold them in front of you and examine them, the way you’d hold a snow globe up to the light.
Most people skip this step because it feels unproductive. In a world that rewards quick answers and decisive action, pausing to examine your own assumptions seems like a luxury.
It’s not.
Fletcher’s research in Wonderworks found that the longer we suspend our judgments, the more accurate our subsequent verdicts become. This isn’t about being indecisive. It’s about giving your brain time to process new information before locking in a position.
The practical application: notice the moment in a conversation when you form your opinion. That’s the moment to get curious. Not because your opinion is wrong, but because it’s incomplete. The opinion is a leaf floating on the surface. The stream of thinking beneath it is where dialogue lives.
Peter Senge, drawing on Bohm’s work in The Fifth Discipline, described what happens when teams actually practice this: “People become observers of their own thinking.” That’s the shift. You go from being consumed by your thoughts to watching them. And from that vantage point, you can choose which ones to voice and which ones to hold up for examination. (For a deeper dive on the Fifth Discipline, check out my book summary).
Try This Week
Pick one conversation this week. A 1:1, a team meeting, a discovery call. Set one rule for yourself:
No “why” questions. Only “how” and “what.”
- Instead of “Why do you think that?” try “How did you arrive at that?”
- Instead of “Why didn’t that work?” try “What happened when you tried it?”
- Instead of “Why is this a priority?” try “How does this connect to what matters most right now?”
Then loop once. Paraphrase what you heard and ask “Do I have that right?”
Notice what happens. The conversation will slow down slightly. The other person will say more. And you’ll learn something you wouldn’t have learned any other way.
That’s narrative dialogue.