Intellectual Humility: The Most Underrated Skill in IT Leadership

I attended a meeting where a senior executive confidently explained why an important IT project was behind schedule due to a software problem. He had a detailed explanation, a proposed solution, and complete confidence in his understanding of the problem. Then an audience member quietly raised her hand and said, “That’s not what’s happening.” She explained that the real issue wasn’t the software at all. It was a vendor dependency no one in leadership had considered. The room fell silent for a moment. To the executive’s credit, he didn’t become defensive. He simply said, “I didn’t know that. Tell me more.”

That moment changed the direction of the meeting. More importantly, it changed the team’s culture. By admitting he didn’t have all the answers, the executive invited others to contribute. The discussion became more honest, more collaborative, and ultimately more productive.

That’s intellectual humility, and it may be the most underrated leadership skill in IT.

Confidence vs. Competence

Unfortunately, many technology leaders have been conditioned to believe the opposite. Promotions often come because of technical expertise. CIOs, IT managers, and MSP owners are expected to project confidence, not intellectual humility. Customers expect competence. Employees look to leaders for direction. Somewhere along the way, some leaders begin to believe they must always have the answer. The pressure to appear certain can become so strong that admitting uncertainty feels like admitting weakness.

In reality, the opposite is true.

Three Ways We Are Stupid

In a YouTube video titled “The 3 elements of stupidity, according to philosophy,” Philosopher Jonny Thomson recently discussed the three ways people act stupidly:

1. We outsource our critical thinking
2. We engage in willful ignorance
3. We seek to conform

One of his observations is surprisingly simple: the wisest people are comfortable saying, “I don’t know.” Thomson argues that we often admire people who sound confident, even when they don’t actually know what they’re talking about. Yet genuine wisdom begins with recognizing the limits of our own knowledge. When someone is willing to say, “I don’t know,” they create space to learn, to ask questions, and to discover better answers. Just as importantly, they give everyone else permission to do the same.

That idea isn’t new. More than 2,400 years ago, Socrates is credited with saying, “I am the wisest man alive, for I know one thing, and that is that I know nothing.” Whether the quotation is perfectly accurate or not, the principle has endured for centuries because it captures an essential truth. The more we learn, the more we recognize how much remains unknown.

The best tech leaders understand this better than most.

Intellectual Humility and Competence

Our industry changes too quickly for anyone to keep up with every new development. Artificial intelligence is reshaping software development, cybersecurity threats evolve daily, cloud platforms introduce new capabilities every month, and customer expectations continue to rise. Expertise is still essential, but expertise has a shelf life. Yesterday’s best practices can quietly become tomorrow’s outdated assumptions.

That’s why intellectual humility is not the opposite of competence. It is what allows your competence to continue growing.

One of the greatest dangers facing experienced leaders is not ignorance. It’s overconfidence. Frankly, this is also a danger for IT pros. After solving thousands of problems, it’s easy to assume you’ve seen this one before. You hear the first few details of an issue and immediately begin diagnosing it. You stop listening because your brain has already decided what the answer must be.

Sometimes you’re right. Sometimes you’re not.

In IT, the cost of that mistake can be enormous. Projects fail because leaders assume they understand customer requirements without asking enough questions. Security incidents occur because teams dismiss concerns that don’t fit their existing assumptions. Service desk technicians overlook the real problem because they’re focused on proving their initial diagnosis rather than testing alternative explanations. It’s similar to a detective who stops looking for suspects after finding one.

The issue isn’t intelligence. The issue is certainty.

The Principle of Being a Good Listener

One reason I emphasize good listening skills in The Five Principles of IT Customer Service Success is that listening requires intellectual humility. You can’t genuinely listen if you’ve already decided what the other person is going to say. You can’t learn if you’re only waiting for your turn to speak. Whether you’re talking with a frustrated customer, a systems engineer, or a member of your executive team, effective listening begins by acknowledging that the other person may know something you don’t.

That attitude changes the way leaders ask questions. Instead of asking, “Why didn’t you follow the process?” they ask, “Help me understand what happened.” Instead of saying, “Here’s what we’re going to do,” they ask, “What options have we not considered?” Instead of assuming silence means agreement, they ask, “What concerns haven’t we discussed yet?”

Those are not signs of indecisiveness. They are signs of mature leadership.

Intellectual Humility Creates Psychological Safety

Intellectual humility also creates psychological safety, one of the defining characteristics of high-performing teams. When leaders admit mistakes, ask for input, and change their minds when presented with better evidence, employees become more willing to speak honestly. Junior technicians point out risks they might otherwise keep to themselves. Experienced engineers challenge assumptions before small problems become expensive ones. Team members stop protecting their egos and start protecting the organization.

I’ve seen the opposite happen, too. Leaders who always have to be right eventually surround themselves with people who stop telling them the truth. Meetings become exercises in agreement rather than opportunities for better decisions. Problems remain hidden until customers discover them first. The leader may appear confident, but confidence without curiosity is a dangerous combination.

Customers Don’t Expect You to Have All the Answers

This principle extends beyond internal leadership and directly affects customer relationships. Customers rarely expect an IT professional to know everything immediately. They do expect honesty. Most users are surprisingly patient when they hear, “I don’t know yet, but I’ll find out.” What frustrates them is false confidence, wasted time, and the feeling that no one is really listening. Intellectual humility encourages technicians to investigate rather than guess, to verify rather than assume, and to solve the right problem rather than the obvious one.

How MSP Owners Can Use Intellectual Humility to Build Trust with Clients

For MSP owners, this has another benefit. Intellectual humility builds trust with clients. A provider who admits uncertainty, thoroughly researches the issue, and returns with a well-supported recommendation is far more credible than one who confidently delivers the wrong answer. Clients aren’t paying for perfection. They’re paying for expertise, honesty, and sound judgment.

Perhaps the greatest irony is that the most accomplished leaders I’ve known were also the most intellectually humble. They never felt compelled to prove how smart they were. They asked thoughtful questions. They sought out people who disagreed with them. They changed course when new evidence warranted it. Their confidence came not from believing they knew everything, but from trusting their ability to learn.

As artificial intelligence becomes more capable, this leadership quality will become even more important. AI can summarize information, write code, analyze data, and recommend solutions; AI even helped write part of this article, but it cannot replace human judgment. The leaders who succeed in the coming decade won’t be those who pretend to have all the answers. They’ll be the ones who know how to ask better questions, challenge their own assumptions, and remain curious long after others have stopped learning.

The executive at the beginning of this article didn’t lose credibility when he said, “I didn’t know that.” He gained it. His willingness to admit what he didn’t know transformed a room full of people into a team determined to solve the problem together.

That’s the kind of leadership every IT organization needs. Not leaders who always have the answers, but leaders who are curious and who have the confidence to say, “I don’t know.”

And then ask, “What can we learn together?”

Next Level IT Customer Service Training

Enroll your team now in Compassionate Geek IT online customer service training so they can work together, get things done, and take care of customers.