The Dunning-Kruger Effect in IT: Why the Most Dangerous Words in IT Might Be, “I’ve Got This.”

The Dunning-Kruger Effect in IT: Confidence Exceeding Competence

One wrong command is all it takes. One confident administrator types a command into the wrong terminal window. A database disappears. A firewall rule locks thousands of users out of the network. A software update rolls into production without testing. A ransomware attack succeeds because someone assumes a security warning doesn’t apply to their environment.

Every experienced IT professional has a story like this. Sometimes we were the ones who made the mistake. Sometimes we watched someone else make it. Either way, the lesson is usually the same. The biggest threat wasn’t a lack of intelligence or IT knowledge. It was overconfidence.

Confidence is valuable. Customers want to believe we know what we’re doing, and our coworkers depend on us to make good decisions. But confidence without competence is dangerous. Few psychological concepts explain that danger better than the Dunning-Kruger Effect. Understanding this phenomenon is essential for anyone who works in technology because it speaks directly to the first of the Five Principles of IT Customer Service: technical competence. Not looking competent or sounding competent, but actually being competent.

Read the complete article just below the video.

What Is the Dunning-Kruger Effect?

In 1999, psychologists David Dunning and Justin Kruger published research showing that people with the lowest levels of competence in a particular area often overestimate their own abilities. Ironically, the very skills they lack are the same skills required to recognize their own shortcomings. Simply put, people who know the least are often the most confident, while those with genuine expertise are often more cautious because they understand the subject’s complexity.

This isn’t merely a personality trait. It’s a cognitive blind spot. If you don’t know much about a topic, you usually don’t know enough to recognize what you don’t know, or, as a former colleague used to say, “I don’t know what I don’t know.” That observation isn’t new. More than 2,400 years ago, Socrates commented, “I am the wisest man alive, for I know one thing, and that is that I know nothing.”

He wasn’t claiming ignorance. He was acknowledging humility. Wisdom begins with recognizing the limits of our own knowledge. Centuries later, philosopher Karl Popper expressed the same idea differently: “Our knowledge can only be finite, while our ignorance must necessarily be infinite.”

The more we learn, the more we discover how much remains to be learned. Or, as my father used to say, “The more you know, the more you realize how little you know.”

Why IT Is Especially Vulnerable to the Dunning-Kruger Effect

Technology evolves faster than almost any other profession. Every year introduces new cloud platforms, programming languages, cybersecurity threats, AI tools, frameworks, networking technologies, operating systems, and countless new applications. No one can master them all.

Yet it’s remarkably easy to convince ourselves that we already have. Someone spends six months learning Kubernetes and suddenly wants to redesign the organization’s infrastructure. A technician completes three Microsoft 365 migrations and concludes Exchange Online is easy. A programmer experiments with AI coding tools for a weekend and confidently announces that software developers will soon be obsolete. The problem isn’t enthusiasm. The problem is confusing early success with mastery. Anyone who’s spent years in IT knows how dangerous that assumption can become.

History Is Full of Brilliant People Doing Foolish Things

History is filled with examples of intelligent people whose confidence exceeded their knowledge. Think of the Titanic, the Challenger, or the Tacoma Narrows Bridge as examples of confidence gone wrong.

Everyday Dunning-Kruger in IT

Fortunately, most IT mistakes don’t become history lessons, but they can still cost organizations millions of dollars.

A junior administrator modifies firewall rules directly in production because “I know what I’m doing.” A developer pushes code without peer review because “it’s only a small change.” An engineer dismisses security recommendations because “I’ve never seen that happen.” A help desk technician interrupts the customer thirty seconds into the conversation because they’re convinced they’ve already diagnosed the problem. A project manager skips testing because “We’ve deployed this dozens of times.”

Different situations. Same mistake.

Confidence replaces competence.

At Compassionate Geek, we operate a testing server to apply patches and configuration changes before deploying them to our production server. We know our customers must be able to take our courses and access the resources we provide. They’re counting on us to follow best practices. Among those best practices is avoiding over-confidence.

We recently needed to make some changes to our DNS. I’m pretty familiar with DNS, but I asked another engineer to look over my shoulder while I made the changes. Good thing! I misread one of the settings, and he stopped me from making a change that would have crashed our website.

True Experts Usually Sound Different

One of the most interesting characteristics of genuine expertise is that it often sounds less certain. Experienced professionals say things like, “Let’s verify that,” “I may be wrong,” “Here’s my best hypothesis,” “I’d like more information before deciding,” or “Let’s test that assumption.”

Some mistake this caution for weakness. It isn’t. It’s professionalism, born from experience. Veteran IT professionals have been surprised too many times. They’ve watched software behave differently in production than it did in testing. They’ve seen one missing semicolon create hours of downtime. They’ve watched a routine Windows update cripple business-critical applications. Experience doesn’t eliminate confidence. It tempers it with humility.

Competence Requires Humility

The first principle of the Five Principles of IT Customer Service is competence. Competence isn’t pretending to know everything. Competence means maintaining and updating your knowledge, continuing to learn, recognizing your limitations, and seeking help when appropriate.

Some technicians worry that admitting, “I don’t know,” makes them appear incompetent. Usually the opposite is true. Customers are far more likely to trust someone who says, “I don’t know the answer yet, but I’ll find it.” That’s competence. Pretending certainty isn’t.

AI Makes This Even More Important

Artificial intelligence has made the Dunning-Kruger Effect even more relevant. AI produces answers that sound remarkably authoritative. Sometimes they’re excellent. Sometimes it hallucinates and provides dangerously wrong answers. The greatest danger isn’t that AI makes mistakes. The danger is that inexperienced people often lack the expertise to recognize when AI is mistaken.

Someone copies AI-generated PowerShell code. It runs successfully, so they assume it’s correct. Months later, they discover security vulnerabilities, scalability problems, or subtle bugs that an experienced engineer would have recognized immediately. AI is an extraordinary assistant, but it is not a substitute for expertise. Today, competence includes knowing when to trust AI and when to question it.

How to Avoid the Trap

None of us is immune to the Dunning-Kruger Effect. The goal isn’t to eliminate it completely. The goal is to build habits that reduce its influence.

Keep learning. Assume today’s expertise will eventually become outdated. Invite disagreement. Surround yourself with coworkers who are willing to challenge your assumptions. Verify before acting because confidence is never evidence. Conduct honest postmortems after outages and failed deployments. Teach others because explaining a concept often exposes gaps in your own understanding. Above all, remain curious. Curiosity is one of the strongest antidotes to overconfidence.

The Best IT Professionals Never Stop Learning

One of the great paradoxes of expertise is that genuine experts often feel less certain than beginners. It’s not because they know less, but because they know more. They understand complexity. They recognize exceptions. They’ve learned that every environment is unique and every solution has tradeoffs.

The novice says, “This is easy.” The experienced engineer says, “Let’s make sure.”

That’s not insecurity. That’s wisdom.

More Than Confidence

Let’s go back to where we started. One wrong command. One misplaced assumption. One person convinced they already knew enough.

Every experienced IT professional has either lived through that story or will someday. The lesson isn’t to become timid or indecisive. Customers need confident professionals, and organizations depend on decisive action. But the best IT professionals combine confidence with humility. They understand that competence isn’t measured by how certain they sound. It’s measured by how committed they are to continual learning, careful verification, and intellectual honesty.

Socrates understood it more than two millennia ago. Karl Popper echoed it in the twentieth century. The best engineers demonstrate it every day.

The wisest people in IT aren’t the ones who believe they’ve mastered technology. They’re the ones who recognize that, no matter how much they know, there is always one more command to verify, one more assumption to question, and one more opportunity to learn before they type those three deceptively dangerous words: “I’ve got this.”

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.