Case Study 1: Sam's One Good Question

Background

Sam Nguyen has been an operations manager at a regional logistics company for six years. Sam is organized, process-driven, and deeply committed to meeting standards. On Sam's team, standards are not abstract — they translate directly into client commitments, shipping timelines, and contractual obligations. When something slips, real things downstream get affected.

Tyler joined Sam's team fourteen months ago. He came in with strong references, navigated the onboarding well, and for the first six months appeared to be on track. Then something shifted. Over the last three months, Tyler has missed three project deadlines — not by catastrophic amounts, but enough to create ripple effects. The first time, Sam let it go with a brief reminder about expectations. The second time, Sam sat Tyler down and delivered a clear, direct speech about the standards. Tyler nodded, said he understood, and missed the next deadline anyway.

Now it's the third time. Sam is frustrated. The team has had to compensate. Sam's manager has noticed. And Sam has been cycling through the same internal monologue: Tyler knows the standard. I've told him the standard twice. What more is there to say?

What Sam has not asked is: What don't I know about Tyler's situation?

The Setup: What Sam Usually Does

Before we watch what Sam does differently, it's worth being clear about what Sam's usual approach looks like. Sam is a good manager by most metrics — fair, consistent, organized. But Sam's management style is fundamentally directive. Sam identifies problems, names standards, explains consequences, requests commitments.

This works. Most of the time. For most employees. In most situations.

What this approach cannot do is surface information Sam doesn't have. Every time Sam talks to Tyler, Sam delivers a speech that Tyler has already heard. And every time Tyler nods and says "I understand," Sam does not ask: What is Tyler understanding? What is Tyler experiencing? What does Tyler see when he looks at this situation?

A colleague — another manager Sam respects — recently asked Sam a pointed question: "Have you ever actually asked Tyler what's getting in the way?" Sam paused. No. Sam hadn't. Sam had told Tyler what the standard was, what the consequence was, and what commitment Sam needed. Sam had never asked Tyler a genuine question about the situation at all.

That pause was the beginning of a change.

The Preparation: Three Questions Before the Conversation

Sam works through the pre-confrontation checklist from the Curious Confronter model.

Question 1: What do I think I know, and how confident am I?

I know Tyler has missed three deadlines. I know I've addressed this twice. I know the standard is clear. What I don't know: whether Tyler actually understands why this is a problem (vs. whether he's just nodding), what Tyler's internal experience of these deadlines is, whether something has changed in Tyler's workload or life, and whether Tyler feels like he can come to me when he's struggling.

Question 2: What am I actually afraid of?

Honestly? I'm afraid I have a bigger problem than I think. I'm afraid that Tyler is either fundamentally struggling in a way that requires formal action, or that I've created conditions where he can't come to me with problems. Either outcome is uncomfortable. It's easier to deliver another speech about the standard — that way I've done my job and the ball is in Tyler's court.

Question 3: What do I genuinely not know that I need to find out?

Why is this happening. Not as an accusation — as a genuine question. Three misses in the same kind of pattern is not random. Something is happening. I don't know what it is.

Sam writes down one question to lead with: "Tyler, what's getting in the way?"

Then Sam pauses. That's a little abrupt. Sam wants to name the observation first, signal genuine curiosity, and then ask. Sam revises:

"Tyler, I've noticed the last three deadlines have been late, and I'm genuinely trying to understand what's happening for you. What's getting in the way?"

Sam reads it back. It's direct. It names the pattern without burying it. And then — instead of asserting what the problem is or what Tyler needs to do — it opens the floor.

Sam prints it out and reads it twice before the meeting.

The Conversation

Sam's office. A Tuesday afternoon. Tyler sits down looking like someone who expects another speech. His body language is already slightly defensive — shoulders slightly in, hands folded, gaze a half-degree past Sam's face rather than at it.

SAM: Tyler, thanks for coming in. I want to talk about the last few deadlines — and I want to approach it differently than I have before. I've addressed the missed deadlines twice, and I don't think another reminder about the standard is going to help. So I want to actually try to understand what's going on. (pause) Tyler, I've noticed the last three deadlines have been late. I'm genuinely trying to understand what's happening for you. What's getting in the way?

A pause. Tyler looks slightly surprised — he was clearly ready for a different kind of conversation.

TYLER: I mean... I've been really overwhelmed lately. There's a lot going on.

Sam's instinct, here, is to say: Everyone's overwhelmed, Tyler. Or: The standard doesn't change based on how busy we are. This is the moment where most directive managers close the funnel prematurely. Instead, Sam thinks: And what else?

SAM: What's been most overwhelming? Help me understand what "a lot" looks like from your end.

Another pause. Tyler shifts in his chair.

TYLER: Honestly? It's the competing requests. When you assign me a deadline, I'm tracking that. But I'm also getting pull-requests from the Hendricks account team, and from Martinez's group, and sometimes from your direct reports. And none of them know what the others have assigned me. So I'm managing — I don't know — four or five overlapping timelines, and sometimes things fall through.

Sam sits with this.

TYLER: (continuing, slightly faster now) And I didn't want to say anything because I was worried it would look like I couldn't handle the workload. Like I was complaining.

Sam processes this. There is something important here that Sam has not heard before. Not because Tyler was hiding it exactly — but because Sam had never created the conditions for it to be said.

SAM: So the deadlines I set with you — you're tracking those. But you're also fielding requests from teams that I may not have visibility into?

TYLER: Yeah. And sometimes those are urgent too, or people act like they are, and I don't — I guess I didn't know how to triage that.

SAM: And you felt like you couldn't bring that to me because you thought it would look like you were complaining or couldn't handle the workload.

TYLER: (quietly) Yeah.

SAM: That's — Tyler, that's really important information. And I want to name something: the fact that you didn't feel like you could bring it to me is at least partly on me. I've delivered two speeches about the standard. I've never asked you what was making it hard to meet. That's a gap in how I've been managing this.

Tyler looks up, visibly recalibrating. This is not the conversation he came in expecting.

SAM: Can I ask you something else?

TYLER: Sure.

SAM: If I were going to fix one thing about how I've been managing your workload — what would actually help most?

TYLER: (genuinely thinking) Honestly? If I knew what my real priority list was — like, what you need from me first, above everything else — I could make better decisions about what to defer or push back on with the other teams.

SAM: So a clearer priority structure.

TYLER: Yeah. And maybe — I don't know, some sense that it's okay to tell someone their request has to wait.

SAM: You don't feel like you have permission to push back on other teams?

TYLER: Not really. They outrank me.

This is the fourth piece of new information Sam has received in ten minutes. The picture is becoming clear. Tyler is not cavalier about deadlines. Tyler is not struggling with competence. Tyler is navigating a chaotic cross-functional request environment without clear priority guidance, without an established escalation path, and without the confidence that he can push back on senior colleagues — and he has been too anxious about Sam's perception to say so.

SAM: Okay. Here's what I want to do. I want to set up a clear priority stack with you — what I need from you first, in order. And I want to establish that you can use my name when you push back on other teams: "Sam's project has to come first." You have that permission. We can formalize it if you need to.

TYLER: That would actually — yeah. That would help a lot.

SAM: I also want to set up a brief weekly check-in. Not to monitor you — but to give you a place where you can tell me if the competing requests are becoming unmanageable. I'd rather know on Tuesday than find out the deadline was missed on Friday.

TYLER: Okay. Yeah. I can do that.

SAM: (after a beat) Tyler — is there anything else that I should know about what's been making this hard?

TYLER: (shaking his head, but more relaxed) No. I think — this actually helps. I feel like I can breathe a little.

Analysis: What the Question Did That the Speech Could Not

Sam has now had ten minutes of conversation with Tyler that produced more usable information than two years of corrective feedback. Let's examine exactly what happened — and why the question made the difference.

Information That Was Invisible Before

The speech — "Here is the standard; here is the consequence; here is the commitment I need" — contains no space for new information. It is a closed circuit. Tyler receives it, confirms receipt, and leaves. The speech cannot surface what Tyler was experiencing, what structural factors were making the deadline hard, or what Tyler needed that Sam wasn't providing.

The question — "What's getting in the way?" — opened a space that Sam had never opened before. What came out:

1. Tyler was managing competing priority requests from multiple teams simultaneously
2. The requestors had no visibility into each other's demands
3. Tyler had no clear priority structure to help him triage
4. Tyler had no permission (formal or cultural) to push back on senior colleagues
5. Tyler felt he couldn't admit this to Sam without looking incompetent

None of this was accessible to Sam through the corrective speech route. Not because Tyler was hiding it, but because the conversation structure that Sam had always used literally could not carry that information. A speech leaves no room for new data. A genuine question creates the room.

The Role of "And What Else"

Notice that Sam used a version of Bungay Stanier's most powerful question — "Help me understand what 'a lot' looks like from your end" — when Tyler's first answer was vague. This moved the conversation from a surface-level "I've been overwhelmed" to the specific structural factors underneath. The first answer is almost never the complete answer. Pressing gently for more — with genuine curiosity, not interrogation — is where the real picture emerges.

The Role of Tone

Sam did not ask a genuine question and then sit back with crossed arms. The tone throughout was collaborative — Sam was genuinely trying to understand. Tyler picked this up. His body language changed noticeably through the conversation. By the end, he was leaning slightly forward. He was speaking faster. He used the phrase "I can breathe a little."

This is the de-escalation effect of genuine inquiry. Tyler came in braced for a verdict. He left with a workable plan and a sense that his experience had been heard. That shift — from threat to safety — is the physiological prerequisite for the kind of honest exchange that just happened.

What Sam Had to Let Go Of

To ask that question — and to wait for the answer — Sam had to let go of several things:

Certainty. Sam had already formed a conclusion: Tyler knows the standard and is not meeting it. The question required Sam to be genuinely open to other explanations. This was uncomfortable.

Control of the direction. When you ask an open question in conflict, you don't know where the answer will go. Tyler's answer went into cross-functional politics and organizational structure — territory Sam hadn't anticipated. Sam had to follow it there rather than redirect back to the prepared agenda.

The comfort of one-way communication. Delivering a speech is emotionally safer than asking a genuine question. A speech puts the work on the other person. A question puts you in a position of genuine uncertainty.

Each of these is a real cost. And Sam chose to pay them — because the previous approach clearly wasn't working.

What Happened Next

In the weeks following this conversation, three things changed:

Tyler's deadlines improved. Not immediately, and not perfectly — but substantially. Having a clear priority list, and explicit permission to defer competing requests, removed the primary structural barrier that had been causing the misses.

Tyler started proactively flagging problems. Instead of waiting until a deadline was missed and then saying nothing, Tyler began sending Sam brief messages mid-week: "The Hendricks team just added something urgent — I'm going to need to push back on your Friday deadline. Is that workable?" This was exactly the escalation behavior Sam had wanted but never created conditions for.

Sam's relationship with Tyler changed. Tyler began to see Sam as a manager who asked before assuming — and that changed what Tyler brought to Sam, and how much Tyler invested in the work.

One conversation. One question. Not magic. But the lever was in a completely different place than Sam had been looking.

Reflection Questions

1. What specific structural barrier was making it impossible for Tyler to raise his concerns under Sam's previous approach? How did the question create a condition where the barrier could be named?

2. Sam prepared the opening question in advance. What does this suggest about genuine curiosity — is it spontaneous, or can it be intentionally cultivated?

3. At several points in the conversation, Sam felt the impulse to redirect Tyler back toward the standard. Sam resisted. What do you think made that resistance possible? What might have happened if Sam had not resisted?

4. The chapter argues that "one good question can replace three minutes of explaining." In Sam's case, what was the equivalent exchange? What did one question produce that two years of corrective feedback had not?

5. Sam said, "The fact that you didn't feel like you could bring it to me is at least partly on me." How does this acknowledgment function in the conversation? Is this an example of the curiosity pivot? Why or why not?

Application

Before your next difficult conversation in a professional context, write down:

1. One wide, open question you will use to open the conversation — before you deliver any position or correction of your own.
2. One "and what else?" or equivalent follow-up question for when the first answer feels incomplete.
3. One thing you are prepared to learn that might change your current understanding of the situation.

The last item is the most important. If there's nothing you can imagine learning that would change your view, the question you're planning to ask may not be as genuine as you think.