Skip to content

Instantly share code, notes, and snippets.

@masnick

masnick/emails.md

Last active June 3, 2020 09:54
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save masnick/ab95478b0a7956f2c4cb7e5c99096071 to your computer and use it in GitHub Desktop.
Save masnick/ab95478b0a7956f2c4cb7e5c99096071 to your computer and use it in GitHub Desktop.
Download ZIP
A strategy for writing clearer emails
Raw
emails.md

From this HBR article:

  • Start email with single sentence summary:

    Bottom line: This is a better way to write emails informed by US Military practices.

  • Then have a Background section that succinctly provides the necessary context for the "bottom line."

  • Keep the whole thing as short as possible, ideally to avoid the reader having to scoll.

  • Link to files in a shared folder (Dropbox, OneDrive, SharePoint, etc.) rather than sending attachments. This avoids inbox clutter, makes it easy to reference specific files, and ensures the recipient has the newest version of the file.

  • Use one of these tags at the beginning of the subject:

    • ACTION – Compulsory for the recipient to take some action
    • SIGN – Requires the signature of the recipient
    • INFO – For informational purposes only, and there is no response or action required
    • DECISION – Requires a decision by the recipient
    • REQUEST – Seeks permission or approval by the recipient
    • COORD – Coordination by or with the recipient is needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment