The Email That Should Have Been a Conversation
And the conversation that somehow became forty-seven replies.
The first email is usually innocent. A question, a small decision, maybe an attachment. Then somebody adds context. Another person is copied in. A third person answers a different part of the question. By the time the thread reaches double figures, everybody is reading a slightly different conversation.
There is plenty written about meetings that should have been emails. The opposite problem gets less attention: the email that should have become a conversation about twelve replies ago.
The subject line now starts RE: RE:. Two people are discussing dates. Somebody else is discussing cost. A person copied in for visibility has asked a new question. The original sender is trying to answer all three without starting another thread.
The point where email stops saving time
A useful rule is not about the number of messages. It is about whether the thread is still reducing uncertainty. If each reply answers one thing and creates two more questions, email is no longer doing the job.
One person thinks the discussion is about whether something can be done. Another thinks the decision has already been made and the question is when. Both replies look sensible on their own. Together they make the thread worse.
Adding somebody can solve a missing-information problem. Adding six people usually creates six new interpretations of the problem. If people are being copied in because nobody is sure who needs to decide, that is a strong sign a short call would help.
FINAL.xlsx, FINAL-2.xlsx and FINAL-approved-new.xlsx can coexist for surprisingly long periods. Once people are discussing different versions of the same file, the email thread has become evidence rather than communication.
Long email chains are bad at carrying irritation, humour and uncertainty. A short sentence can sound abrupt. A careful sentence can sound defensive. People begin replying to the tone they think they read instead of the point being made.
Someone writes “I think there may be some confusion here.” There is. This sentence is the smoke alarm. Stop typing.
What the five-minute conversation needs to do
It does not need to become a forty-five-minute meeting with an agenda. Get the people who can answer the question together, state the decision that is needed, settle the disputed point and send a short written summary afterwards. The email remains useful as the record. It just stops being the place where the argument lives.
Reply-all etiquette is mostly common sense once the thread is under control. Use reply all when everybody genuinely needs the answer. Drop people who no longer need to be involved. Do not copy in senior people as decoration. If you need three paragraphs to explain why the previous three paragraphs were misunderstood, talk to each other.
Email is excellent at records, clear requests and information people need to find later. It is much less good at untangling a disagreement in real time. The trick is noticing when the thing in your inbox has quietly changed from one into the other.