Best in Command: What Grissom AFB Taught Me About Leading Under Pressure

During my time as an Operations Intelligence officer at Grissom Air Reserve Base, our unit was recognized as "best in command" — a distinction that, on paper, looks like an individual accomplishment but in practice was almost entirely about the team.

Operations Intelligence work is a strange mix of high-stakes and unglamorous. Analysts spend long stretches preparing detailed mission materials — terrain analysis, threat assessments, recovery plans — that crews rely on but rarely see the work behind. The job rewards precision and punishes shortcuts, and it's easy for that pressure to turn into a culture of checking boxes rather than genuinely understanding the mission.

When I took over leading the team, the unit was technically proficient but inconsistent — strong on some mission types, shaky on others, depending on who happened to be on shift. My first instinct was to write better checklists. That helped, but it didn't solve the underlying problem: junior analysts didn't have a consistent way to learn the judgment calls that didn't fit neatly into a checklist.

So we restructured how the team trained. Instead of pairing new analysts with whoever was available, we built a rotation where every analyst worked through the same set of mission profiles with the same two or three senior reviewers, specifically so that the reasoning behind a judgment call got passed on consistently — not just the answer. We also started doing short after-action reviews on every mission package, regardless of whether anything went wrong, because the goal wasn't to catch failures — it was to build a shared vocabulary for "good enough" versus "great."

Within about two quarters, the variance between our best and weakest mission packages had nearly disappeared. Crews started requesting specific products by name because they trusted the consistency, not just the occasional standout analyst.

When the "best in command" recognition came through, it felt almost beside the point — the award was for the unit, but the real change was that any analyst on the team, on any given day, could produce work that met the same bar. That's the kind of leadership outcome that doesn't show up in a single mission's after-action report, but it's the one that actually compounds.

It's a lesson I've carried into every team I've led since: the goal isn't to be the strongest link. It's to make sure there isn't a weak one.