Simulation Training Leadership: Why It Works

I'm Kurt Schmidt, founder of Schmidt Consulting Group, and I've spent years watching organizations invest heavily in strategy decks and training manuals while their frontline teams quietly fall apart under real pressure. The gap between what leadership believes is happening and what's actually happening on the floor is almost always wider than anyone wants to admit. Simulation training leadership is one of the most practical, evidence-backed ways to close that gap. And it's still wildly underused outside of aviation and defense.

I had a conversation recently with Dr. Doug Slakey, a transplant surgeon turned health system innovator who's building a center for health system science at Belmont University's Frist College of Medicine in Nashville. His work gave me a sharper vocabulary for something I've been observing across client engagements for years: the organizations that perform best under pressure are the ones that practice failure before it's expensive.

Simulation training means putting people into realistic, scenario-based exercises that replicate the pressure, ambiguity, and cross-functional demands of actual work. Then debriefing on what went wrong. It's distinct from classroom training, which teaches people what to do, and from on-the-job experience, which teaches them after the damage is done. Simulation sits in the middle: deliberate, controlled, and designed to surface the gaps that only show up when the stakes feel real.

Adhocracy is a related concept worth defining here. Popularized partly by NASA's Apollo program, it describes a leadership structure that enables frontline experts to make decisions within a framework of clear objectives and measurables, rather than routing every call up a hierarchy. It's the organizational counterpart to simulation: both treat human judgment as the asset worth developing.

---

What Does Simulation Training Actually Develop in Leaders?

Simulation training leadership develops the one thing that no compliance module ever does: situational judgment under conditions of uncertainty. When you put a surgeon, a nurse, a technologist, and an administrator in a room together and give them a pressurized scenario, you find out very quickly where the handoffs break, where communication assumptions fail, and where people default to hierarchy instead of expertise.

Dr. Slakey described a simulation exercise involving dialysis fistula procedures where administrators were asked to perform needle insertion with and without ultrasound guidance. The administrators struggled without the ultrasound. With it, even a non-clinician could succeed. The result: those administrators approved ultrasound purchases. They had previously viewed ultrasounds as a cost. After the simulation, they understood them as a quality-of-care investment. That's the shift simulation creates. It moves decision-makers from abstract policy to lived consequence.

I've seen versions of this play out in technology contexts too. Hackathons are a rough equivalent. Put a C-suite executive on a product team for 48 hours and watch how their assumptions about "what customers want" collide with what engineers and designers are actually building. Every time I've seen an executive genuinely participate (rather than drop in for 20 minutes in a suit), it changes how they communicate with their team for months afterward.

---

Why Do Most Organizations Skip Simulation Training Leadership?

The short answer is that it's uncomfortable and it surfaces inconvenient truths. The longer answer involves how most organizations are structured.

Leaders trained in traditional command-and-control environments. And Jack Welch's era at GE produced a generation of those leaders. Are conditioned to reduce complexity to a linear process. An assembly line is predictable. Healthcare, professional services, and most complex B2B environments are not. When you run a simulation and discover that your ICU infection rate is partly caused by one-person cleaning teams who can't lift 80-pound mattresses, you've just invalidated months of "hand hygiene compliance" training. That's embarrassing. And so organizations skip the exercise that would have surfaced it.

There's also a budget framing problem. Training tends to sit in the "cost" column. But people are assets, and developing those assets is a capital investment. The organizations that keep cutting training to protect short-term margins eventually discover they've cut their way to a capability gap they can't bill through. I've watched new leaders come in, slash headcount and training, celebrate the improved EBITDA for a year, then watch quality metrics erode. And be gone before the reckoning arrives. The next leader inherits the mess. The cycle continues.

When organizations treat simulation training as a core operating investment rather than a budget line to trim, they stop that cycle. They build teams that can handle the unexpected because they've practiced handling it.

---

How Does Compassionate Leadership Connect to Simulation Training?

This is where a lot of leadership conversations stop short, so I want to spend some time here.

Simulation training leadership is a technical intervention. But the culture that makes it work is built on something harder to quantify: genuine empathy between people who occupy very different roles in a system. The us-versus-them active that Dr. Slakey describes in healthcare. Payer versus patient, administrator versus clinician. Exists in almost every complex organization. Marketing versus sales. Engineering versus product. Client services versus finance. These divisions produce the same dysfunction: people optimizing for their piece of the process while the overall outcome degrades.

Simulation breaks those divisions because it puts people in each other's situations. An administrator who has personally struggled to insert a needle without ultrasound guidance will never look at a "just buy the cheaper equipment" budget decision the same way. A VP of Sales who has sat with a customer support rep through a live escalation call will stop writing policies that make those calls harder.

This connects directly to what I think is the most underappreciated leadership skill: the ability to seek out dissenting voices and actually listen to them. Not the performative listening of leadership rounds where three executives in suits show up and get routed to the happy patients. Real listening, where the person cleaning the room gets to say that the mattresses are too heavy for one person to lift. And gets believed.

That ICU example stuck with me because the answer was sitting in the room the whole time. Nobody asked the environmental services team. When they finally did, the problem was identified and solved. No consultant needed. No expensive technology. Just the question: "What are we missing that you can see?"

---

How Should Leaders Structure a Simulation Training Program?

A few principles have held up across every context I've studied or been involved with.

First, mix the functions deliberately. Homogeneous groups confirm what everyone already believes. You want the surgeon next to the administrator next to the nurse. You want the CTO in the room with the customer success rep. The friction between those perspectives is the data. It's also, eventually, the foundation of the empathy that makes teams actually work.

Second, focus KPIs on outcomes rather than process steps. This is a persistent failure mode in complex organizations. The process measure says "patients discharged in under 24 hours after knee surgery." The outcome measure asks whether the knee surgeries are succeeding, how many patients are returning with infections, and how many need revision procedures. Optimizing for the process measure produces organizations that discharge people quickly and readmit them a week later. performance measurement

Third, debrief without blame. The shift from a blame culture to a learning culture is slow and requires consistency from the top. When Dr. Slakey described moving away from the surgical ABCs. "Assess, Blame, Criticize". Toward using near-misses and errors as educational material, he was describing a culture change that takes years. But simulations accelerate it because the "failure" happens in a safe environment. Nobody is harmed. Everyone learns.

Fourth, fidelity matters less than you think. Two full floors of simulation space at a brand-new medical school is impressive, but it's not the starting point for most organizations. You can run powerful simulation exercises with limited physical resources. What you can't shortcut is the debrief. That's where the learning actually happens. The scenario is just the trigger.

---

How Do You Get Leadership Buy-In for Simulation Training?

This is the practical question, and it's the one I get most often.

Dr. Slakey's answer was the one I've seen work in non-healthcare contexts too: articulate the why before the how. Most change initiatives die because the people proposing them lead with the mechanism. "We're going to run quarterly simulation exercises using scenario cards and cross-functional teams." That sentence will get the meeting rescheduled three times. "We want to make sure that when something goes wrong at 2am, our people know exactly what to do. And we want to find out now whether they do" is a different conversation.

Listening to dissenting voices is the second move. Confirmation bias is a leadership tax. Leaders who've already decided that simulation training works will find every piece of evidence that confirms it. The smarter approach is to actively recruit the skeptics, hear their objections fully, and build the program in a way that addresses them. Skeptics who feel heard become the program's most credible advocates.

The third element is mapping the full journey of whoever the program is meant to serve. In healthcare, that's the patient journey across 365 days, not a blood pressure reading twice a year. In professional services, it might be the full client engagement lifecycle, from prospecting through offboarding. Where are the handoffs? Where are the knowledge gaps? Where does the system assume something that reality doesn't support? That mapping exercise alone is often more illuminating than the first simulation.

For the aerospace and defense benchmarks on simulation-based training, RAND's research on collective simulation-based training in the U.S. Army offers useful reference points on how structured simulation scales across large organizations.

One honest note: if you're a small firm with fewer than 15 people and your primary challenge is lead generation or revenue structure, a simulation training initiative is probably downstream of more urgent work. Get your pipeline healthy first. pipeline development

---

Simulation vs. Traditional Training: A Comparison

---

Key Takeaways

• Simulation training leadership develops situational judgment that no classroom module can replicate. People learn by doing under pressure, then debriefing what went wrong.
• Mixing functions deliberately in simulation exercises (administrators with clinicians, executives with front-line staff) produces the empathy and communication shifts that structural reorganizations rarely achieve.
• Organizations that treat employee development as a capital investment outperform those that treat it as a cost line to trim; the cut-to-the-bone cycle always produces a capability gap eventually.
• KPIs built around process compliance miss the point; outcome-focused measurement is what simulation training is designed to improve.
• Getting buy-in requires leading with the why, genuinely recruiting skeptics, and mapping the full journey of the people the system is meant to serve.
• Fidelity of the simulation environment matters less than the quality of the debrief; that's where the behavioral change actually happens.

I covered related ideas about building high-performing teams and leadership development on The Schmidt List. Worth a listen if this topic is live for you.

The question I keep coming back to is this: your team will eventually face a scenario they've never seen before. The only real variable is whether they've practiced for it. Have they?