In the ever-evolving world of IT and consulting, we’re used to dealing with ambiguity, complexity, and… let’s say, interesting personalities. But there’s a specific pattern of behavior that many of us have encountered — whether in the form of a junior developer who wants to refactor the whole architecture after a weekend on Medium, or a manager who dismisses technical feedback with a confident “trust me” grin.

This pattern has a name. It’s called the Dunning-Kruger Effect — and it’s not just annoying. It can be toxic, particularly when left unchecked in team dynamics, project decisions, and company culture.

If you’ve ever looked around and thought, “How is the least informed person the most convinced they’re right?” — you’re not imagining things. And you’re definitely not alone.

What Is the Dunning-Kruger Effect?

The Dunning-Kruger Effect is a well-documented cognitive bias first studied in 1999. It describes how people with low ability in a given domain tend to overestimate their own competence — often dramatically so. At the same time, people with genuine expertise tend to underestimate themselves, because they’re more aware of what they don’t know.

Put simply: the less someone knows, the more they think they know. And the more they actually know, the more humble and uncertain they become.

This isn’t just philosophical. It’s observable. In performance studies, those in the lowest quartile often rank themselves near the top, while top performers tend to rate themselves closer to the middle.

The workplace version? People with surface-level understanding behaving as if they were authorities — and in the process, making decisions, leading projects, or even managing others based on a foundation of overconfidence and blind spots.

Why It Matters (Especially in Tech and Consulting)

The tech and consulting worlds are particularly vulnerable to the Dunning-Kruger Effect. These are fast-paced, knowledge-heavy industries where it’s easy to become exposed to a concept without truly mastering it.

Take IT, for example. The sheer volume and velocity of change means that almost no one can keep up with everything. But that doesn’t stop people from believing they’ve mastered a domain after watching a few conference talks or experimenting with a framework over the weekend.

In one study, over 40% of software engineers rated themselves in the top 5% within their companies. Mathematically impossible, of course, but very revealing in terms of self-perception.

In consulting, the problem becomes even more visible — and dangerous. The product you’re selling is your expertise. But if consultants are overestimating their skills, or clients are underestimating complexity, outcomes will suffer. Boutique firms are particularly exposed: there are fewer safety nets, fewer reviewers, and often more space for self-confidence to eclipse substance.

The worst part? In many environments, these behaviors are rewarded. We unintentionally promote the loudest voice instead of the most informed one. The person who speaks with conviction is often assumed to be right — especially if they’re charismatic or confident.

The Damage Done

So what happens when the Dunning-Kruger Effect goes unchecked in a team or company?

First, it distorts collaboration. Individuals affected by this bias often reject feedback, dominate discussions, and fail to recognize the competence of others. They may push forward with flawed ideas, confident that their reasoning is sound — even as others with deeper knowledge try (often in vain) to intervene.

Second, it damages performance. Because these individuals believe they know more than they do, they frequently take on tasks beyond their capabilities, underdeliver, or make basic errors that others then have to correct. The result is not just rework, but a ripple effect of delay, frustration, and technical debt.

Third, it disincentivizes real expertise. Those with strong skills but a humble approach may get overlooked, especially in cultures that equate confidence with leadership. Over time, these people may disengage or leave — taking their silent competence with them.

Finally, at a systemic level, it poisons decision-making. Teams make poor strategic calls, hire the wrong people, or promote individuals based on perception rather than performance. And the organization pays the price, in everything from failed projects to declining morale.

Sound Familiar?

You might recognize some common workplace signs of this effect:

• Individuals who are adamant they’re right, even when they’re not experts
• People who talk over others or ignore evidence in meetings
• Colleagues who refuse to consider feedback, convinced they know better
• Leaders who promote based on confidence rather than capability

These are not always malicious behaviors. Often, they’re rooted in genuine unawareness. That’s what makes this bias so dangerous: those affected don’t realize they’re affected. They don’t lack intelligence, they lack insight into their own limitations.

Can We Do Anything About It?

Yes. And we should. Because the answer isn’t just “avoid these people” (especially when they’re in leadership positions). The real challenge — and opportunity — lies in building systems and cultures that reduce the risk.

Here are some proven strategies.

1. Foster a culture of humility and learning.
Normalize the phrase “I don’t know.” Encourage curiosity and questioning, and reward those who admit limitations and seek input. Leaders should model this behavior.

2. Use feedback loops and objective evaluations.
Self-assessment is not enough. Regular peer reviews, 360-degree feedback, and performance metrics help everyone calibrate their self-perception. It also helps identify overconfidence before it causes real harm.

3. Differentiate exposure from experience.
Just because someone has read a white paper doesn’t mean they’re an expert. Define clear expectations for roles, and ensure that promotions or project ownership are based on demonstrable skills — not confidence or popularity.

4. Create mixed-experience teams.
Encourage collaboration between senior and junior team members. This helps prevent inflated self-perception, creates mentorship opportunities, and improves overall decision quality.

5. Review decisions collectively.
Implement code reviews, architecture reviews, or project retrospectives where assumptions can be challenged constructively. Dunning-Kruger doesn’t thrive in transparent, peer-validated environments.

6. Train hiring managers and leaders.
Teach those responsible for hiring or promoting others to recognize overconfidence and ask the right questions. A strong interview performance doesn’t always equal deep competence.

7. Provide coaching — especially at the top.
Executives are not immune to this bias. External coaching or structured feedback can help senior leaders develop better self-awareness and reduce organizational risk.

Humility as a Competitive Advantage

In our current age — where anyone can Google an answer or ask a chatbot and feel informed — the Dunning-Kruger Effect is more present than ever. The illusion of knowledge is easy to access, and with it comes a temptation to speak with unwarranted authority.

But if we want resilient teams, sustainable decisions, and meaningful innovation, we need to elevate a different trait: humility.

Yes, it may not trend on LinkedIn. Yes, it may be quieter than bravado. But humility is the foundation of real growth — for individuals, for teams, and for organizations.

Let’s stop promoting noise over nuance. Let’s recognize that knowing your limits is not a weakness, but a strength. And let’s make space for the people who say, “I’m not sure, but I’ll find out.”

Because in the long run, they’re the ones who build things that actually last.

If this post made you reflect on someone you know… or maybe even yourself, you’re not alone. We all sit somewhere on the Dunning-Kruger curve, depending on the topic. The key is recognising where and doing something about it.

And if you’re curious about the other side of this coin, when skilled people underestimate themselves, I explored that in a previous post: Imposter Syndrome in IT: Between Generative AI and Social Media Pressure.