How Not to Reply All to Forty-Seven People

The Reply All incident follows a predictable pattern. Someone sends a message to a large group. Someone else replies to thank them. Then someone replies to that. Then someone replies asking to be removed from the list. Then someone replies to ask everyone to stop replying. Then someone replies to agree.

By the time it ends, forty-seven people have received twelve emails about nothing.

Why Reply All exists

Reply All is a useful feature. When a group of people needs to see a response — because they are all making a shared decision, or because the correction affects everyone — Reply All is the right choice.

The problem is not the feature. The problem is using it when a reply to the sender would do.

The five questions before you hit Reply All

• Does everyone on this list need my response? If not, reply to the sender only.
• Am I only saying thanks, congratulations, or "noted"? If yes, reply to the sender only.
• Is my reply correcting something everyone received? If yes, Reply All may be appropriate.
• Does everyone need to weigh in on a shared decision? If yes, Reply All may be appropriate.
• Am I about to add to a Reply All chain that is already out of control? If yes, do not reply at all.

The acknowledgement problem

The most common Reply All mistake is the acknowledgement. Someone sends an announcement to the whole team. You want to say thank you. You hit Reply All.

Now forty-seven people have received your thanks. Most of them did not need it. Some of them are now annoyed. One of them will reply to ask everyone to stop replying, which will make things worse.

Reply to the sender. Or do not reply at all. The sender knows you received the email.

When the chain has already started

If you are in the middle of a Reply All chain that has gotten out of control, the answer is almost always to stop replying. Adding a message asking everyone to stop replying is itself a Reply All. It makes things worse.

The chain will end on its own. Let it.