Search

Blog Entries:

Some posts from The Methodology Blog around the time of Reply-All for Gridlock

Archives by Subject:

More Resources

Reply-All for Gridlock

Monday, January 12, 2009 by Slaughter Development

State Department employees have been warned not to use the “reply-all” feature on their email programs, as a recent message storm nearly took down a major internal communication systems. According to the Associated Press, an accidental press of the shift key will invoke unspecified “disciplinary actions.”

Responding to an email may only take a few seconds, but every address in the To, CC and BCC line corresponds to a new copy of the message. Sending one note to a thousand people already taxes resources. If even only a handful fire back using “reply-all”, thousands upon thousands more pile onto the servers all at the same time. More expert users contributed to the issue when they used “reply-all” to inform others not to use “reply-all” in the future. The AP explains that the onslaught of messages began with a mistake:

Officials said the storm started when some diplomats used the “reply-all” function to respond to a blank e-mail sent recently to many people on the department’s global address list.

Most demanded to be removed from the list while others used “reply-all” to tell their co-workers, in often less than diplomatic language, to stop responding to the entire group, the officials said.

Some then compounded the problem by trying to recall their initial replies, which generated another round of messages to the group, they said.

When organizations like the State Department suffer from embarrassing technical foul-ups, it is easy to laugh and crack jokes about government bureaucracy. The real failing in this story, however, is not with the individuals who should have used  “reply” instead of “reply-all.” Management should never create giant distribution lists which anyone can use, as there is no reason for every employee to have the ability to fill a thousand inboxes with a few errant keystrokes. Likewise, reacting to a technical failure by admonishing and threatening employees will only build apathy and discontent. When both of these components appear in the popular press, the average citizen will likely attribute the story to incompetence.

The technology of email servers is complex, but the patterns of workflow that should define policies, procedures and system settings need to be clear to all key stakeholders. Tools for communication should encourage positive interaction and make it difficult for people to accidentally consume resources and waste time. Our own perspective on email surprises many people because we use it for coordination, not discussion. If your company or organization has floundered under a cascade of “reply-all” messages or seeks to improve the methods of work and workplace communication, reach out to Slaughter Development. We help businesses change their culture for the benefit of all stakeholders.

❖ ❖ ❖

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

I Hate Out Of Office - Last month, I ranted about Google Priority Inbox. So this month, I’m taking on another “feature” of email I despise: the out-of-office message. Read on »
Fire Protection Workflow - Every week, Muncie, Indiana firefighters dutifully submit maintenance reports to headquarters. Until last month, this was done by hand—by actually driving fire trucks across town to deliver the paperwork! Read on »
What Google Should Do - Last week, I explained why Google’s new Priority Inbox feature was a terrible idea. This week, I’ll explain what they should do instead.
Read on »
Want to learn more? Register now for the 2011 Productivity Series

Switch to our mobile site