Skip to main content


300 Emails? It was 24 hours!

I would have never thought as a front line manager of a small team that I could receive as much email as I do. It’s so overwhelming, I’ve taken to putting my Out of Office as “Due to the volume of email, I will be deleting all email received in my absence. Please hold important correspondence til my return on 3 January 2024”!

So, how do we communicate to our peers and leaders if they’re also receiving this much email, or multitudes more? I propose a simple solution.

A quick to remember and learn writing template for emails born of years of military correspondence, when seconds mattered, and enough time in the corporate world to know that it’s on me to communicate effectively.

I originally adapted this from a business correspondence course, bolted on some pieces from the Army, and its served me well through out the years. I don’t quite get a 100% response rate, but it’s in the high 90’s.

Take it, modify as it fits your needs and situations and pass it on to those you mentor.

First, the Subject Line:

We’re going to break this down into two parts.

  1. Is an action required?
    If not, now’s a great time to let the leader know. If it’s just informational, make that your first point.

  2. What are we talking about?
    Provide some context up-front. Don’t make me read the entire email to figure out what you’re talking about.

Here’s an example of some of my most recent subject lines.

Confirmation Requested | Add Bob to Security Group $Name?

Informational | Project A Completed Milestone 2

Action Requested | Approve Paternity Leave

Executive Summary | Meeting with Vendor $ABC, LLC

A well crafted subject line can get the entire point across in less than a sentence and is much more likely to get a response from busy peers and leaders.

BLUF, Or Bottom Line Up Front

After the subject line, the BLUF or TL;DR is a restatement of your Needed Action along with a quick 5 W’s (Who, What, Where, When, Why, and How).

Examples might look like this.

BLUF: Before the End of Q1, Junior analysts need to adopt the below email template to communicate more effectively.

BLUF: To prevent threat actors from threat actoring, all users must patch by Tuesday, December 26th.

This should encompass everything that the reader has to know and entice them to read more. If you’ve ever taken a journalism class, you may recognize this as the inverted pyramid format. Consider your Subject line to be a Headline, and the BLUF to be your by-line.

5 W’s

This is where the meat of your email comes into play. Any evidences need to support previous statements, extraneous details, length explanations, etc…

I prefer the below format for End User Notifications, Letters to Executive Teams, Historical briefs, and on and on.

What's Happening?: We're training users to write concise emails. 

Why Is It Happening?: User emails are long and rambling and take up excessive time. 

When?: Today, at 9p.

Who doing it?: The IT Leadership team, assisted by Corp Comms. 

Where?: Virtually, at [Teams Invite](

How?: Instructors will explain inverted pyramid communications to users. Users will practice constructing their own email communications. 

What Should I do?: Attend one of the scheduled trainings. 

Each section should be its own concise header with a few lines of information for the reader.
We don’t want to give a novel, but this is our opportunity to provide information that aids our audience in their decision making, or supports our recommendation.

Popular posts from this blog

LibWebP (CVE-2023-4863)

Here is a non-exhaustive list of possible mitigations to prevent the exploitation of CVE 2023-4863 in the LibWebP library. This library has a heap buffer overflow available across all operating systems, most browsers, an exceptional number of Electron framework applications. This CVE is rated a 10 after previously being rated 8.8. This was due to an original disclosure from Google stating that Chrome was the only effected application. After investigation, it was discovered that all instances of the LibWebP library were vulnerable across all platforms. A similar CVE ( 2023-5217 ) is pending analysis for the VP8 webstream video format (a sister library to libwep.) As working proof-of-concepts are generally available to the public and Google and Apple both acknowledge threat actors and spyware vendors making use of the vulnerability, it is essential that you begin reviewing and patching all business critical applications. Patch Browsers, All of them All major and minor browsers acr

Show And Tell

Once a week, our security team gathers everyone into a meeting and shares the last week’s worth of security related news and any new security initiatives. This one hour may be the most valuable meeting we attend and has the greatest impact on successful security outcomes. What is it? We call ours a Security Show & Tell. (You can call it whatever fun and exciting name fits your corporate culture.) Regardless of the name, the goal is to set aside an hour each week to share three kinds of security stories and our response to them. Stories that are in the news. Stories that impact our work. Stories that impact our lives. Author’s Note: There’s some helpful tips below on how to gather these stories.  Why you should do it There’s a lot of great reasons to do this, but I want to drive home a few really important ones. How many times has this happened to you? You wake up, open , and begin scrolling only to find out that $Vendor has a nasty zero-day and organiza

Savory Dutch Babies

Ingredients: 1/4 Stick butter 1/2C AP flour 3/4C room temp milk 3 room temp eggs Salt pepper mace nutmeg allspice etc if you want it Blend it or whisk it until homogeneous  Put a castiron in a cold oven at 425°.  Remove when preheat finishes and melt in a 1\4 stick of butter.   Pour in batter.  Top with parm and fresh herbs.  Cook 15m.