Shoot-to-Kill Policy, Shock, Awe and Change Management

Opinion: The British police made more than one tragic mistake when it shot an innocent man to death in the underground, Ziff Davis Internet's Jeff Angus writes. They took the same destructive approach to secrecy and radical action that often

We must all hang together, or assuredly we shall all hang separately.
—Benjamin Franklin Last months mistaken execution of a London commuter by British security forces holds a management lesson worth learning for all kinds of organizations—from governmental to corporate to professional practices. The security personnel appear to have carried out their orders by the book. But those who put the policy into place, people in the British government, blundered into a classic management snake pit that American executive teams fall into far too often. The Poms lethal gaffe is the result of two colossal clangers, one Ill name "The Polaroid Instant Blunder" and the other I call "The Etinuum Error." The government secretly put a "shoot to kill" preventative execution policy into place for the police. That policy only became known because the men and women doing their jobs executed a man commuting to work with five shots to the head at close range. He turned out to be an innocent bystander. Part of what made backlash so strong to this management blunder is that the action is very un-British. Unlike over-amped police in New York City and some Third World countries like Guatemala, the police in Britain dont normally kill non-Irish people only to discover the target was an innocent person. Aggressive policing is not part of their national self-image. The policy, as reported by Londons Sunday Times, allowed a senior commander to authorize police to execute without warning people suspected of carrying a bomb. The goal was to prevent potential suicide bombers from doing the psychopath thing; police were apparently directed to shoot at the head to take out the suspect without setting off the device with gunfire. I wont argue about the merits of preventative execution (the ultimate "no strikes, youre out" form of enforcement). Click here to read more about fighting terrorism with technology. I have a personal opinion thats not germane to the lesson in this example; I do see both the logic around which the policy became operational and why it guarantees the public execution of innocent people. Police needed new procedures; change was required; the procedures chosen were radically different from any historical precedent the country has known within its borders since, I believe, The Restoration (1660). The problem I want to discuss is the fact that, like too many big corporate change initiatives, the bosses didnt consult stakeholders and didnt even pretend to listen before making a change that would be seen by the stakeholders as not just very different, but possibly antithetical to their self-image. Read the full story on CIOInsight.com: Shoot-to-Kill Policy, Shock, Awe and Change Management Check out eWEEK.coms for the latest news, reviews and analysis on IT management from CIOInsight.com.