Competency vs. Confidence Why Your Technicians Think They’re Ready (But Aren’t)

Workforce & Capability

“I’ve done this a thousand times.” That sentence, said in good faith by an experienced technician, is one of the most reliable warning signs in industrial maintenance. Confidence and competency are not the same thing — and the gap between them is where careers, equipment, and sometimes people get hurt.

Here’s a scene I see almost every time I run a hands-on training session. A senior technician walks in — fifteen, twenty, sometimes thirty years on the floor. He’s been sent by his employer, often without much explanation, and he’s a little annoyed about it. Why is he in a classroom for a topic he’s been doing his whole career? When the practical exercises start, he’s confident. He’s relaxed. He moves quickly because he’s done this kind of work countless times.

And then, more often than people would expect, he hits a step where his technique is wrong. Not catastrophically — just enough to produce a calibration that’s out of tolerance, or a torque sequence that loads the joint incorrectly, or a documentation entry that doesn’t match what was actually measured. He doesn’t see it. The work looked right to him because it looked the way he’s always done it. The confidence was complete. The competency, on that specific detail, had drifted years ago.

This is the most uncomfortable conversation in industrial training, and it’s the one nobody wants to have. The honest reality is that your most experienced technicians are often the ones with the largest gap between how confident they feel and how capable they actually are on specific tasks — and the structures most plants rely on to manage that risk are not designed to catch it.

The Science: Why Confidence and Competency Drift Apart

This isn’t an opinion or a personal observation. It’s a well-documented psychological phenomenon called the Dunning-Kruger effect, first described in a 1999 study by David Dunning and Justin Kruger at Cornell University. They tested participants on logic, grammar, and reasoning, and discovered something striking: people who scored in the bottom 12th percentile rated their own performance, on average, in the 62nd percentile. Not slightly off. Massively off.

The mechanism behind it is brutal in its logic. The same skills that allow someone to perform a task well are the skills that allow them to recognize when they’re doing it wrong. If those skills are missing, the person can’t see the gap — and confidence fills the space where competence should be. As Dunning and Kruger put it: “it takes competence to judge competence.”

12 → 62

low performers self-rated at the 62nd percentile while scoring at the 12th

1999

Dunning-Kruger effect first published — replicated repeatedly across domains

70:20:10

the established framework: experience, coaching, and formal training

The effect plays out across both ends of the experience spectrum. Newer technicians often overestimate themselves because they don’t yet know what they don’t know. Highly skilled technicians sometimes underestimate themselves because they’ve seen enough complexity to be humble about it. The most dangerous zone, in my experience, is the middle: experienced people who have built strong confidence but whose specific task-level competency has quietly drifted from what “correct” actually looks like. They don’t feel uncertain. They feel ready. And the system around them rarely tests whether the readiness is real.

Two Things That Look the Same From Across the Room

From the outside, confidence and competency are easy to confuse. Both produce technicians who walk up to the job, pick up the tools, and get started without hesitation. The difference doesn’t show up in body language. It shows up in outcomes — sometimes weeks or months later, when a calibration drifts, a bearing fails early, or a process incident gets traced back to a step somebody was sure they did right.

Confidence	Competency
Internal feeling: “I’ve done this many times. I know how this works.”	Demonstrated ability: I can perform this task to a defined standard, observed by a qualified evaluator, today.
Built from years of repetition, including repetitions that were not corrected.	Built from supervised practice, with feedback that catches and corrects technique drift.
Scales with experience — grows almost automatically over time.	Decays without exercise — must be re-verified on a defined cycle.
Felt by the technician.	Verified by the organization.
Becomes dangerous when it outpaces real ability without anyone noticing.	Stays calibrated when the verification system is honest, structured, and recurring.

Why This Gap Is So Hard to See From the Inside

The competency-confidence gap doesn’t hide because people are dishonest. It hides because the structures that produce it are completely normal in industrial workplaces — and because once it sets in, the technician genuinely cannot see it. A few patterns show up in nearly every plant where I do assessments.

Repetition Without Correction

A technician learns a task once — maybe well, maybe not — and then performs it for years. Nobody corrects them, because the work “gets done.” Equipment runs. The job order closes. The technique stays exactly the way it was learned, including any errors that were never flagged. Confidence grows with every repetition. Competency, on those specific drift points, never gets recalibrated.

Outcomes That Don’t Fail Loudly

Most technique errors don’t produce immediate failures. A bearing installed slightly off may run for two years before it fails. A calibration done with the wrong reference value may produce process drift that gets attributed to upstream conditions. Without a tight feedback loop between technique and outcome, the technician has no way to know that what they’re doing is not working as well as they think it is.

Normalization of Deviance

This term — coined by sociologist Diane Vaughan in her study of the Challenger disaster — describes how unsafe or incorrect practices gradually become “the way we do it” when they don’t produce immediate consequences. In a maintenance context, it shows up as shortcuts that worked once, then twice, then a hundred times — until they’re indistinguishable from the standard procedure. The team isn’t cutting corners maliciously. They’re executing what experience has taught them is acceptable, because nothing has yet taught them otherwise.

Cultural Reluctance to Challenge Experience

On most plant floors, experience is treated as authority. A technician with twenty-five years of service is assumed to know more than a technician with five — and in many cases, they do. But this assumption makes it socially difficult to point out that the experienced person’s technique on a specific task has drifted from current best practice. Junior technicians who notice it learn quickly not to mention it. The organization loses the chance to catch the drift early.

Closing the Gap Without Breaking the Team

The single most important reframing here is that this is not a discipline problem or a character problem. It’s a structural one. Your most experienced technicians are not failing you — they’re operating in a system that wasn’t designed to catch the specific gaps that experience naturally produces. Closing the confidence-competency gap requires building structures that make verification routine, neutral, and respectful.

SIX WAYS TO CLOSE THE COMPETENCY-CONFIDENCE GAP

Each element addresses one driver of the gap. Done together, they shift the culture from “trust the experience” to “verify the capability” — without disrespecting the experience.

Make Verification a Normal Part of the Work, Not a Punishment

The single biggest cultural error organizations make is rolling out competency verification as a response to a problem. When verification is announced after an incident, it feels like an audit. When it’s built into the job from day one — every technician, every critical task, every defined cycle — it becomes part of the craft, the way recurrent training is in aviation or proficiency demonstrations are in nuclear operations. Nobody takes a recurrent check-ride personally. They take it as part of the job.

Verify by Demonstrated Performance on Real Tasks

Written tests measure information. They don’t measure competency. The only honest test of a technician’s capability is to ask them to perform the task on real or representative equipment, in front of a qualified evaluator, against a defined standard. The evaluation isn’t about catching them out — it’s about giving the organization a clear picture of where each person actually stands, and giving the technician a defensible record of their own ability.

Use a Standard External to the Team

Internal benchmarks have a quiet flaw: they tend to drift toward what the team is already doing. “Good” becomes whatever the senior technicians do, even if their technique has slowly diverged from current best practice. Anchor your standards to something external — OEM specifications, industry standards, certifications like ISA CCST, or assessments performed by a qualified third party. External standards reset the calibration that internal repetition tends to erode.

Recurring Re-Verification, Especially for Tasks Done Infrequently

Skill decays. A capability verified eighteen months ago, on a task the technician has not performed since, is no longer a verified capability. The cycle should be tighter for high-consequence, low-frequency tasks — the ones where confidence is high (“I’ve done this before”) but recent practice is rare. Aviation built this principle into the training calendar a long time ago. Industrial settings benefit from the same logic, even when the regulatory pressure isn’t there to require it.

Pair Experienced Technicians With Structured Peer Review

One of the most effective tools we use is structured peer observation. Two experienced technicians watch each other perform a critical task against a documented standard, and compare notes. This is not a power dynamic — it’s a calibration exercise between equals. It catches the technique drift that nobody else is positioned to see, it builds a shared sense of what “good” looks like, and it spreads better practices through the team faster than any classroom session can.

Treat Findings as Information, Not as Failure

When verification surfaces a gap, the next move determines whether the program works or quietly dies. Treat the finding as data: this task is where this technician needs more practice, here’s the support to close that gap. Don’t penalize. Don’t make it part of a performance review. Don’t broadcast it. Use it the way aviation uses simulator findings — as inputs to the development plan, not ammunition. Once technicians see that verification leads to support rather than punishment, the cultural resistance disappears, and the assessments start telling the truth.

What Changes When the Gap Actually Closes

When a verification culture takes root, the practical experience inside the maintenance organization changes in ways that reach beyond the training room. Calibrations across the team get more consistent because the technique has been calibrated. Troubleshooting time on familiar faults drops because the diagnostic discipline is now genuinely shared, not just claimed. Near-misses get caught earlier because technicians feel safe naming the gap before it becomes an incident. New hires reach productive autonomy faster because the standard they’re measured against is the same standard everyone else has been verified to.

Just as importantly, the experienced technicians — the ones who initially have the most to lose from verification — often become its strongest advocates within a year or two. They tell us in interviews that, once the dynamic shifts from “prove yourself” to “keep your skills sharp,” verification becomes something they actually appreciate. It gives them a defensible record of their craft. It gives them feedback they otherwise stopped getting decades ago. It treats their work with the seriousness it deserves.

None of this happens overnight. Building a real verification culture takes 12 to 24 months, and the early conversations are the hardest. But every plant I’ve worked with that committed to it long enough to see the curve through has come out the other side with a workforce that’s more capable, more confident in a grounded way, and demonstrably more reliable in the metrics that matter.

FOUR QUESTIONS FOR YOUR NEXT TEAM CAPABILITY REVIEW

1. For our most critical tasks, what does “good” look like — and is it documented to a standard external to our own team?

2. When was each of our experienced technicians last observed performing those tasks, against that standard, by a qualified evaluator?

3. For tasks our team performs rarely but with high consequence if done wrong, what is our re-verification cycle — and is it actually being held?

4. When a verification surfaces a gap, what is our standard response — support and development, or something that feels closer to discipline?

If the answers reveal that your team is operating mostly on confidence and assumed competency, that’s the work. The good news is that experienced technicians, treated with respect, almost always become partners in closing the gap once the structure is in place to support them.

Confidence is not the enemy. A technician who lacks confidence cannot do the job well — the work requires decisiveness, judgment, and the willingness to act under pressure. The problem is confidence that is not anchored in current, verified competency, because that’s the exact pattern that produces incidents nobody saw coming.

What I’ve come to believe, after years in aviation maintenance and now in industrial training: experienced technicians are not the problem in this story. They are the people most affected by an organization that confuses confidence with competency, and they are also the people most invested in closing the gap once they see it framed honestly. The leaders who get this right don’t challenge the experience — they build the structures that keep it sharp. The technicians appreciate it. The plants run better. And the conversation about whether someone is “ready” stops being a feeling and starts being a fact.

Cesar Fernandez, PMP

Live Training Development Manager at Reliability Solutions | Specializing in E&I, mechanical precision maintenance, and workforce development | USAF veteran (aircraft maintenance)