A dispatcher with 10 years on the console can process a routine call almost without thinking. The address comes in, the call type registers, the units get dispatched, the CAD gets updated - the whole sequence fires like muscle memory. Fast. Efficient. Accurate.
That speed is earned and it's valuable. A busy shift depends on dispatchers who can move routine work through the system without burning cognitive resources on every keystroke. The problem emerges when a non-routine call arrives wearing a routine disguise.
The pattern-matching trap
"Smoke in the area" comes in. The experienced dispatcher has handled 500 smoke-in-the-area calls. The pattern recognition fires instantly: probably a brush fire, dispatch an engine, move on. What they didn't catch was that this address is a quarter mile downwind from the propane storage facility, the caller mentioned a "weird smell" they dismissed as wood smoke, and the wind shifted two hours ago from the direction that would carry fumes from the facility toward this neighborhood.
A less experienced dispatcher, working slower and without the instant pattern match, might have spent an extra 30 seconds with the caller. Might have heard the "weird smell" comment differently. Might have pulled up the map and noticed the facility. Might have dispatched hazmat alongside the engine.
The experienced dispatcher's muscle memory processed the call faster. The less experienced dispatcher's slower, more deliberate processing might have processed it better.
This isn't an argument against experience. It's an argument against assuming that experience automatically produces judgment. Speed and judgment are different skills. Experience builds the first one reliably. It builds the second one only if the dispatcher is actively thinking about their thinking, which is very hard to do when the muscle memory is doing the thinking for them.
The complacency nobody admits to
Experienced dispatchers don't think of themselves as complacent. The word feels insulting. They're fast because they're good. They pattern-match because it works 498 times out of 500. The two times it doesn't work are invisible until they produce a bad outcome, and by then nobody connects it to the pattern recognition that usually works perfectly.
The better framing isn't complacency - it's automation. The brain automates repeated tasks to free up capacity for new ones. That's a feature, not a bug, until the automated response gets applied to a situation that needed manual processing. The dispatcher didn't choose to dismiss the weird smell. Their brain categorized the call before they consciously evaluated it.
Training judgment at the 10-year mark
Experienced dispatchers need different training than new hires. They don't need protocol refreshers. They don't need basic call processing practice. What they need are scenarios designed to disrupt their pattern-matching - calls that sound routine and aren't, calls where the critical detail is buried in a sentence the dispatcher would normally skip past, calls where the correct response is the opposite of what the pattern predicts.
That's judgment training. It doesn't replace muscle memory. It builds a check on top of it - a cognitive pause that fires when something doesn't quite fit, even when everything else about the call says "routine."
The goal isn't to slow experienced dispatchers down. It's to make them dangerous in both directions - fast when speed is what's needed, and alert when speed is what gets you in trouble.