To summarise a long thread quickly, read it backwards: the latest messages hold the current state, so start at the end and work up only until the picture is complete. Then pull out just three things, decisions made, actions owed and by whom, and questions still open. Everything else, the greetings, the back-and-forth, and anything that got superseded along the way, can go.
Why reading backwards works
Threads resolve themselves as they go. The date proposed in message two gets moved in message nine; the plan everyone debated for a week gets dropped in a single line near the end. If you read from the top, you spend most of your effort absorbing positions that are already dead, and you have to hold them all in your head until the thread tells you which ones survived. Reading from the bottom flips that: you learn where things stand first, then skim upwards only to fill gaps, like who committed to what, or why a decision changed.
The three things worth extracting
- Decisions: what was actually settled, one line each.
- Actions: who owes what, and by when if a date was given.
- Open questions: what is still undecided, and who is waiting on whom.
Everything else in the thread is scaffolding. Twenty messages of discussion usually collapse into two decisions, three actions, and one unresolved question. If a line does not change what someone would do or say next, it does not belong in the summary.
Summarising for someone being looped in
When you forward a thread to a colleague with a summary on top, resist the urge to recount the history. They do not need the journey; they need to know what they are being asked to do. Lead with their part: what they need to decide, review, or reply to. Then give one line of context and the current state. If they want the full story, the thread is right there below.
Watch for superseded facts
The classic summary error is quoting a date, number, or plan that changed halfway through the thread. The budget was £4,000 in message three and £5,500 by message eleven; the launch moved from the 12th to the 19th. When a later message contradicts an earlier one, the latest version wins, always. If you are not certain a detail survived to the end of the thread, search for its last mention before you write it down.
Example
Common mistakes
- Summarising chronologically instead of by outcome, so the reader relives the thread instead of skipping it.
- Keeping superseded details, the old date or the old number, because they appeared first and felt established.
- Burying the action items under history, when the actions are the only part most readers came for.
- Writing a summary nearly as long as the thread. If it takes as long to read, it has not summarised anything.