"What Does Success Look Like?" — CQB, Metrics, and the Mission Nobody Reframed

Where This Started

I was recently a student in Greenline Tactical's NVG Shoot House course — a crawl, walk, run progression through room clearing under night vision, run by Don Edwards. Solid class, focused on entries, points of domination, the fundamentals of getting inside a room and owning it.

During the course, a student asked about pieing the door, fighting from the threshold — the concept of solving the room problem without actually going inside. It wasn't a bad question. Nobody wants to get shot. But the way it was framed revealed something: the student was thinking about it entirely from the perspective of personal survival. How do I not be in the room when bullets are flying?

Chris Sizelove pulled the conversation back to something nobody had addressed: why do we enter the room in the first place?

The answer — the original answer — is hostages. You enter the room because someone inside is going to die if you don't. You can't control what's happening to a hostage from the doorway. You flood the room because speed and presence inside is the only mechanism that saves the person who can't save themselves. That's the whole reason CQB exists.

I'd been training room clearing for years and had never once heard it explained that way. It was always just "the way it's done." Points of domination, violence of action, get inside and own the room. The what and the how got passed down. The why didn't.

And once you understand the why, it changes how you think about everything — the tactics, the risk, and what "winning" actually looks like for any given mission.

Part 1: Munich and the Birth of a Doctrine Built on Sacrifice

The Failure That Started Everything

On September 5, 1972, eight Palestinian terrorists infiltrated the Munich Olympic Village and took eleven Israeli athletes hostage. West German police attempted a rescue at Fürstenfeldbruck airbase — they lacked qualified snipers, proper equipment, and any real experience in hostage rescue. All nine remaining hostages were killed.

Munich exposed a terrifying gap: no Western military or police force had a dedicated capability to rescue hostages from armed terrorists. The response was immediate. West Germany created GSG 9 just two weeks later. France established GIGN in 1973–74, prompted by Munich and other incidents like the 1973 Saudi embassy siege in Paris. In the United States, Colonel Charles "Chargin' Charlie" Beckwith — who had been pushing for an SAS-style unit since his 1962–63 exchange tour with the British SAS — finally got approval. He co-founded 1st SFOD-D (Delta Force) with Colonel Thomas M. Henry on November 19, 1977.

Beckwith's vision predated Munich by a full decade. Munich wasn't the sole trigger — it was the event that tipped the political will in a direction he'd been pushing for years. But the post-Munich wave of CT unit creation is what gave modern CQB its institutional home.

The Original Success Metric

Delta Force's primary mission was hostage rescue, and the success metric was built around a single question: Are the hostages alive at the end?

Everything about CQB doctrine — the speed, the violence of action, the willingness to bypass rooms, the acceptance of enormous personal risk — was designed around this metric. Operators cleared rooms with fewer people than tactically ideal. They skipped risk-reducing procedures. They moved at speeds that increased their own vulnerability. All because reducing the time hostage-takers had to execute their captives was the single overriding priority.

As one experienced CQB practitioner explained: "In HR, the hostages are the mission. We focus on their safety and on how long it takes to reach them... To reduce this risk, we do everything we can to cut the time the hostage-takers have to pull the trigger. This mainly involves accepting higher risk to the assault team."

RAND terrorism analyst Brian Jenkins articulated the same calculus: "Such desperate measures are not undertaken without a grim, but necessary, calculus that weighs the chances of a successful rescue mission against a range of other outcomes, most of which involve the hostages' doom." Former Delta Force operators have echoed this logic publicly — the team is only sent in because the alternative is that everyone inside dies anyway.

The SAS demonstrated these tactics to the world during the 1980 Iranian Embassy siege in London, storming the building on live television. These units were closely-knit, frequently trained together, and cross-pollinated CQB techniques across borders.

The metric was never "did all operators survive?" It was "did the hostages survive?" Operator casualties were factored in from the start — not as failure, but as an expected cost. That's why you enter the room. That's why speed matters. That's why you accept the risk of being inside.

Part 2: How the Tactics Spread Without the "Why"

The Trickle-Down

CQB didn't stay in the kill houses of Delta Force. It migrated outward — and it migrated fast. Colonel Richard D. Hooker (Ret.) described the process in his 2021 Modern War Institute article "The Tyranny of Battle Drill 6": "Room clearing was seen as sexy and cool, and it spread to the Rangers and then to Army Special Forces... By the late '80s, as leaders from the Rangers rotated back into conventional light infantry units, they brought a mania for room clearing with them."

The migration chain:

1. Delta Force → developed CQB for hostage rescue
2. Rangers → worked alongside Delta as outer cordon, adopted room clearing
3. Special Forces (Green Berets) → picked up CQB from proximity to Delta/Rangers
4. Conventional infantry → leaders rotating from Ranger units brought it to Big Army
5. Law enforcement tactical teams → SOF veterans entered LE, brought dynamic entry with them
6. Broader law enforcement → post-Columbine active shooter doctrine pushed room clearing concepts further out

At every step, the technique transferred. The points of domination, the stack, the speed, the violence of action — all of that came through loud and clear. What didn't transfer was the context. The reason those tactics looked the way they did. The reason for the speed. The reason operators accepted that level of risk.

The "why" got lost in the migration. The "how" survived.

This is exactly what I experienced for years of training — learning the mechanics without ever being told the original purpose behind them. And I don't think my experience is unusual. If you've trained room clearing in the military, in law enforcement, or in the tactical civilian world, ask yourself: did anyone ever explain why these tactics exist the way they do? Or was it just "this is how it's done"?

The Metric Stayed the Same, the Mission Changed

When Battle Drill 6 was first formalized in FM 7-8 in 1992 as "Enter Building/Clear Room," it was a conventional infantry task — clearing rooms in a combat zone. The hostage rescue context was gone. By 2003, "Enter and Clear a Room" was a Warrior Task required of every deploying soldier regardless of MOS — because non-infantry units in Iraq and Afghanistan were regularly given battlespace that required urban raids.

In Fallujah in 2004, soldiers and Marines were clearing over 30,000 buildings against dug-in insurgents — no hostages involved, just enemy fighters in an urban battlefield. The infantry mission in Fallujah was fundamentally different from Delta rescuing hostages in Baghdad. But the room-clearing technique was the same four-man stack.

This isn't to say it was wrong to use those tactics in Fallujah or anywhere else. It's to say that the reason for using them — and the acceptable cost of using them — should have been a conscious decision based on the mission, not just inherited muscle memory from a hostage rescue doctrine.

Part 3: A Framework for Thinking About It

Mission Dictates Metric, Metric Dictates Tactic

Here's the mental model that clicked for me after Chris's breakdown in that shoot house. It's not complicated, but I'd never seen anyone lay it out:

The mission defines the success metric. The success metric defines the acceptable risk. The acceptable risk determines which tactics make sense.

When CQB was built for hostage rescue, that chain was tight:

• Mission: Save the hostage
• Metric: Did the hostage live?
• Acceptable risk: Very high — operators may die
• Tactic: Flood the room, maximum speed, violence of action, get inside NOW

Every element of the tactic — the speed, the aggression, the willingness to be inside the room — was a direct product of the metric. You accept that risk because someone inside needs you there.

The problem is that when the mission changes, most people keep running the same tactic without re-evaluating the chain. The tactic becomes "just how it's done" rather than a deliberate choice connected to a specific mission and metric.

The Two Ends Are Clear

On one end of the spectrum, the answer is obvious. Hostage rescue, active shooter — someone inside is going to die if you don't get in there. The metric is save the innocent, and the tactic that serves that metric is speed, aggression, and accepting the risk of being inside the room. This is the original CQB answer. It checks out every time. You move with purpose because every second you hesitate is a second someone might die.

On the other end, also pretty clear. If there are zero hostages and zero innocents at risk, the calculus flips entirely. From a military perspective, if it's just the enemy inside — use grenades, machine guns, a JDAM, whatever you have. The building is a problem to be destroyed, not a room to be entered. From a law enforcement perspective with a barricaded subject and no hostages, take your time. Set up, contain, wait them out. There's no life-or-death clock forcing you inside.

Neither of those ends require much discussion. The tactics match the mission naturally when the situation is clear-cut.

The Middle Is Where It Gets Interesting

The real conversation — the one worth having with your team — is everything in between. And honestly, that's where most real-world situations actually live.

You roll up on a structure and you don't know what's inside. Maybe there are hostages, maybe there aren't. Maybe there are civilians in the building, maybe it's all enemy. Maybe the HVT you're after has intel that's time-sensitive, maybe he doesn't. Maybe the situation is developing and what was a barricaded subject five minutes ago is now something else.

This is where the "why are we entering" question becomes more than philosophical — it becomes tactical. Because your answer to that question should change how you enter, not just whether you enter.

If the situation is ambiguous, you don't have to choose between full-speed Delta-style room flooding and not going in at all. The spectrum of techniques exists for this exact reason. Pie the door before committing. Do a threshold assessment. Limited penetration to gather information before you commit the whole team inside. These aren't lesser tactics or half-measures — they're tools for managing the uncertainty when you don't have enough information to know which end of the spectrum you're on.

The student's question in that shoot house — "why don't we just pie the door?" — wasn't wrong. It was just disconnected from the framework. If you're in a hostage rescue scenario, pieing the door costs you the thing that saves the hostage: time. You need to be inside, now. But if you're in an ambiguous situation where you don't know what's behind the door, taking a few extra seconds to assess from the threshold before committing might be exactly the right call. The technique matches the uncertainty.

The point isn't that one approach is always right. The point is that your tactics should be a conscious choice driven by what you know about the mission — not a default you inherited from training. Speed is justified when the mission demands it. Caution is justified when the situation is uncertain. Running full speed into every room because that's how you trained is no different than refusing to enter any room because you don't want to get shot. Both are defaults. Neither is a decision.

Asking the Right Questions

The framework is simple enough to run in your head:

What's the mission? — What am I actually trying to accomplish here? Save someone? Secure an objective? Clear a building? Arrest a suspect?

What does success look like? — If everything goes right, what's the outcome? A hostage alive? An HVT captured? Evidence seized? Area confirmed clear?

What risk does that success justify? — Is the outcome worth the risk of putting my team inside that room at speed? Is someone going to die if I take an extra thirty seconds?

Do my tactics match that answer? — Am I running HR-speed tactics because the situation demands it, or because that's the only speed I know? Am I hesitating because the situation allows patience, or because I'm defaulting to self-preservation?

That's it. Four questions. They don't give you a single right answer — they give you a framework for making a conscious decision instead of running on autopilot.

Part 4: Where This Plays Out in the Real World

When the Metric Was Right

The active shooter scenario is where the original hostage rescue logic maps most directly onto a broader audience. Before Columbine (1999), the standard response to an active shooting was to set a perimeter and wait for a tactical team. SWAT arrived 47 minutes after gunfire started at Columbine. The post-Columbine revolution changed the metric to stop the killing as fast as possible — and that metric justified accepting the same kind of risk the original CQB operators accepted, because the situation is functionally the same. People inside are dying. Every second you wait, someone else might die. You enter the room because someone inside needs you there.

That's the Munich logic applied correctly to a different context. The mission changed, but the metric honestly does justify the tactic.

When the Metric Got Lost

Uvalde is the most visible example of what happens when the metric breaks down.

When officers arrived at Robb Elementary on May 24, 2022, they initially moved toward the gunfire — consistent with active shooter training. But after taking fire, they retreated and reclassified the situation as a "barricaded subject" scenario. The DOJ's report called this "the most significant failure" of the response: "An active shooter with access to victims should never be considered and treated as a barricaded subject."

Through the lens of metrics, this was a catastrophic mismatch. Officers applied a success metric that prioritized waiting and minimizing their own risk to a situation where the correct metric was identical to hostage rescue — people inside were dying, and the only way to affect the outcome was to be inside that room. The 33 students and three teachers trapped for 77 minutes were functionally hostages.

I'm not bringing this up to pile onto the officers involved — plenty of people have done that. I bring it up because it's the clearest real-world illustration of why understanding the "why" behind CQB matters. If you understand that the whole reason these tactics exist is to save the person inside the room, then you understand when you must accept the risk of entry — and when it's a conscious choice rather than a default.

The Broader Pattern

The cases of Breonna Taylor and Amir Locke illustrate the opposite end of the spectrum — hostage-rescue-speed tactics applied to situations where nobody inside was in danger. These aren't examples I bring up to critique any specific team's SOPs. They're examples of the same metric disconnect playing out differently: in one case, not enough urgency when the metric demanded it (Uvalde). In the other cases, too much urgency when the metric didn't call for it.

Same root problem. The tactic was inherited. The "why" wasn't.

Part 5: Bringing This Back to Training

What I Took Away From That Shoot House

After Chris's breakdown, something shifted in how I approached the rest of that course. The mechanics didn't change — I was still running entries, still working POD, still doing the same drills. But I was doing them with an understanding of why the techniques look the way they do. Why the speed matters. Why being inside the room is the point, not a side effect.

That understanding doesn't make you less safe. It makes you more deliberate. You're not blindly accepting risk because "that's the drill." You're accepting risk because you understand what it buys — and for whom.

What You Can Do With This

This isn't meant to be the definitive word on CQB doctrine. It's meant to be a conversation starter — something you can bring back to your team, your training group, your next class, and use to pressure-test your own thinking.

A few questions worth asking in your next training session:

• "What's the mission for this scenario, and what does success look like?" — Before you talk stack order or entry technique, get the team aligned on what winning actually means for the problem in front of you.
• "Does our level of urgency match the mission?" — Are we moving at hostage-rescue speed because the situation demands it, or because that's the only speed we've ever trained?
• "What is the risk we're accepting, and what does it buy us?" — If the answer is "it saves the person inside," that's the original CQB answer and it checks out. If the answer is less clear, it's worth discussing.
• "Why are we entering the room?" — The foundational question. The one Chris asked in that shoot house that nobody had a clean answer for until he traced it back to Munich.

The Thread That Connects It All

The original inventors of modern CQB — Beckwith, the SAS, the early Delta operators — were clear-eyed about what they were doing and why. They were building a capability to rescue hostages, and they accepted that operators would die doing it. The metric was honest. The cost was understood. The tactic was purpose-built to serve that metric.

Fifty years later, those same tactics are used across military, law enforcement, and civilian tactical training — but the "why" has largely been lost in the migration. Most of us learned the how without ever learning the what for. I know I did.

Understanding the origin doesn't mean you have to change how you train. It means you can make informed decisions about when those tactics are the right answer, when they need to be adapted, and when a different approach serves the mission better. It means you can have a real conversation about risk, metrics, and mission — instead of just running the drill because that's the drill.

The tactic was never the problem. The failure to connect it back to the mission was.