Collection · 5 articles
Summaries.
A summary is a small idea with a large consequence. If every conversation arrives carrying a plain line about what it is, then reading an inbox stops meaning opening an inbox, and the twenty seconds you spend working out what a thread is become nothing at all. These guides cover what that is like in practice: what a summary actually carries, how a full inbox gets skimmed in minutes, what happens to a chain of forty replies with an attachment somewhere in it, and what a summary does when you correct it. Written for someone deciding whether reading less is the same as knowing less.
-
A plain summary of every email, before you open it
A summary email is two things, the recap you send after a meeting and the account of a thread you have not read. What the second one has to carry.
-
How to skim a full inbox in minutes
Skimming means deciding about every conversation without opening one. What the pass costs in minutes, how to run it, and which threads you open anyway.
-
One summary for an email thread, its files and tasks
Managing tasks out of email fails when the task leaves the conversation behind. What one account of a thread, its attachments and its tasks has to carry.
-
How to catch up on a long email chain
A forty-message chain is not a long email. It is a history with a current position. What a summary of one has to carry, and which messages to read.
-
When a summary learns from the corrections you make
An edit fixes one summary. A correction that is kept fixes every summary after it. What is worth correcting, how to say it, and how to tell it stuck.