You wrote a thorough email. It covered the background, the current situation, the three options, the recommendation, and the next steps. It took forty-five minutes to write. It was comprehensive. It was clear. It was five hundred words.

The recipient read the first two sentences and replied asking a question that was answered in paragraph three.

This is not a failure of the recipient. It is a predictable response to a long email.

Why long emails do not get read

The inbox is a triage environment. People process email quickly, deciding in seconds whether to read, skim, defer, or delete. A long email signals "this will take time" and gets deferred. Deferred often means never.

The important information is buried. Long emails often bury the key point in the middle of the third paragraph. The reader who skims the first paragraph and the last paragraph misses it entirely.

The reader does not know what they are supposed to do. A long email that does not clearly state what action is required leaves the reader uncertain. Uncertainty leads to deferral.

The paradox of thoroughness

The instinct to write a thorough email is good. The execution often undermines the goal. A thorough email that is not read has communicated nothing. A brief email that is read and understood has communicated everything that matters.

How to write a long email that gets read

  • Lead with the point. State the most important thing in the first sentence. Not the background. The point.
  • State the action required. "I need a decision on X by Friday" in the first paragraph. Not buried in paragraph four.
  • Use headers and bullets. Long prose is harder to skim than structured content. If the email is long, structure it so the reader can find what they need.
  • Put the detail at the bottom. Background, context, and supporting information belong at the end, after the key point and the required action.

The test: If someone reads only the first two sentences of your email, do they know what you need from them? If not, rewrite the first two sentences.

Read next

How to Be Brief Without Being Rude

How to Write a Subject Line That Says Something