The Psychology of Capability

Competence and confidence are meant to move together, like two gears sharing the same shaft. When they fall out of alignment, things start to slip. Confidence without competence becomes noise. Competence without confidence becomes hesitation. The objective is not confidence alone, but confidence that has been properly calibrated through experience, pressure, and honest evaluation.

This is where the foundation of execution culture is formed. Earned confidence replaces assumption. Quiet mastery takes the place of performance. Accurate self-assessment overrides ego. And teams begin to organize themselves around actual skill instead of the loudest voice in the room. That is the difference between appearing ready and being ready.

The Friction That Reveals the Gap

In 2011, I was working at the Lawrence Energy Center as the Piping Superintendent for Sterling Boiler & Mechanical. The project was a baghouse expansion, expanding the footprint of the powerhouse outward by 1 square mile to help improve carbon emissions. It was complex, fast-moving, and full of variables that didn’t announce themselves ahead of time.

It was an interesting and truly fun project to be an active participant in. And… to say that I learned a lot would be a major understatement.

The Construction Manager, Mike, was an ironworker by trade. He didn’t care much for pipefitters, and he made that clear on more than one occasion. The feeling was mutual, at least at the start. But I could see that he had been around and spoke from experience and knowledge. He had no patience for false confidence. He wasn’t interested in how things sounded. He cared about how they would actually perform when it mattered.

That created friction, but it also created clarity. Because underneath the tension was a standard: if you were going to speak, you needed to know. And if you didn’t know, you needed to find out before it cost the team.

“I’m Worried About What We Can’t See”

One day he told me to walk with him. We stepped out of the trailer, hard hats on, the plant stretching out in front of us. He didn’t waste time.

“I’m going to tell you this once. I need you to comb over every square inch of those blueprints and get your plan in place.” Then he paused and looked back at the job.

“I’m not concerned about the obvious things that ANYONE can see… I’m worried about the things we can’t see.”

Then he patted me on the shoulder and said, “Make Sense?”

It did.

That statement shifted everything. Because it reframed the work. The goal wasn’t to confirm what was already obvious. The goal was to uncover what hadn’t been considered yet and reveal the unseen variables that only show up when pressure hits.

Building Capability Through Iteration

So… I did as I was directed. And from that point forward, the process became intentional.

The crew kept working on their assigned tasks and I began the combing process. After a few days, I went to my General Forman and told him the same things. We walked through the areas we were going to focus on during the shutdown, the scope of work, the items I identified and asked him to punch holes in it… to see what I missed.

The GF and I then reconvened that Monday and compared notes. Then we got with the Foremen and the Job Steward the next day and told them the same thing. We walked through the areas we were going to focus on during the shutdown, the scope of work, the items that we had already identified and asked them to punch holes in it… to see what was missing.

A week later, when our next planning meeting occurred, I had a plan in place to present to the CM Mike for him to review. He quickly perused over the plan and said without batting an eye, “It’s a good start. Do it again.”

And so we repeated that process for 2 more weeks. Each time, the instruction was the same: find the gaps. Challenge the assumptions. Expose what’s missing.

There was no room for defending the plan. No value in pretending it was complete. Every round of review stripped away false confidence and replaced it with something stronger. The plan was evolving, not because it was wrong, but because it wasn’t finished yet.

When pride is put aside, criticism quickly becomes calibration.

We repeated that cycle for weeks. Eventually, he had all 4 of the superintendents (Pipefitter, Boilermaker, Electrician, Iron Worker) walk the job together with him and go through the process together. We were aligning not just on tasks, but on understanding. By the time the shutdown arrived, we had identified additional scope, added leadership where it was needed, built out a structured night shift, and ensured that everyone knew not just their role, but the full picture.

What seemed excessive at the time revealed itself as something else entirely. It was quiet mastery being built, layer by layer.

The Moment That Tests the System

There’s a scene in We Were Soldiers where Col. Hal Moore, commander of the 1st AirCav division in Vietnam, stops a training exercise mid-action. The soldiers were rehearsing Hewy Helicopters landing, soldiers deploying, and then the helicopter taking off again. Makes sense… right?

Then Col. Moore walks up to a helicopter as it’s landing and hits the lieutenant in the chest and yells "You're dead!" Then points to the next soldier and yells, "What do you do?" The soldier responds, "Get off the chopper!"

The answer comes quickly, but the exercise is already broken open. The point has been made. Because the mission does not fail during the parts everyone rehearses. It fails in the moment no one accounted for.

Execution Culture Is Built in the Unseen

That experience reinforced something that has stayed with me ever since. False confidence focuses on what is visible and assumes the rest will work itself out. Earned confidence is built by deliberately searching for what is not visible and preparing for it anyway.

Strong teams are not defined by how clearly they can explain the plan. They are defined by how well they have challenged it before execution ever begins. They are willing to slow down early so they don’t break down later.

Mike wasn’t just pushing for a better plan. He was building a team that understood the difference between talking about capability and actually possessing it.

And in the end, capability doesn’t announce itself. It reveals itself when something goes wrong and the team doesn’t have to guess what to do next.