A striking example of how perception of the same incident is processed is seen in this example. Patrol was pinned down and engaged in a shootout with a barricaded suspect. Immediately upon arrival, SWAT deployed and shot and killed the suspect. Shortly afterward, the chief arrived and was clearly more concerned with the power outage that had knocked out all the downtown traffic signals. I seriously doubt any of the officers involved in the shooting were concerned about anything other than their survival. Very clearly, the perception gap in this incident was night and day.
In an ideal world, ICS at SWAT incidents would consist of command elements who are trained and knowledgeable in strategy and tactics and who understand how best to deploy all their tools – SWAT, CNT, Patrol, PIO, etc. But in the real world, oftentimes, ICS is still left to rank and chance instead. Too often the result is that SWAT is handcuffed or must reinvent the wheel every time it’s called out for critical incidents. Savvy SWAT commanders often find ways to work with ICS, not against it. However, in the real world, this is not always possible. Just do the best you can, and always act as the consummate professionals you are.
When our SWAT team first formed, we had numerous detractors drooling over the prospect of our first “screw up.” We knew there was zero margin for error, and a single mistake would result in the unit being eliminated. Inadvertently, instead of destroying us, our detractors made us a better, stronger, and closer team. And an interesting thing happened along the way, we earned the respect and cooperation of those who count the most: the street cops.
Ultimately, SWAT’s professionalism will prevail.