A dispatcher mishandles a high-profile call. The QA review surfaces it. It goes up the chain. By the following week, every shift briefing in the center is about that exact call type. Every in-service block for the next quarter is built around the specific failure mode. The training calendar gets rewritten around a single incident.
Six months later, something completely different goes wrong - something that was on nobody's radar because the entire training program pivoted to the last failure. The pattern repeats.
This is reactive training, and it's the default mode in most comm centers.
Why reactive training feels right but isn't
After a bad outcome, there's institutional pressure to demonstrate that something is being done. Training is the most visible response. The logic feels airtight: this specific thing went wrong, so we'll train on this specific thing so it doesn't happen again.
The problem is opportunity cost. Every hour spent on reactive training is an hour not spent on the 15 other training gaps that haven't produced a visible failure yet. Your dispatchers haven't trained on the dam EAP in three years, but that gap is invisible because the dam hasn't failed. Your mutual aid channel procedures haven't been exercised in 18 months, but that gap is invisible because you haven't had a multi-jurisdictional incident.
The gaps that produce the next bad outcome are almost never the same gap that produced the last one. Training to the exception makes you excellent at preventing yesterday's failure and blind to tomorrow's.
The visibility bias
Bad outcomes are visible. Near-misses are invisible. Gaps that haven't been tested yet are invisible. The dispatch training calendar gets built around what's visible, which means it gets built around what already went wrong rather than what's most likely to go wrong next.
A center that just had a botched active shooter call will train heavily on active shooters for the next six months. During those six months, they'll handle 300 medical calls, 50 domestic violence calls, 20 missing person calls, and zero active shooters. The training emphasis is inversely proportional to the probability.
This isn't an argument against training on active shooters. It's an argument against letting one bad outcome distort the entire training program at the expense of everything else.
Building a balanced training calendar
Start with the data, not the last incident. Pull your call types by frequency. Pull your QA error patterns. Pull your EAP inventory. Map them against your last 12 months of training. The places where high-frequency call types or high-consequence scenarios have received zero training time are your priorities - not because they failed, but because they haven't been tested.
Reserve 20% of your training calendar for reactive work - the specific incident reviews, the policy refreshers, the things that respond to real events. But protect the other 80% for the proactive work: the scenarios your team hasn't faced, the infrastructure they've never trained on, the coordination procedures they've never exercised.
The reactive 20% manages yesterday. The proactive 80% prepares for tomorrow. Most centers have that ratio inverted.