The Sound Barrier Was Never the Problem. The Assumption Was.

In 1947, pretty much every aeronautical engineer agreed on one thing: fly an aircraft at the speed of sound and it rips itself apart. Buffeting, shock waves, total loss of control. They called it “the sound barrier” for a reason. Everybody pictured a wall. Hit it, and you’re done.

On October 14, 1947, Chuck Yeager flew the Bell X-1 aircraft through it anyway. No catastrophic structural failure. No wall. Just a sharp jolt as the aircraft crossed from subsonic to supersonic, and then smoother air on the other side.

The barrier wasn’t physical. It was a long-accepted assumption that nobody had actually tested at full commitment. Once someone did, the entire premise collapsed, and the entire industry changed.

I bring this up because it’s the exact mechanism I see killing performance inside companies every week, and almost nobody is tracking what it costs them.

The assumption that never gets tested

Impostor syndrome is not a confidence problem. It’s an unverified assumption treated as settled fact. “I’ll sound stupid if I say this. I’m not ready for that role. They’ll find out I don’t belong here”. Nobody tests it. They just treat the wall as real and steer away from it.

What’s the result? It a behavior pattern simply called “Refusal.” Not fear. Refusal. Fear of failure is something every high performer has and works through constantly. Refusal is different. Refusal is the decision not to act, not to speak, not to step forward, made before any data comes in to confirm the fear was even justified.

And because it happens entirely inside someone’s head, in the half second before a meeting comment doesn’t get made, leaders have no way to see it on a dashboard. It’s not in the engagement survey. It’s not in the exit interview, not directly. So it gets written off as a personal issue, a confidence thing, something HR offers a workshop for and moves on from.

That’s the misdiagnosis. And it’s an expensive one.

What you’d be measuring if you could measure it

You can’t put a sensor on hesitation. But you can look at what it produces, because what it produces is observable.

The idea that arrived three months late. Ask any leadership team how often someone says, after the fact, “I actually saw that coming” or “I had that idea a while ago.” That’s not a confidence story. That’s not a confidence story. That’s value sitting on the shelf, delayed by Refusal, and a delayed idea has a real price tag in a competitive market.

The promotion gap. Companies already track time-to-promotion and internal mobility. What they don’t usually track is how many qualified people never put themselves forward for the role at all. That’s not a pipeline problem on paper. It’s a pipeline problem in practice, and it’s invisible until someone goes looking for it.

The slow decision. In high-stakes moments, the person with the right answer sometimes says nothing, not because they’re unqualified, but because they haven’t verified whether their hesitation is fact or distortion. Multiply that pause across enough meetings and enough quarters and it becomes a measurable drag on decision speed.

The quiet exit. People rarely leave and say “impostor syndrome” in the exit interview. They say “I didn’t feel like I had room to grow,” or “I wasn’t given the opportunity.” Often, they had more opportunity than they used. That’s not a knock on them. It’s what happens when capable people keep treating an assumption as a wall instead of testing it.

Why this is a performance problem, not a personal one

A friend who runs a successful IT company pushed me on this recently. He wanted a real number, a clean line connecting impostor syndrome to the bottom line. I don’t have a single number for him, and I’d be lying if I pretended I did. What I have instead is the same thing aeronautical engineers eventually had to accept about the sound barrier: the thing they were treating as an immovable fact was actually just an untested assumption, and the cost of never testing it was staying subsonic forever.

That’s the real bottom-line argument. It’s not that you can assign a precise dollar figure to a feeling. It’s that the feeling produces specific, trackable absences: the idea not said, the role not pursued, the decision not made on time, the person who quietly leaves instead of pushing through. Those are line items. They’ve just been filed under the wrong category.

The fix isn’t more confidence. It’s a faster way to test the assumption. 

Yeager didn’t wait to feel ready. He didn’t wait for fear to go away. He had a protocol, a plane built for the specific job, and a moment where the decision was made before the doubt got a vote.

That’s what I teach. Not “feel more confident.” A real-time method for catching the assumption in the moment it shows up, checking it against actual evidence, and acting anyway. Detect it. Verify it against what’s actually true. Act before the hesitation gets to make the call.

The sound barrier was never a wall. It only worked as one because nobody had broken through it yet. Refusal works the same way inside your organization right now, and it’s costing you more than anyone’s currently counting.

Wondering what assumptions may be limiting performance on your team or curious about what this discussion looks like in a live setting? Let’s schedule a conversation.

Watch my demo video → https://vimeo.com/801696873