What a meeting follow-up needs to preserve

A recap email is meant to close a meeting. Some extend it instead. The meeting ends, and within the hour a summary arrives that restates the agenda, walks through each point discussed, notes who said what, and closes with a paragraph on next steps, sent to people who were in the room and already have this information.

This is a common example of over-explanation, a related behaviour rather than one of the three named patterns. Context and record-keeping can be genuinely necessary; the issue is accumulation, where background or repetition continues after the reader already has what they need to act.

What a follow-up needs to preserve

The part of a meeting most likely to be forgotten or disputed later is usually the smallest part: decisions made, actions assigned, and dates attached to those actions. A follow-up that states these clearly does the essential work. Everything else, the discussion, the reasoning, the back and forth, served its purpose during the meeting itself.

A message that lists a small number of decisions and owners is also more likely to be read carefully in full. A longer recap is often skimmed, and decisions inside it can carry the same visual weight as the material around them.

When a fuller record is appropriate

This is not a case for minimalism regardless of context. A fuller written record may be necessary where a stakeholder was absent and needs the background, where the work is subject to regulatory or compliance record-keeping, where a decision is contested and the reasoning matters, or where the subject is complex enough that a bare decision list would be ambiguous without it. Professional judgement about the situation should govern the level of detail, not a fixed rule about length.