What Happens to an Email Nobody Can Act On
An email that cannot be acted on is one where the request sits below the context. The reader opens it, scans for what they are being asked to do, does not find it in the first two lines, and closes it to deal with later. Later is where most internal delay comes from.
The writer almost always knows what they want and puts it last out of politeness, building the case before making the ask. That order works in a letter and fails in an inbox of ninety messages, because the reader is triaging rather than reading. Kept out of the video entirely is any real correspondence: internal threads used as examples have to be rewritten as fictional, because a training module circulates for years and the people in the thread did not consent to be a case study.
The module is set out across nine scenes: one on how a work inbox is actually processed, two on subject lines that survive scanning, two on putting the request first and the context after, one on the deadline and what makes one credible, one on tone in short messages, one on when not to send an email at all, and one on the reply that closes a thread.
.PNG)
.PNG)
.PNG)
