Thought of Crumpet's

Conventional Email

Introduction

There are Conventional Commits and Conventional Comments for code reviewing, an activity done by programmers, which help smooth the protocols required to focus the activity on what it is intended to be for (one person trying to get another person to understand the proposed code changes) and try to avoid pitfalls in communication that otherwise slow, distract, or derail the point of the exchange in the first place.

This is my quick n dirty guide to how you can approach this with your emails. Or at least how I approach it with my emails.

Instructions

Subject Lines

  1. Tag your subject line with an [Action Required], [Response Required], [Question], or similar common prefix so recipients can see the basics of this email without even having to open it.

Sample Subject Prefix Tags

Tag Purpose Notes
[FYI] This email is for your information, I don't expect a response from you.
[FYI-CC] This email is for your information if you are CCed.
[A/R] / [Action Required] This email is being sent to you because some action is required on your part in the opinion of the sender. If you include this, be sure to specify what will happen if no action is taken by a certain time, so readers can choose to accept to take no action if they are so inclined.
[Question] This email has a request for you to read and answer a question.
[Request] / [Response Requested] This email has a request of you that can be solved by replying to it. Try not to conflate response requests (can be handled with just an email reply) with action requests (something outside email replies).
  1. You may have multiple tags for different audiences ([A/R-to], [FYI-CC]), but try not to go overboard (more than 3) with prefixes

  2. When email thread responses muddy-up the original prefix tags on the email, either start a new thread with new tags and note in prose that you are continuing from a previous thread in this new direction, or consider adding a [RT#] prefix tag to the reply all so that readers can understand what generation of tags this refers to. 3a. The # should refer to a monotonically increasing number (1, 2, 3). 3b. If you get beyond 2 retags, that is a strong signal that this thread is getting a bit long in the tooth, strongly consider breaking off chunks of conversation into a new email thread. In the new thread, note that you are splitting that conversation off, and reply to the original one noting the new subject line.

Email bodies

  1. Consider using plaintext email where possible. While technical users prefer it, in strictly corporate communications and other areas, that may not match the audience expectations of the email.
  2. Decide whether you are using bottom-posting (good for long-lived threads, for 'forum style thread viewing') or top-posting (Outlook, Gmail, common popular email client defaults) defaults, then stay consistent with that audience. Teams may be internally bottom posting but top-post to the outside world, this is tricky. Again, know your audience.
  3. Link to meetings, online resources, IM threads, and other external resources, even if the reader could theoretically go look that information up by searching or hunting on their own, make it easy for them to just click to access the information. Most of the time, they won't even do that, so if you 'need' them to click and read that information, quote or screenshot it right in the email.
  4. Just like with powerpoint presentations, keep your message as short and direct as possible, providing enough niceties to not offend your intended audience.
  5. Consider including a BLUF in your email, if it is particularly lengthy.
  6. If an email is not containing sensitive information, consider moving the non-essential information (that you still want to be reviewable at a later date) to a linked explanation or appendix such as a corporate wiki article, 'public' online document to anyone who has the link (which is in the email), attached email document, or other place of holding longer-but-not-immediately urgent information without requiring it to be in the email subject body.

External Related links

  1. Netiquette RFC
  2. https://subspace.kernel.org/etiquette.html
  3. https://useplaintext.email/#etiquette
  4. https://people.kernel.org/tglx/notes-about-netiquette
  5. https://en.wikipedia.org/wiki/Etiquette_in_technology#Netiquette
  6. http://www.catb.org/~esr/jargon/alternates.html

CHANGELOG