For almost two years, I was Chief Medical Officer of a hospital.
Early in my role, I rolled out a new night call schedule. I had walked the doctors through it. I had briefed the Chief Nursing Officer. Because that’s what good leaders do — we communicate.
The schedule was solid. On Friday morning, I sent the launch email. It ended with, “We go live on Monday. Let me know if you have any concerns.”
We went live on Monday.
Three weeks later, when the schedule was failing in ways that were predictable to everyone but me, I sat in my office and asked a question that would change how I led from that day forward.
Why didn’t anyone tell me?
The honest answer was harder than I expected.
They hadn’t told me because I hadn’t actually asked.
We Were Trained to Have Answers
Medicine rewards expertise. It trains you to be the person in the room who knows.
A patient presents with crushing chest pain. You don’t pause and say, “Hmm, I wonder what the team thinks.” You act. You give orders. You tell people what to do and when to do it.
That instinct saves lives.
Then you become a leader, and the same instinct quietly starts damaging your team.
In clinical work, telling is how you show competence.
In leadership, telling when you should be asking is how you shut people down.
The Question That Isn’t a Question
Ed and Peter Schein, organizational psychologists who spent decades studying culture and leadership, wrote a small book called Humble Inquiry. It should be required reading for anyone stepping into a leadership role.
Their core idea is simple. Most of the questions leaders ask are not real questions. They’re statements wearing a costume.
“Does anyone have any concerns?” is not a question. It’s a closing line.
“Are we all on the same page?” is not a question. It’s pressure.
“Don’t you think it would be better if we did it this way?” is not a question. It’s an order with a question mark glued onto the end.
Real questions are different. They come from a place of not knowing. They’re asked because you genuinely want to learn something.
The Scheins called this humble inquiry, and they argued it was the most underused skill in modern leadership. For doctors, it might be the hardest skill we ever try to build.

The Four Ways to Ask
The Scheins describe four types of inquiry. Each one creates a different dynamic in the room — and most physician leaders use one of them almost exclusively without realizing it.
Humble inquiry is asking because you’re genuinely curious and have no answer in mind. “What’s been your experience with this?” You’re inviting someone to share what they know. You don’t yet know where the conversation will go. It builds trust because the other person feels seen.
Diagnostic inquiry is when you focus the conversation on a specific area. “What’s the biggest barrier to getting patients through triage faster?” You’re still asking — you genuinely want their answer — but you’re steering. Useful when you need to narrow things down. Still leaves room for the other person to think.
Confrontive inquiry is when you insert your own ideas, hunches, or hypotheses into the question itself. “Could the issue be staffing?” or “Have you considered talking to the night nurses about this?” Notice that these aren’t dishonest. You may genuinely want to know the answer. But you’ve quietly stopped drawing out the other person’s thinking and started introducing your own. The conversation now revolves around your hypothesis, not theirs.
Process-oriented inquiry is the one most leaders never use. It’s asking about the conversation itself. “Are we having the conversation you wanted to have?” or “What should we be discussing right now that we’re not?” It pulls the meeting up from content to process — and in difficult moments, it can be the most powerful question in the room.
“You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions.”
— Naguib Mahfouz
If you’re like most physician leaders, you live somewhere in confrontive inquiry without realizing it. You think you’re asking. You’re actually narrating your hypothesis and waiting for the team to confirm it.
And here’s why that’s a problem.
Every time you ask a confrontive question, you teach your team something. You teach them that you already have a theory. You teach them that the safest move is to tell you whether your theory is right — not to tell you what they actually see.
Over time, that becomes the only signal you ever get back.
The team stops surfacing what’s happening on the floor. They start telling you what fits your frame.
And then, three weeks after you roll something out, you find yourself sitting in your office asking the question I asked.
Why didn’t anyone tell me?
This post draws on Edgar and Peter Schein’s book “Humble Inquiry: The Gentle Art of Asking Instead of Telling.” Their work is foundational for anyone who leads teams — especially in healthcare, where what people don’t say can have grave consequences for patient experience and safety.



