|
In case you TL;DR, the takeaway: - Keep it "concise", "ascribed", and "specific". By concise, avoid irrelevant details; by ascribed, write necessary data even though it's obvious but saves time for the reader by not having to look up, i. e., complete date mm-dd-yy instead of yesterday/tomorrow, links for references; by specific, avoid ambiguity, separate lines for each required query. - Use proper text formatting, i.e, <bold> important texts, wrap links with titles. - Divide long email into separate paragraphs, each can contain its subject. i.e., the way most SaaS services publishes postmortem about an outage or vulnerability. Note: I've read many articles on writing good emails, this article focuses on the technical team, which in itself follows its guidelines. |