Crew Resource Management exists because the aviation industry figured out that most crashes weren't caused by mechanical failure or pilot incompetence. They were caused by communication failures between competent people working under pressure. A co-pilot who saw the problem but didn't speak up. A captain who dismissed input from the flight engineer. A crew that had all the information needed to prevent the accident, distributed across three people who never assembled it into one picture.
The comm center has exactly the same dynamics. Multiple dispatchers working the same incident. A supervisor managing the floor. Field units feeding information back. Call takers passing data to dispatchers. Everyone competent. Everyone under pressure. The information exists. The question is whether it gets assembled correctly before the decision gets made.
The hierarchy problem dispatch shares with aviation
In aviation, CRM directly addressed the authority gradient - the tendency for junior crew members to defer to the captain even when they had critical information that contradicted the captain's plan. The fix wasn't to eliminate hierarchy. It was to formalize the expectation that everyone on the crew had a responsibility to speak up, and that the captain had a responsibility to listen.
In dispatch, the same gradient exists. A newer dispatcher sees something in the call that doesn't match what the supervisor just decided. A call taker has information from the caller that contradicts the dispatch that just went out. A dispatcher on the adjacent position notices that the channel assignment is wrong but doesn't want to step on the primary dispatcher's call.
In each case, the information that would have improved the outcome exists in someone's head. The barrier to sharing it isn't technical - it's interpersonal. And unlike aviation, dispatch has no formal framework for overcoming that barrier.
What CRM would look like in the comm center
Formalized callouts. When a dispatcher sees something that doesn't match expectations - an address in a flood zone during a weather event, a unit number that doesn't belong to the agency being dispatched, a caller report that contradicts the call type in CAD - there's a standard, expected way to surface it. Not "hey, um, I think maybe..." but a structured communication that's understood by everyone on the floor as "I have information that may change the plan."
Structured handoffs. When a dispatcher transfers an incident to another position - shift change, position split, overflow - the handoff follows a standard format: situation, background, assessment, recommendation. Aviation calls this a briefing. Medicine calls it SBAR. Dispatch calls it "here, take this" and hopes the next person reads the CAD notes.
Sterile cockpit rules. In aviation, during critical phases of flight, non-essential communication is prohibited. The dispatch equivalent would be a protocol for high-acuity incidents where the primary dispatcher is protected from interruptions that aren't directly relevant to the active incident. Most centers do this informally. CRM would make it formal, expected, and trained.
Why this doesn't exist yet
Dispatch doesn't have the same institutional infrastructure for training innovation that aviation does. Airlines spend millions on simulator training and CRM programs because the FAA requires it and because a crash costs billions. Comm centers operate on budgets that barely cover staffing. The investment case for formal CRM training in dispatch is strong, but the funding environment doesn't support it.
Which means the principles get adopted piecemeal, center by center, by supervisors who read about CRM and think "that's exactly what happens on my floor." Good enough to start. Not yet enough to transform the profession the way it transformed aviation.