Case Study 2: The Quality of Your Questions Determines the Quality of What You Learn

Edgar Schein and the Radical Act of Not Telling

Introduction: A Question as a Relationship

Edgar Schein spent most of his career at MIT's Sloan School of Management studying something that seems, on the surface, straightforward: how do people in organizations actually communicate? What does it mean to truly help someone? What distinguishes an expert giving advice from someone genuinely supporting another person's thinking?

His conclusions, articulated most directly in Humble Inquiry: The Gentle Art of Asking Instead of Telling (2013), are both simple and — in a culture saturated with advice-giving, positioning, and assertion — genuinely radical. The core claim: in most of the situations we call "helping" or "conflict" or "feedback," we are telling far too much and asking far too little. And what we lose when we tell is not just information — we lose the relationship itself.

Schein opens the book with an observation that cuts to the heart of everything this chapter has argued: "I define Humble Inquiry as the fine art of drawing someone out, of asking questions to which you do not know the answer, of building a relationship based on curiosity and interest in the other person." (Schein, 2013, p. 2)

Notice what is packed into that sentence. Humble inquiry is a fine art — which means it can be practiced poorly or well, and that getting it right requires genuine skill. It involves drawing someone out — a spatial metaphor that implies the other person's perspective is inside them, needing to be brought to the surface rather than overwritten. It is asking questions to which you do not know the answer — which is the litmus test we've argued throughout this chapter for genuine questioning. And it builds a relationship — not just an exchange of information, but an ongoing structure of trust and reciprocity.

The implications of humble inquiry for conflict — for difficult conversations specifically — are profound and practical. This case study explores Schein's framework in depth, examines the four types of inquiry he distinguishes, and applies them concretely to the conflicts you are likely to face.

The Cultural Problem: Why We Tell Instead of Ask

Schein argues that Western cultures, and particularly American professional culture, have a profound bias toward telling. This bias is so deep that we barely notice it. Telling is how we demonstrate competence. Telling is how we establish authority. Telling is how we show we've done our homework, that we have a perspective worth having, that we belong in the conversation.

"We are biased toward telling," Schein writes, "because we live in a pragmatic, problem-solving culture in which knowing things and being able to tell others what we know is valued." (Schein, 2013, p. 4)

In this cultural frame, asking — especially asking from a position of genuine not-knowing — can feel like a threat to status. It can seem like weakness. It implies that you don't already know. In most professional contexts, not knowing is something to hide.

But Schein flips this entirely. In his view, the willingness to ask from genuine not-knowing — the willingness to prioritize your curiosity about the other person's experience over your own need to demonstrate knowledge — is not weakness. It is a form of relational respect that is, in most contexts, far more powerful and productive than assertion.

The connection to conflict is immediate. When we enter a conflict conversation, we typically arrive loaded with conclusions: about what happened, about what the other person intended, about what the problem is, about what needs to change. We are ready to tell. The other person is also ready to tell. Two people in telling-mode face each other, and the conversation becomes a collision of competing assertions — with no one in the room actually asking.

Schein's intervention is to create a third option: what if, before you told anything, you asked?

The Four Types of Inquiry

Schein's most analytically useful contribution is his taxonomy of inquiry types. He distinguishes four forms of questioning, arranged on a spectrum from most to least open:

1. Pure Inquiry

Pure inquiry is asking only what you genuinely don't know — with no agenda, no frame, no interpretive overlay. It is the most open form of inquiry, and the most demanding, because it requires the asker to hold their own perspective entirely in abeyance while the other person speaks.

"What is going on?" is pure inquiry. "Tell me what happened from your perspective" is pure inquiry. "What's been on your mind?" is pure inquiry. The defining feature: the asker has no pre-existing interpretation they are testing. They are simply creating a space and waiting to see what fills it.

In conflict contexts, pure inquiry at the opening of a conversation sends a powerful signal: I have not already decided what happened. I am here to find out. This is simultaneously rare and disarming. Most people enter conflict braced for assertion. Pure inquiry interrupts the pattern before it starts.

The limits of pure inquiry are real, however. It is not always appropriate to present as a complete blank — in some conflict contexts, pure inquiry can feel evasive or even passive-aggressive. ("What do you mean, 'what happened' — you know what happened.") And there are moments in conflict where you need to share your own perspective and not just ask. Schein does not argue that pure inquiry should replace all other modes — only that it should be the starting point far more often than it is.

2. Diagnostic Inquiry

Diagnostic inquiry is asking within your own frame. You have a hypothesis — a theory about what's happening — and your questions are shaped by that hypothesis, even if they're still genuinely open.

If a manager suspects a performance problem is caused by workload, they might ask: "What does your week typically look like right now? How are you balancing the different projects?" These are open questions, but they're oriented by the manager's suspicion. The manager is not purely open to any answer — they are exploring a specific territory.

Diagnostic inquiry is not inherently problematic. Hypothesis-testing is how we move from pure exploration to useful understanding. The diagnostic questions Priya Okafor asks of her residents can be valuable — she is, after all, diagnosing something. The problem arises when diagnostic inquiry is mistaken for pure inquiry — when the asker believes they are being open while actually only asking about the territory they've already decided matters.

In conflict, diagnostic inquiry looks like this: "Help me understand what happened with the deadline — was it a resourcing issue or a planning issue?" The asker is genuinely curious, but has pre-sorted the possible answers into two categories. If the answer is neither — if it was a communication issue, or a priority conflict — the diagnostic question may not leave room for that.

The key discipline in diagnostic inquiry is to hold your hypothesis loosely and remain genuinely open to answers that don't fit it.

3. Confrontive Inquiry

Confrontive inquiry is asking in a way that actively challenges the other person's frame. It introduces your perspective into the question itself and invites the other person to grapple with it.

"I've been noticing that this has happened three times in a row — what do you think is behind that pattern?" is confrontive inquiry. It names your interpretation (there's a pattern; it's meaningful) and asks the other person to engage with it. It is still a question — it is still asking for the other person's response — but it is no longer presenting as neutral or empty.

Confrontive inquiry, used skillfully, can be a powerful tool in conflict. It allows you to introduce your perspective without asserting it as fact, and to invite the other person to respond to it rather than simply defend against it. The difference between "You're repeating the same pattern" (assertion) and "I've noticed this has happened three times — what do you make of that?" (confrontive inquiry) is significant. The second keeps the conversation open while still putting your observation on the table.

The risk of confrontive inquiry is that it can slide into manipulation or coercion — using question form to pressure the other person toward your conclusion. This is the line between Schein's confrontive inquiry and Dr. Priya's leading questions: Priya's questions are confrontive in form but coercive in intent. She is not genuinely asking what the resident makes of the pattern. She is using question form to make the resident admit it.

Confrontive inquiry requires genuine openness to the other person's response, even when the response is unexpected or unwelcome.

4. Process Inquiry

Process inquiry is asking about the conversation itself — about how the exchange is going, what is and isn't working, what needs to shift in the conversation for it to be productive.

"I'm noticing we keep coming back to the same point. What do you think is keeping us stuck there?" is process inquiry. "Is this conversation feeling useful to you?" is process inquiry. "What would need to be different about this conversation for it to feel like we're making progress?" is process inquiry.

Process inquiry is the meta-level of the conversation — stepping back from the content to ask about the container. In conflict, it is often the most underused tool. When a conversation is cycling, or escalating, or going silent, most people try to solve the content problem harder. Process inquiry steps back and asks about the conversation itself.

Schein argues that process inquiry is, in many ways, the most honest form of inquiry available — because it acknowledges that the quality of the conversation matters, that what's happening between people in a conflict is not just about the content but about the interaction structure.

Humble vs. Defensive Inquiry: The Crucial Distinction

Schein's most important contribution for conflict practitioners may be his distinction between humble inquiry and what we might call defensive inquiry — questioning that appears curious but is actually protective.

Humble inquiry, in Schein's terms, is characterized by: - Genuine curiosity about the other person's experience - Willingness to have your own view changed by what you hear - Interest in the person, not just the information - Comfort with not knowing — with being in the open space

Defensive inquiry, by contrast, is questioning that serves the asker's own emotional needs rather than genuine exploration: - Asking questions to buy time before asserting your own position - Asking questions to appear open while remaining closed - Asking questions that you hope will trap the other person in a contradiction - Asking questions to gather ammunition for a response you've already prepared

The distinction is internal, and it is precisely this interiority that makes the practice difficult. You can ask textbook-correct questions in textbook-correct sequence while operating entirely in defensive inquiry mode — and the other person will usually know. Not necessarily consciously, but bodily: they'll feel the inauthenticity of your attention. They'll answer your questions with a guardedness that mirrors your own.

This is why Schein's framework is ultimately not about technique. It's about orientation. The techniques — open questions, funnel structure, "and what else" — are only as good as the genuine curiosity that drives them. The techniques without the orientation produce better-sounding defensive inquiry. The orientation produces genuine connection, even with imperfect technique.

Application to Conflict: Three Principles

Schein's framework suggests three operational principles for questioning in conflict:

Principle 1: Start with Pure Inquiry Before Moving to Diagnostic

Whatever your hypothesis about what's happening in the conflict — and you will have a hypothesis — hold it in reserve. Begin with a question that is as close to pure inquiry as you can manage: "What's your experience of this situation?" or "What's been most difficult about this for you?" Let the other person define the territory before you introduce your own framing.

This is difficult. You came in with a view. But the discipline of beginning in pure inquiry gives you something invaluable: you learn what the other person actually thinks before you've contaminated the space with your own interpretation. You may learn something that changes your hypothesis entirely. Or you may confirm your hypothesis — but now with the other person's own words as evidence, rather than with your assumption. Either outcome is better than diagnostic-first.

Principle 2: Hold Your Confrontive Questions Until You've Earned the Right to Them

Confrontive inquiry — introducing your interpretation and asking the other person to engage with it — is most effective after you've demonstrated genuine curiosity about their experience. If the first question you ask is confrontive, the other person has no reason to believe you're genuinely open. You haven't yet established that you're listening, or that their perspective matters.

Earn the right to confrontive inquiry by demonstrating that you've heard, understood, and taken seriously what the other person has said. Then, from that foundation of demonstrated respect, you can introduce your perspective as a question: "Given what you've shared — what do you make of the fact that this has happened three times?"

Principle 3: Use Process Inquiry When You're Stuck

When the conversation is cycling, or one or both parties are becoming defensive, the content of the conflict is usually not the most useful place to intervene. Process inquiry — "What's happening in this conversation that's keeping us stuck?" — steps outside the content and invites both parties to look at the exchange itself. This move is often surprisingly effective: it interrupts the pattern, acknowledges something real (the conversation isn't working), and invites collaborative problem-solving about the process before returning to the content.

What Humble Inquiry Looks Like in Conflict: A Contrast

To make the abstract concrete, consider two versions of the same opening to a conflict conversation. A manager is about to address a team member who has been increasingly withdrawn and uncommunicative in meetings.

Defensive Inquiry Version:

"I've noticed you haven't been participating much in our team meetings lately. Is everything okay at home? Are you having trouble with the work? I want to make sure you're not falling behind."

The questions here are technically questions. But they are organized entirely around the manager's frame — and they are loaded with assumptions. "Is everything okay at home?" assumes the problem is personal. "Are you having trouble with the work?" assumes incompetence might be the issue. "I want to make sure you're not falling behind" reveals the real anxiety — the manager is worried about a performance problem, and these questions are probing for confirmation. The employee, sensing this, will likely respond defensively or minimally.

Humble Inquiry Version:

"I've noticed things seem a bit different for you in our team meetings lately. I realized I haven't asked about it directly, so I wanted to. What's been going on for you?"

This version names the observation specifically but non-judgmentally ("things seem a bit different"). It acknowledges the manager's own gap ("I realized I haven't asked about it directly"). And then it opens entirely — "What's been going on for you?" is pure inquiry. It makes no assumptions about the category of the problem. The employee has genuine room to define the territory.

The humble inquiry version may surface information the defensive inquiry version never would — including, possibly, that the employee is frustrated with the manager's own behavior, or with team dynamics, or with a structural problem the manager hasn't noticed. The defensive inquiry version makes those answers nearly impossible, because it has already organized the space around the manager's hypotheses.

The Deeper Claim: Asking Is a Form of Respect

Schein makes a point that is easy to miss in the practical focus on technique. The choice to ask rather than tell is not just strategically better in most conflict contexts — it is ethically significant. It reflects a fundamental stance about the other person.

When you tell, you are positioning yourself as the one who knows. The other person becomes the recipient of your knowledge — or the subject of your correction. The relationship is inherently hierarchical in that moment, even if you don't intend it to be.

When you ask from genuine curiosity, you are positioning the other person as the one whose experience matters, whose perspective you want, whose inner life you don't already know. This is a form of respect that is, in conflict especially, deeply rare — and deeply felt.

Schein puts it simply: "Humble Inquiry favors curiosity and exploration over immediate diagnosis and solution, favors the relationship and the long run over immediate efficiency and short-term task accomplishment." (Schein, 2013, p. 12)

This is the trade-off. Humble inquiry is slower in the short term — it requires patience, genuine listening, and comfort with not knowing. But in the long run, it produces something that efficient telling never can: a relationship in which the other person believes, on the basis of experience, that you actually want to understand them. That belief changes everything — what they tell you, how they respond to your input, how they feel about the relationship, and ultimately whether the conflict actually gets resolved.

Implications for Practice

Schein's humble inquiry framework is not a technique to be deployed. It is an ongoing practice — something that requires regular cultivation and regular honest assessment of whether you're actually in humble inquiry or have slipped into its defensive imitation.

Some practical markers to help you assess:

You are probably in humble inquiry when: - You are surprised by what you hear — it's new information, not confirmation of what you expected - The other person seems to relax over the course of the conversation - You find yourself genuinely uncertain about what to say next, because you're actually thinking about what you just heard - The conversation goes in a direction you didn't anticipate

You are probably in defensive inquiry when: - Every answer the other person gives confirms what you already believed - You are mainly waiting for the other person to finish so you can make your point - You feel impatient when their answer goes in an unexpected direction - The other person becomes more guarded as the conversation continues

The distinction is real, and it matters. Not just for the other person — for you. Genuine curiosity is a different cognitive and emotional state than strategic questioning. In genuine curiosity, you are genuinely engaged. The conversation is interesting to you because you don't know where it's going. In defensive inquiry, you already know where it's going — you're just going through the motions.

The challenge that Schein poses — the challenge that this entire chapter poses — is whether you are willing to actually not know, for long enough to find out.

Reflection Questions

Schein argues that Western professional culture is biased toward telling. In your own experience — professional, academic, or personal — where do you see this bias most strongly? Where has it caused problems in your conflicts?
The distinction between humble inquiry and defensive inquiry is internal: it's about your actual orientation, not your question technique. What internal conditions make humble inquiry difficult for you personally? What makes it easier?
Think of a conflict in which you used what turned out to be diagnostic inquiry — you were asking, but within your own frame. What did you miss? What might pure inquiry have surfaced?
Schein argues that asking is a form of respect. Do you agree? Are there contexts in which asking could be a form of disrespect — and if so, what distinguishes them?
Process inquiry — asking about the conversation itself — is the most underused inquiry type in most people's repertoires. What makes it uncomfortable to use? What might make it easier?

Sources Referenced

Schein, E. H. (2013). Humble inquiry: The gentle art of asking instead of telling. Berrett-Koehler.

de Shazer, S., & Berg, I. K. (1997). "What works?" — Remarks on research aspects of solution-focused brief therapy. Journal of Family Therapy, 19(2), 121–124.

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.