Search

Blog Entries:

Some posts from The Methodology Blog around the time of Cold War Workaround

Archives by Subject:

More Resources

Cold War Workaround

Monday, November 9, 2009 by Slaughter Development

Over at the Lean Blog, Mark Graban reports on a Wired story about former Defense Secretary Robert McNamara. Apparently when he ordered secure numeric codes to be placed on the weapons nuclear arsenal, the Strategic Air Command set the passwords to all zeros.

Graban quotes the original Wired article:

When: 1960s

What: Midway through the Cold War, American leaders began to worry that a rogue US officer might launch a small, unauthorized strike, prompting massive retaliation. So in 1962, Robert McNamara ordered every nuclear weapon locked with numerical codes.

Effect: None. Irritated by the restriction, Strategic Air Command set all the codes to strings of zeros. The Defense Department didn’t learn of the subterfuge until 1977.

Lean Blog contributor Mark Graban responded directly:

Isn’t it amazing to see how clever people can be in working around a top-down management mandate? Would Secretary McNamara been more successful if he had involved all of the stakeholders and gotten buy in instead of issuing an order? How did DoD not know about the “subterfuge”? Because they weren’t going to the “gemba”??

There’s considerable wisdom in Graban’s commentary. He notes, for example, that the decision makers were probably not going to the gemba, a Japanese word roughly meaning “scene of the crime.” Graban also wonders if McNamara should have worked with stakeholders instead of sending down another mandate.

However, there’s even more going on here than just  the usual issue of top-down management, command and control thinking, and a failure to engage stakeholders on their own turf. The greater question is why did leaders feel that officers might be untrustworthy? After all, the original motivation for the change was due to the concern that a rogue US officer might order a small nuclear strike without proper authority. (It’s not clear if this fear came from the 1964 film Dr. Strangelove, in which actor Sterling Hayden plays this very character.)

To improve process at organizations, we must recognize that workarounds often represent frustration, lack of communication and mistrust. Yet, they are also a fundamental source for improvement: a workaround usually illustrates what stakeholders truly desire. If you need help identifying challenges in your organization, contact Slaughter Development. We help companies realize that passwords set to “all zeros” illustrate that perhaps there is a better way to design access and control.

❖ ❖ ❖

Like this post? Here are some related entries from The Methodology Blog you might enjoy:

Hunting for Energy Treasure - How did GE save $110 million in recurring costs? They sent employees hunting for energy treasure. Read on »
Inefficiency Far from Home - The names might sound unfamiliar, but a recent story in a Pakistan’s newspaper reports on inefficiencies in local community boards that might well be in your own hometown. Read on »
Want to learn more? Register now for the 2011 Productivity Series

One Response to “Cold War Workaround”

  1. Mark Graban Says:

    Thanks for the link. I’m curious to follow what your readers have to say on this. Thanks for building on my points, I agree that the existence of a workaround should prompt leaders to ask “why?” instead of just chewing people out for working around the system.

Leave a Reply

Switch to our mobile site