What happens after every corporate training event?
Twelve supervisors return from a day off the floor. A skilled facilitator. Solid content. A real conversation about psychological safety and how to give better feedback.
Then Monday arrives. The floor is moving. A team member makes a mistake. The supervisor responds exactly the way they always have.
The training didn’t disappear. It still happened. It just didn’t transfer.
This is the most under-diagnosed problem in frontline supervisor development — and one of the most consequential. Organizations spend real money on real programs and absorb the gap between investment and outcome as though it were inevitable.
It isn’t. Pilot training figured out how to close it before most of today’s HR leaders were born.
This week I sat down with Matt Gjertsen — Air Force Academy graduate, nine-year instructor pilot in the T-1 and KC-10, former Head of Training & Development at SpaceX, and founder of BUILT — to pull on a question neither of us is done answering: what did aviation’s development model get right, and what would it take to apply it seriously inside an organization?
Why Frontline Supervisor Training Doesn’t Survive Monday Morning
The brain stores information contextually. It encodes learning alongside the sounds, the people, the physical space, and the emotional temperature of the environment where the learning happened. When the retrieval environment doesn’t match the learning environment, the connection doesn’t reliably fire.
A skill learned in a conference room is tagged to a conference room — not to the floor, the noise, the pressure, and the specific person standing three feet away.
This isn’t a content problem. The content might have been excellent. It’s a structural problem — one that pilot training largely avoided because it never separated learning from the environment where performance actually had to appear.
In aviation, you don’t practice emergency procedures in a classroom and call it complete. You practice them in the aircraft, under conditions approximating actual pressure, with an instructor close enough to observe your exact responses. The debrief happens where the briefing lived. The corrections happen in the aircraft, on the same approach, in the same airspace.
The closer the training is to the environment where the skill must appear — the people, the noise, the stakes, the specific sensory cues — the more likely it is to transfer when it’s actually needed.
That principle alone should change how most organizations design their frontline supervisor development programs.
Procedure vs. Technique: What Every Instructor Pilot Knows That Most Organizations Don’t
There’s a distinction in aviation that translates directly into leader development.
Procedure and technique are not the same thing.
Procedure is non-negotiable. It’s the checklist run before every takeoff. The emergency sequence burned in so completely that it fires under pressure without conscious thought. Procedure is consistent by design — because consistency is the point, and deviation carries real risk.
Technique is how you execute the procedure. The exact feel on the throttle. The timing of the flare. The scan pattern developed over hundreds of approaches. Two experienced pilots can run the same procedure in ways that look and feel completely different — and both be right. Technique adapts to the person, the conditions, the moment.
Here’s the translation to frontline leadership development.
Most organizations give their supervisors neither.
There is no defined procedure — no non-negotiable set of behaviors a frontline leader is expected to execute consistently, regardless of personality or tenure. No standard for the one-on-one that actually has to happen. No minimum for how a performance expectation gets communicated and verified on the floor.
Without the procedure, technique is just improvisation. Every supervisor makes it up based on personality and prior experience. The result is ten supervisors running ten different operations — and a senior leader who can’t explain why one shift consistently outperforms another.
The fix isn’t to eliminate individual style. Relationship and personality are real. But technique without procedure is variance without a floor. And that variance shows up in engagement scores, in inconsistent team member experiences across departments, in turnover that gets blamed on compensation when the actual driver is something else entirely.
Define the procedure. Then let technique live inside it.
There Is No Such Thing as a Soft Skill
Matt said something I haven’t been able to leave alone.
“The only difference between a soft skill and a hard skill is that we haven’t thought about the soft skill enough to make it hard yet.”
The label “soft skill” has always done quiet damage to frontline supervisor development. It classifies feedback, coaching, expectation-setting, and direct conversation as personality traits — things a person either has or doesn’t. Which is a convenient position for any organization that doesn’t want to build the curriculum, the practice structure, or the observation loop required to actually develop them.
But feedback is a behavior. Behaviors are observable. Observable behaviors have components. Components can be taught, practiced, repeated under pressure, and evaluated.
Matt described a moment during his time as an instructor pilot in undergraduate pilot training where the entire gap between a student succeeding on an approach and washing out came down to a one-inch throttle movement. Not feel. Not talent. Not intangible aviation instinct. A single, measurable, correctable behavior — observed by someone close enough to see it and precise enough to name it.
Every so-called soft skill in your development program has an equivalent. A specific behavior, inside a specific interaction, that makes the difference between a conversation that develops someone and one that quietly damages the relationship.
Most organizations have never gotten close enough to find it. Not because it doesn’t exist — because finding it creates an obligation. You’d have to teach it. Practice it. Put an observer on the floor and build the feedback loop that determines whether someone actually acquired it.
That’s harder than a training day. It’s also the only approach with a reasonable chance of changing what happens Monday morning.
The Developmental Presence Nobody Has Built
One thing Matt and I kept landing on from different directions: the instructor pilot role doesn’t end when flight school ends.
In the Air Force, the instructor rating follows a pilot into every operational unit. On a Pacific crossing, if a co-pilot has a skill gap and there’s an instructor in the aircraft, that crossing becomes a training opportunity. The developmental presence isn’t reserved for a classroom. It lives in the work — closest to where the performance actually has to happen.
Most organizations have no equivalent. They have a manager — often overextended — and an annual training calendar. The person who functions like an instructor pilot, present enough to observe the one-inch throttle adjustment and close enough to correct it in the moment, simply doesn’t exist inside most frontline leadership structures.
The manager is supposed to fill that role. In most cases, they were never told that’s what the role requires, and were never given the tools or the bandwidth to do it.
According to the 2026 Gallup State of the Workplace report, employee engagement sits at 22%. Manager engagement, measured separately: 20%. The supervisors responsible for other people’s engagement are among the least engaged people in the building.
That isn’t a hiring problem. It isn’t a motivation problem. It is a development infrastructure problem — and it won’t be solved by another training day.
A frontline supervisor development program that actually moves the needle isn’t built around events. It’s built around an ongoing, embedded developmental relationship that makes behavior change possible after the event is over. The same way aviation builds it — not as a one-time certification, but as a presence that follows the work.
Where to Start
If you’re recognizing the training-to-behavior gap in your own operation — if your supervisors are improvising because no one gave them a procedure to work from — The Leader’s Preflight Checklist is the starting point. Download it free at operationlead.com/checklist.
If you’re a senior leader watching development investment go in and engagement scores stay flat and you want to understand what a development infrastructure looks like rather than what another training event costs — request a call to learn about our system and process here.
And if you want to learn more about Matt, check out his work at BUILT: builtleaders.com.
The conference room isn’t the problem. The absence of a system that develops leaders where the work actually happens — that’s the problem. Leaders can be built. It just doesn’t happen by accident.
Let’s Lead,
Craig
