The Most Expensive Leadership Mistake Is the Question You Didn’t Ask
Three weeks into a major project implementation, a junior staff member caught me in the hallway after a meeting. She started to say something, hesitated, then said, “Never mind. I’m sure you’ve thought of this.”
I was busy. I had the answers. I let it go.
Three weeks after that, we hit a critical issue that pushed the project back two months. It was exactly what she had wanted to mention.
I hadn’t been dismissive. I hadn’t been rude. I had simply been certain — and my certainty closed the door before she could walk through it.
That moment has stayed with me for years, not because it was unusual, but because it was so ordinary. It happens in organizations every day. A leader’s confidence signals that the answers are already in the room, so anyone holding a question learns to keep it to themselves.
What I lacked wasn’t empathy or technical skill. I lacked what organizational psychologist Edgar Schein called Humble Inquiry — the discipline of asking questions to which you genuinely don’t know the answer, and actually waiting for the response.
It sounds simple. It isn’t. And the cost of not practicing it is far higher than most leaders recognize.
Why Leaders Stop Asking (and Start Telling)
Schein spent decades studying organizational culture and identified three forces in American professional culture that actively work against inquiry:
- Task accomplishment bias. We’re rewarded for getting things done, and asking questions feels like it slows things down. The fastest path to looking competent is having the answer.
- Status and rank consciousness. In most organizations, authority flows from expertise. Leaders are expected to know. Admitting uncertainty can feel like a challenge to the foundation of your role.
- Individualism and competition. Professional culture rewards people who demonstrate capability, not people who surface what they don’t know. The incentive is to project confidence, not to invite collaboration.
The result, as Schein wrote in Humble Inquiry (2013), is a culture that “over-values telling and under-values asking.” We train leaders to be decisive. We rarely train them to be genuinely curious.
And here’s what makes this particularly difficult: the more experience you accumulate, the harder it gets. Thirty-five years of leading organizations gives you a rich pattern library — you’ve seen how these things usually unfold. That pattern recognition is real and valuable. It is also the exact thing that makes you likely to mistake your assumptions for facts.
Psychologist Chris Argyris called this the ladder of inference. We observe something, and within seconds we’ve climbed from raw observation to conclusion — selecting data, applying assumptions, drawing meaning — without ever checking whether our inference matches reality. The more experienced we are, the faster we climb that ladder, and the more confident we are at the top of it. (See also: When Leaders Don’t Trust the Numbers.)
Humble inquiry is how you climb back down.
Not All Questions Are Equal
Schein identified four types of inquiry, and the differences matter more than most people realize.
Humble Inquiry starts from genuine curiosity. You don’t know the answer, you’re not steering toward a conclusion, and you’re actually listening. “What’s your read on where this project stands?” asked without an agenda is humble inquiry.
Diagnostic Inquiry guides the conversation toward information you want. It’s still inquiry — you’re asking, not telling — but you’re shaping the direction. “What do you think caused the delay?” steers the conversation without asserting the answer.
Process Inquiry is meta-communication — asking about how the conversation itself is going. “Are we solving the right problem here?” or “What are we not talking about that we should be?” These questions are underused and often transformative. (See also: Communication Isn’t What You Say.)
Confrontational Inquiry is the one that sounds like a question but isn’t. “Don’t you think the real issue is the timeline?” is an assertion dressed in a question mark. It gives the appearance of openness while shutting the conversation down.
Most leaders live in Confrontational Inquiry territory, thinking they’re being collaborative when they’re actually just packaging their existing conclusions in a less abrasive format. The other person knows it. They answer accordingly — which is to say, they tell you what you’ve already indicated you want to hear.
The distinction isn’t just semantic. It changes what information reaches you.
Psychological Safety Doesn’t Happen by Decree
Amy Edmondson’s research on psychological safety has become one of the most cited bodies of work in organizational behavior. Her finding — that teams perform better when members feel safe to speak up, take risks, and admit mistakes — has been confirmed repeatedly, most famously by Google’s Project Aristotle, which identified psychological safety as the single strongest predictor of team effectiveness across hundreds of teams.
What gets less attention is the mechanism. Psychological safety isn’t an attitude you can mandate. You can’t announce it, require it, or put it on a values poster. It’s a cultural output — the result of repeated interactions that either signal your input matters here or this is not a safe space to be uncertain.
Humble inquiry is how that signal gets sent.
When a senior leader asks a genuine question and genuinely listens to the answer — when they say “I don’t know, what’s your take?” without irony — it communicates something that no policy document can replicate. It tells people: my certainty is not the ceiling of what we know as a team.
Gallup’s research puts a number on this. Employees who feel their opinions count at work are 4.6 times more likely to feel empowered to do their best work. The Q05 item from Gallup’s Q12 engagement framework — “My supervisor, or someone at work, seems to care about me as a person” — is one of the strongest predictors of engagement. Inquiry is how caring gets expressed in practice. Not the caring you describe in a mission statement, but the caring you demonstrate in a conversation.
Brené Brown’s research on vulnerability in leadership reinforces this from another angle. Leaders who can say “I don’t know” or “Help me understand this” aren’t displaying weakness — they’re building the trust that makes honest communication possible. Vulnerability, Brown found, is not the opposite of strength. It is, in many organizational contexts, the prerequisite for it.
What High-Performing Organizations Actually Look Like
I’ve spent years as a Baldrige examiner, sitting across from leadership teams in organizations at every level of performance. The patterns that distinguish high-performing from low-performing organizations are often subtler than people expect. They show up not in strategy documents or process charts but in how leaders behave in rooms.
In high-performing organizations, you see leaders asking genuine questions — not setting up their next statement, but actually gathering information. Multiple voices contribute to complex decisions. When disagreements surface, they’re explored with curiosity rather than resolved by seniority. You regularly hear senior people say, “I don’t know” or “I hadn’t considered that.” The information that reaches decision-makers is more accurate because the incentive to filter bad news upward has been reduced.
In low-performing organizations, the pattern is almost always the opposite. A senior leader dominates the conversation. Others in the room wait to hear what the leader thinks before forming an opinion — or at least before sharing one. Disagreements get resolved by authority rather than evidence. The leader leaves the room confident in the alignment of the team. The team leaves the room having said what they calculated was safe to say.
The gap between those two rooms is not intelligence, strategy, or resources. It is inquiry culture — and inquiry culture starts with whether the person at the top of the hierarchy asks genuine questions.
W. Edwards Deming observed that “the most important things cannot be measured.” He was talking about quality management, but the principle scales directly to leadership. The intelligence you need most — the early warning signals, the ground-level pattern recognition, the concerns that haven’t yet become crises — almost never shows up in your data. It lives in the people around you who are waiting to see whether it’s safe to bring it forward.
The Expertise Paradox
There’s a painful irony embedded in all of this. The leaders who most need to practice humble inquiry are often the ones for whom it’s most difficult — because they have earned the right to their confidence. Thirty-five years of experience, hundreds of decisions, thousands of conversations. That’s not arrogance; that’s a legitimate track record.
The paradox is that expertise creates both the pattern recognition that makes you valuable and the cognitive shortcuts that make you dangerous. You categorize faster, which means you also stop looking sooner. Your internal model of how things work becomes so well-developed that it can override incoming data that doesn’t fit the model.
The junior staff member who hesitated in the hallway had less experience. She also had fewer assumptions and a closer view of the specific situation on the ground. Both things were true simultaneously. Her perspective wasn’t a substitute for mine — but it was information I didn’t have, and I didn’t get it because my certainty communicated that I didn’t need it.
Humble inquiry isn’t about pretending you don’t know things you know. It’s about staying genuinely open to the possibility that what you know isn’t everything that matters.
A Practical Starting Point
Framework is useful. Practice is where it becomes real. Here’s a seven-day structure for beginning to shift your inquiry ratio:
Days 1–2: Track your tell-to-ask ratio. For two days, pay attention to how you enter conversations. When someone brings you a problem or update, do you begin by sharing what you know or by asking what they know? Don’t try to change anything yet — just observe. Most leaders are surprised by how heavily weighted toward telling they actually are.
Days 3–4: Practice with low-stakes relationships. Choose someone you trust and practice staying in genuine inquiry for a full conversation. Ask questions. Let the pauses sit. Resist the urge to finish their sentences or redirect toward what you already believe. Notice what you learn that you wouldn’t have otherwise.
Days 5–6: Apply it in a high-stakes context. Bring the same discipline into a meeting or conversation where the stakes are real. Before you share your perspective, ask two genuine questions. Write them out beforehand if that helps. The goal isn’t to appear humble — it’s to gather information before you form your position.
Day 7: Reflect on what shifted. What did you learn that you wouldn’t have learned by telling? Where did you resist inquiry and default to assertion? What would it take to make this a consistent practice rather than a seven-day experiment?
The payoff isn’t immediate, and it isn’t always comfortable. Building a habit of genuine inquiry means tolerating the ambiguity of not having the answer — which runs against most of what professional culture rewards. But organizations that get this right are more adaptive, more honest about their problems, and more effective at solving them.
The Question You Didn’t Ask
The staff member in the hallway wasn’t wrong to hesitate. She read the signals correctly. I had communicated, through certainty and busy-ness and the particular way experienced leaders carry authority, that the conversation was already over.
I’ve thought about that moment many times since. Not because the project delay was catastrophic — it wasn’t — but because it was a clear illustration of how information failure actually works. It’s rarely dramatic. Nobody withholds the critical insight out of spite or fear. They withhold it because the leader’s behavior made it seem unnecessary to share.
Edgar Schein’s framework isn’t primarily about being a nicer person. It’s about building systems where the information that leaders need actually reaches them — where the people closest to the work can surface what they see without calculating whether it will be welcome.
That’s not a soft skill. That’s organizational intelligence. And the entry point for building it is the discipline of asking genuine questions — and staying quiet long enough to hear the answers.
The most expensive leadership mistake usually isn’t the wrong decision. It’s the question you didn’t think to ask, because you were already certain you knew the answer.
What question are you not asking right now — and who in your organization is waiting to be asked? (See also: The Accountability Crisis Hiding in Plain Sight.)
