Humble Inquiry: The Gentle Art of Asking Instead of Telling: Summary
Edgar H. Schein, the MIT organizational psychologist, argues that a culture of telling, especially from bosses to the people below them, quietly breaks the trust that safe and effective work depends on. He defines Humble Inquiry as asking questions to which you do not already know the answer, out of real interest in the other person, and shows how it differs from diagnostic, confrontational and process questions.
- Edgar H. Schein
- 2013
- 8 min read
- 8 key takeaways
- 8 ways to apply it
Key takeaways from Humble Inquiry: The Gentle Art of Asking Instead of Telling
The ideas readers on HourLife upvote the most, in order.
-
1
Humble Inquiry is asking questions to which you do not already know the answer.
The test is honest: if the answer is already in your head, the question is a statement wearing a question mark. Real curiosity about the other person is what makes it work.
-
2
Telling puts the other person one step down; asking lifts them up.
Telling implies the other person does not know. Asking makes you, for a moment, dependent on them, and that small shift is what builds the relationship.
-
3
We live in a culture that values doing and telling over asking and relating.
In task-focused workplaces, being the one with the answer is rewarded, so asking can feel like weakness. Notice the pull to tell, and decide on purpose whether to follow it.
-
4
Here-and-now humility means admitting that, right now, you depend on someone else.
Rank does not change this: the surgeon depends on the nurse who notices something is wrong. Saying so out loud makes it safe for that person to speak up.
-
5
Diagnostic questions steer the conversation, so use them knowingly.
Asking about feelings, causes or next steps moves the talk toward your interests. That can be useful, but it is a choice; start humble, and steer only once you understand.
-
6
Confrontational inquiry is telling disguised as a question.
"Have you thought of..." and "Wouldn't it be better if..." carry your idea inside them. If you have an idea, it is more honest to offer it as one.
-
7
Process inquiry asks about the conversation itself.
Questions such as "Is this helpful?" or "Are we getting off track?" turn attention to how you are talking. They are a good reset when a conversation starts to go wrong.
-
8
Between seeing and acting, we react and judge, often too fast.
Schein's ORJI cycle runs Observe, React, Judge, Intervene. Slowing down at the judging step and checking your reading with a question keeps you from acting on a mistake.
How to apply Humble Inquiry: The Gentle Art of Asking Instead of Telling
Turn the ideas into something you can do this week.
Count your tells
In one meeting you lead, tally the statements you make against the questions you ask that you do not know the answer to.
Write your opening question
Prepare one humble opener for your next one-to-one, such as "What's on your mind?", and ask it before any agenda item.
Name your dependence
At the start of a project, tell each person one thing you will need from them that you cannot do yourself.
Make a rewrite card
List three confrontational questions you often ask, such as "Have you tried...?", and write a humble version of each.
Agree a process check
Agree with your team that anyone can ask "Can we check how this conversation is going?" at any time.
Ask before you tell
In every conversation, ask at least one question you do not know the answer to before you give your view.
Slow the ORJI loop
When you react strongly to something, ask one clarifying question before you judge or act.
Ask one process question a week
At the end of a weekly meeting, ask "How did that go for you?" and listen to the answer without defending.
Ask what you do not know, of the person who knows it, and let them see that you need the answer.
