Email Culture: How to End Email Overload and Build Team Productivity and Accountability
By Joe Newsum
The single biggest productivity gain available to most companies is sitting in their inbox, untouched. Email is the biggest time suck in the building. It is the thing people complain about more than anything else, the flood of threads they get dragged onto and never needed to see, the reply-all pile-ons, the asks that vanish into the pile. Everyone knows it is broken. Almost no one fixes it. And here is the part that should make every leader sit up: the fix is the simplest and easiest thing I will ever hand you. Not a tool. Not a reorg. Not a six-month change program. A handful of shared commitments, adopted by everyone at once, that take about a week to take hold.
The Real Definition of Email Culture
Email culture is the set of shared habits a team brings to email: how they write it, send it, respond to it, and manage it. Left to chance, a hundred people develop a hundred ways of writing, and every reader decodes every sender. Built on purpose, with a few shared commitments, email becomes fast, clear, and accountable.
The root of the mess is that decode tax, paid on every message, all day, every day. Give everyone the same way to write, and the tax goes to zero. I have rolled out these commitments with team after team, and they work fast, because the only way they work is fast. Everyone flips the switch together. And once people start, it is close to magic, because a good email is a written, dated promise. The moment one asks for something by a date, the receiver has to answer: yes, or not by Friday but by Monday. Either way, it is on the record, which is why email drives accountability like almost nothing else. Conservatively, my clients are seeing 15-30% fewer emails and 20-35% less time lost to the inbox, which across an organization frees up thousands of hours and hundreds of days a year to spend on the work that actually matters.
This is not a small leak. The average professional handles around 121 emails a day and loses roughly 28% of the workweek to email, about eleven hours, more than a full workday gone every single week. Only about 38% of those emails actually need a response. The rest is noise, reply-all, and unnecessary CCs. Email overload is the single biggest self-reported drain on team productivity, ahead of meetings. The biggest complaint and the biggest opportunity are the same thing. Sources: Radicati, McKinsey, Atlassian.
Watch the tax in action. An email lands with the subject line “Quick question,” and nine paragraphs below it, somewhere, is a request that needed an answer two days ago, except you cannot tell if it is for you or the four other people on the thread. That is the decode tax. Now the same email, built: [Action] Approve the Q3 budget by Thursday. Two sentences of ask, one of context, done. The reader acts in ten seconds. Multiply that difference across every email a hundred people send, and you have either an execution machine or a fog of interpretation and quiet non-accountability.
This is a different kind of activity domain than most. With meetings or feedback, a team has real choices to make about its own commitments. With email, the right answers are basically solved. A fastener distributor, a law firm, and a software company should all write email the same way, because the physics is identical everywhere: a reader is trying to extract an ask from text. So this page is not a design exercise. It is the system, ready to adopt. Here are the commitments. Flip the switch.
The Mechanism: How Email Builds Culture
Email culture is built the same way every culture is built, through a simple chain. The language people use shapes how they think, and thinking shapes how they behave. And behavior, repeated across a team day after day, becomes culture.
Most attempts to fix email work the wrong end of that chain. They send a tips memo, or buy a tool that uses AI to decode the mess after it arrives, which is a quiet admission that the writing itself is broken. The leverage is at the front of the chain, in the actual words people put in the subject line and the first two sentences. Change the language a team writes in, and you change how the team thinks, acts, and ultimately performs. A shared email system is shared language, and shared language is how you build a culture on purpose.
The Email Commitments: One System, Four Moments
The whole system fits the natural life of an email: before you send it, when you write it, when you receive it, and how you keep your own inbox. None of these is complicated. The power is that everyone holds the same ones, so the language becomes predictable and the decode tax disappears. Here is the whole system on one page. Screenshot it, paste it in the team channel, and start. The four sections below take each moment in turn, with the commitments and the reason each one works.
1. Before You Send: Earn Their Time
Before you send is where the waste begins, or does not. Every email is a withdrawal from other people’s attention, and most of us spend it like it is free: copying half the team to be safe, stacking three asks into one thread, firing off a message that should have been a thirty-second question. The sender saves a few seconds and everyone downstream pays for it, over and over, all day. This first moment is pure restraint, and it is the cheapest place in the whole system to save the most time, because the best email is often the one you never send.
Send to the minimum viable people. To means I need something from you. CC means awareness only, no reply needed. Every unnecessary recipient pays with their time, and over-CC is one of the biggest sources of inbox volume there is.
One topic per email. Two topics means two emails. A single thread that tries to do three things gets none of them done cleanly, and becomes impossible to close.
Pick the channel before you default to email. Email is for a clear ask that needs a record. Before you send one, ask whether something else would resolve it faster: a quick chat or a Slack message for a one-line question, a two-minute call or a meeting with a goal for anything that needs real back-and-forth. If a thread is about to run three rounds deep, it was a conversation all along. The fastest email is the one a thirty-second chat made unnecessary.
Why It Works
Attention is the one resource email spends without a budget. Every name on the To and CC line pays a processing cost, so a thread sent to twelve people burns twelve people’s time whether they needed it or not. There is also a quieter effect: when an ask goes to a crowd, everyone assumes someone else owns it, and nobody acts. Psychologists call it diffusion of responsibility, and it is why a request sent to five people often gets answered by none. Sending to the fewest who need it, one topic at a time, makes ownership unmistakable and strips out the volume everyone else has to wade through. The research is blunt about the upside: eliminating unnecessary copies and forwards alone can cut total email volume by roughly half.
2. Writing It: Bottom Line Up Front (BLUF), in the Subject and the Body
A buried ask is a tax, and every reader pays it every time. The point of the email is in there somewhere, under the throat-clearing and the backstory, and the reader has to dig for it, on your message and the next one and the forty after that. Picture the most expensive people in the building spending their morning re-reading nine paragraphs to find the one sentence that needed them. This is the moment where that stops. Get the writing right and an email becomes something anyone can read and act on in ten seconds. It comes down to one principle applied in two places: bottom line up front, known as BLUF. The subject line is BLUF in its purest form, the bottom line placed in the most up-front real estate there is, before the reader even opens the email. Then the first two sentences of the body lead with that same bottom line again, before any context. Same move, twice, in the two places a reader looks first.
Start with the subject. Tag it so the reader knows what is needed before they open it. Three tags, and almost every team should just use these three:
[Decision] Choose or approve something.
[Action] Do something, and you can sub-type it as answer, review, send, or do.
[FYI] Awareness only, nothing needed.
Three is the standard. If your team genuinely needs one more, add it carefully, because every tag you add is a tax on the reader and a judgment call for the writer. The whole point is to remove interpretation, not move it upstream.
BLUF the subject line: tag, ask, when. The subject line is the email. “[Decision] Approve the new vendor contract. Need by Friday” puts the whole bottom line up front, before the reader opens a thing. The body just carries the context.
BLUF the body. Open with the ask and its date in the first two sentences. Context comes after. This is the same principle as the subject line, one level down, and it forces you to synthesize the point so the reader does not have to dig for it.
Write for the skim. If the reader sees only the first two lines, the email should still work. Detail goes to the attachment. The body makes the case in a few sentences.
Every ask has a when. “When you get a chance” is not a when. A date is what turns a message into a commitment.
Optional, for functional teams: one secondary tag. The three primary tags answer one question, what do you need from me. A functional team can add a second axis that answers a different question, what is this about. It stacks after the primary tag and routes the work: a sales team might add an account or segment, “[Action][Acme]” or “[Decision][Enterprise]”; an operations team an issue type, “[Action][Expedite]” or “[FYI][Quality]”; a support team a category, “[Action][Billing]”; finance a workflow, “[Decision][Budget].” Now the reader sees both signals before opening, what you need and what it concerns, and a salesperson can filter every Acme thread while an ops lead can see every expedite at a glance. Over time the secondary tag becomes data: “we are drowning in expedite emails” turns from a feeling into a number.
This only stays an asset if it inherits the same discipline as the primary tag. One secondary tag, never a stack, primary plus one. It comes from a short, shared, closed list the team agrees on up front, four to eight categories that map to how that function actually divides its work, with boundaries instant enough that nobody hesitates over which to use. And it is defined by the function, not the company: the whole company shares Decision, Action, and FYI, but sales defines its own secondary layer and operations defines a different one. The primary tag keeps the organization legible across every team; the secondary tag lets each team route its own world. The core system is still just the three tags, and most people can adopt those and stop. This is the layer for teams that want it.
The tags are an internal protocol. The writing is universal. Tagging only works when everyone shares the convention, so the tag system is for internal email. You would not put “[Action]” in the subject line to a customer or vendor, it reads as cold or presumptuous to someone outside your norms, and informal tags across organizations just create confusion. So externally, drop the tags. But keep everything else, especially BLUF. A customer, a vendor, a partner all want the same thing your colleagues want: the ask up front, one topic, a clear date, a body they can skim. The protocol is internal. The clarity travels everywhere.
Why It Works
BLUF matches how the brain reads under load. When the ask comes last, the reader has to hold every line in working memory while hunting for the point. When it comes first, they can act and stop. Putting the bottom line up front also forces the writer to actually know their ask, which is the real work, and the part most people skip.
It is not a new idea. The U.S. Army formalized BLUF in its correspondence regulation, with the principle that writing is action-oriented and states its purpose in the first sentence, because in the military a buried message can be the difference between mission accomplished and mission failure. If the highest-stakes, most time-compressed environment on earth puts the bottom line first, the rest of us can manage it for a budget approval. One modern bonus: AI systems pull the first clear answer they find, so a team that writes bottom-line-up-front is also writing the way the next generation of tools reads.
3. Receiving and Responding: A Date, or a New Date
This is the half of email almost everyone ignores, and it is exactly where things fall through the cracks. Sending well is only ever half a conversation. The other half is what happens when the email lands, and that half is where work quietly dies: the message that sits unanswered for three days, the date that slips with no word, the thread that just trails off and leaves the sender wondering whether anything is happening at all. Almost no email advice covers the receiver. Yet this is where I see teams change the most, because once people commit to how they respond, the dropped balls stop. A good email culture has commitments for the receiver, not just the sender.
Respond within a day. A clear ask deserves a reply within roughly twenty-four hours, even if it is just “got it, you’ll have it Thursday.” Silence leaves the sender guessing and the work stalled.
Hit the date, or name a new one out loud. This is the heart of it. If you cannot get it to them by Friday, do not go quiet. Say when you can: “not by Friday, but by Monday.” A renegotiated date is a kept commitment. A missed date in silence is a broken one.
Flag a slip before it lands. The moment you know you will miss a date, tell them. Late notice is a courtesy. No notice is a failure of accountability.
Reply to who needs it, not to all. Reply-all is the default that quietly multiplies everyone’s inbox. Reply to the people who actually need the answer.
Close the loop. When it is done, say so. The thread ends when the loop is closed. An open thread is invisible waste, the sender never knows if the ask landed.
The Core Idea
A good email is a written, dated, two-sided commitment. The sender asks for something by a date. The receiver accepts it, or names a new date. Either way, it is on the record.
Why It Works
This is where email stops being a writing style and becomes an accountability system, and it is the reason email drives accountability like almost nothing else. A meeting commitment lives in the room and fades. An email commitment is written down, addressed to a named person, with a date attached, and visible to both sides. When the subject says “[Action] Send the budget by Tuesday,” the receiver cannot quietly let it drift. They have to do one of two things: hit the date, or say “not Tuesday, but Thursday.” That forced choice, accept or counter, is the whole accountability engine, and it runs both ways: the sender commits to a clear ask with a real date, the receiver commits to honoring it or renegotiating out loud. It is the email version of deciding and owning it, clear ask, named owner, real date, on the record.
Closing the loop has its own logic. An open, unfinished task keeps nagging at the mind and quietly consuming attention until it is resolved, an effect known as the Zeigarnik effect. “Close the loop” is not just courtesy, it lets both people stop carrying the thread and put the attention somewhere useful.
4. Managing Your Inbox: A To-Do List, Not a Filing Cabinet
This is the hardest moment to sustain and the easiest to let rot. Sending and writing well are visible, public acts; how you keep your own inbox is private, so it is the first thing to slide when the week gets busy. And a rotting inbox is invisible: nobody sees the four hundred unread, the asks buried twelve deep, the work quietly going missing, until something important falls through and no one can say how. Keep this moment and the opposite becomes true, the work stops hiding. It is also where one of the biggest benefits in the whole system lives, the one almost nobody names.
Your inbox is a to-do list. If it is in the inbox, it still needs an action from you. Everything else gets filed or archived the moment you have read it. An inbox of four hundred “read but kept” emails is four hundred decisions you keep re-making.
Keep a “waiting on” view. The asks you have sent where the loop is not yet closed live in one place. Review it weekly and nudge the date. This is how you hold others to their commitments without it living in your head.
Let search do the filing. Do not build elaborate folder trees. A flat archive plus search beats a filing system you have to maintain.
The hidden benefit: a manager can see the real work. When everyone’s inbox is a clean to-do list, a manager can glance at it and see the actual workload and status, the live work in flight, instead of asking “what are you working on?” and getting a curated answer. The inbox becomes a real operations dashboard. This is enormous in high-volume operations where email is the engine, the distributor, the support desk, the ops team where the work arrives and moves by email. The catch is that it only works if everyone stays organized, which is exactly why this is the cluster that takes the most discipline and pays back the most.
One thing that does not matter: your exact folder structure. Build whatever fits how you work. What matters is that you actually keep it. If you want a starting point, the cleanest setup I have seen is simple, a folder for completed actions, an FYI folder, a folder per major customer or account, and an “other” catch-all, with everything live still sitting in the inbox itself. And use the features your email client already gives you, flags, categories, priorities, and rules can automate a lot of the sorting. The exact features vary by tool, so learn the few your team uses and let them do the work.
Why It Works
An inbox of four hundred read-but-kept emails is four hundred decisions you re-make every time you scroll past them, and re-deciding the same thing is its own tax, a drain on the judgment you need for real work. Treating the inbox as a to-do list means each message is decided once: act on it, file it, or delete it. The “waiting on” view does the same for the asks you have sent, it moves the tracking out of your head and onto the screen, so you are not spending attention remembering who owes you what. And letting search do the filing kills the wasted effort of building folder trees you will never reliably maintain. A clear inbox is not tidiness for its own sake, it is a clear mind, and it is what keeps the other three commitments from quietly slipping. And when everyone keeps theirs, the team gains something it never had: a shared, visible picture of the real work, which is why this unglamorous cluster is often the one leaders value most.
Watch Out for These Things
A system this clean is strong medicine, and strong medicine has a few side effects. The point is not to BLUF every message into a blunt instrument. It is to be clear, and clarity sometimes means context first. Four cautions.
Do not BLUF bad or sensitive news. Leading with “the project is dead” reads as cold and lands badly. For hard news, give a sentence of context first, then the bottom line. Clarity and care are not opposites.
Do not let tags multiply. Three tags is the standard for a reason. The moment a team is debating whether something is a [Request] or an [Action] or a [Sign-off], the system has started taxing the writer instead of freeing the reader. Resist the urge to add tags.
Do not use email for everything. A great email culture also knows when not to email. Quick coordination belongs in chat. A real debate belongs in a conversation. Email is for the clear ask with a record, not the running argument.
Do not enforce it as a policy. These are commitments a team makes to each other and models from the top, not rules with disciplinary teeth. People resist policies and adopt commitments. The switch gets flipped because leaders write this way first, and because anyone can hold anyone to it, gently, regardless of rank.
How to Roll It Out and Make It Stick
This is where most of the value is won or lost, so do not shortchange it. Cleaning up email is plausibly the single largest productivity gain available to a knowledge-work team, a fifth of the workweek sitting right there, and you get one good shot at the switch. The system is simple, but simple is not the same as automatic. The day you flip the switch is the easy ten percent. The weeks of reinforcement after are the ninety percent that decides whether you built a new way of working or just sent a memo everyone forgot by Thursday. So pour energy into the launch and the weeks that follow, not just the announcement.
Email commitments also have to be adopted by everyone at once. They do not work as a personal habit, because the value is in the shared language, and shared language only exists when the team shares it. One person tagging subject lines into an untagged inbox is just talking to themselves. The whole team flips the switch on the same day, which is exactly why the run-up and the follow-through matter so much. Build it on the same three moves that make any culture change stick: people have to see the commitments, use them, and have them reinforced, until they own them.
Before the Switch: Get People Ready to Flip It
You cannot just announce new rules on Monday and expect them lived by Tuesday. People have to understand the system, see why it matters, and practice it before the switch, so that on day one they are ready, not surprised.
Leaders align and commit first. This cannot be delegated to operations. If the leadership team has not agreed to write this way themselves, stop here, because the moment a leader sends an untagged “Quick question,” the system is dead. Leaders adopt it first, together, out loud.
Make the case, with the number. Show the team the cost: a fifth of the week, the decode tax, the dropped asks. People flip the switch willingly when they feel how much time the old way is quietly stealing from them.
Train it by doing, not by telling. Run a working session, not a slide review. Have everyone open their sent folder, pull a real email from last week, and rewrite the subject and first two sentences with tag, ask, and when. Read a few out loud. The before-and-after on their own email is what makes it click, and it is the practice rep that makes day one feel familiar.
Write the commitments down and pick the date. Agree the specific commitments as a team, the tags, the response window, what closing the loop means here, put them on one page, and name the day everyone starts.
The Switch: Everyone, the Same Day
On the start date, the whole team turns it on at once, leaders first and most visibly. From the first morning, every email anyone sends is tagged, bottom-lined, and dated. Because the team practiced, this feels like switching to a habit already rehearsed, not learning one cold. The shared language exists from hour one, so the decode tax starts falling immediately and people feel the lift the same week.
After the Switch: A Tsunami of Reinforcement
This is the part that makes it permanent, and the part everyone underestimates. A launch without weeks of reinforcement fades back to the old habits inside a month. The job now is to flood the team with reinforcement and stories until the new way is simply how email is done here, and a sloppy email feels out of place.
Reinforce in the moment, both ways. When a great tagged, dated email lands, say so. When one slips back to the old way, anyone can gently call it, regardless of rank, “no date on this one.” Reinforcement is not a memo, it is hundreds of small, in-the-moment nudges and nods.
Tell stories, relentlessly. The thing that landed in two minutes instead of three days. The decision that did not slip because the ask had a date. A steady tsunami of small wins is what builds the social proof that pulls the fence-sitters in and leaves the holdouts no room to hold out.
Run a cadence of check-ins, then calibrate. Tight at first, ten minutes weekly for the first month, then spacing out. Early on, people will use the tags slightly differently, one person’s [Decision] is another’s [Action]. A calibration pass or two keeps the language genuinely shared instead of drifting into private dialects, which is the quiet way a tag system dies.
Tune the commitments. For the first month or two the system is alive. Maybe the response window was too aggressive, maybe a team wants a secondary tag, maybe one commitment is not landing. Adjust it together. A commitment the team refines is one the team owns.
Use the Data: A Weekly Scorecard
Email is one of the few culture domains that comes with its own hard numbers, so use them. You can measure emails sent, average recipients per email, average length, and how full inboxes are running, the exact things the commitments are designed to move. Turn that into a simple scorecard and send it to the team every day or every week.
The scorecard is the reinforcement engine. It makes the invisible visible: recipients per email ticking down as people right-size the to-line, average length dropping as BLUF takes hold, inbox counts falling as people treat the inbox as a to-do list. Watching the numbers move is its own motivation, it turns the rollout into a visible win the team can rally around, and it surfaces backsliding early, while it is still a nudge and not a relapse. A number that is sliding the wrong way is a calibration conversation waiting to happen.
That is the rollout. The commitments are simple and the switch is fast, but the energy you put into readying people, then flooding the weeks after with reinforcement, stories, and a scorecard, is what turns the biggest easy productivity gain on the table into a permanent change in how your team works.
And that completes the three daily activities: meetings, feedback, and email, the places where culture is practiced every single day. If these commitments have you seeing what deliberate culture-building can do, the full method is where to go next. Read next: Culture by Commitment, the system behind every page in this guide.
Free Download
The Email Commitments Starter Deck
The whole system in 15 slides: the four moments, the three tags, BLUF, the subject-line examples, and the rollout. Screenshot it, walk a team through it, or run it as a workshop. Yours to use.
Work with Joe
Want to build an email culture that turns your team into an execution machine?
Email is one of the fastest, highest-leverage places to change a culture, because it repeats constantly, it is written down, and the right system is the same everywhere. I help leadership teams roll out email and meeting commitments that take hold in days, not quarters, and reclaim a real share of the workweek.
If you want to flip the switch with your team and make it stick, let’s build it.
See How Joe Works with Clients
Or email Joe directly at joe@stratechi.com
And follow Joe on LinkedIn for new content and insights.
Joe Newsum: McKinsey alum, former CEO, COO, CFO, and CMO, and creator of Culture by Commitment, working directly with Fortune 500 CEOs and executive teams to build cultures that hold.
Part of the Culture Guide
This is one piece of a complete, free guide to building a high performance culture. Start at the Culture Guide hub for the full system, or jump to the ideas most worth your time:
|
Culture Strategy ›
The strategy: deriving the culture your business needs from your True North, your advantage, and the behaviors that win.
|
|
Culture by Commitment ›
The method behind this page: how shared commitments, not values, actually build culture.
|
|
What Is Organizational Culture ›
The big idea: it was never values, it was always language. Why most culture work fails.
|
|
How Language Creates Culture ›
The mechanism: language shapes thinking, thinking shapes behavior, behavior becomes culture.
|
|
The Four Types of Culture Commitments ›
The framework: the four kinds of commitments that build culture, and where meetings fit in.
|
|
How to Make Culture Change Stick ›
The proof: concentrate, model, and reinforce until the new way holds on its own.
|
Frequently Asked Questions
What is email culture?
Email culture is the set of shared habits a team brings to email: how they write it, send it, respond to it, and manage it. Left to chance, a team of 100 develops 100 different ways of writing email, which forces every reader to decode every sender. Built on purpose, with a few shared commitments, email becomes fast, clear, and accountable.
How do you build a good email culture?
Adopt one shared system and have everyone start at once. The core commitments are simple: tag the subject (Decision, Action, or FYI), put the ask in the first two sentences (BLUF), give every ask a date, send to the fewest people who need it, respond within a day or name a new date, and close the loop when it is done. The system only works when the whole team flips the switch together.
How do you reduce email overload on a team?
Email overload is mostly a writing and norms problem, not a volume problem. Cut it by sending to the fewest people who need it, one topic per email, and replacing unnecessary CCs and reply-all with reply-to-who-needs-it. Research shows eliminating unnecessary copies and forwards alone can cut total volume by roughly half. Then make every email faster to process with BLUF and subject-line tags. Adopted across a team, this typically cuts both email volume and time spent on email.
What is BLUF in email?
BLUF stands for bottom line up front. It means putting the ask, the who, and the when in the first sentence or two, before any context. It comes from U.S. military correspondence, where a buried message can mean a failed mission. BLUF forces the writer to synthesize the point so the reader does not have to dig for it.
What is the BLUF email format?
The BLUF email format has three parts. The subject line carries the tag, the ask, and the date, for example “[Decision] Approve the new vendor contract. Need by Friday.” The first two sentences of the body carry the bottom line: the ask and its date, before any context. The context comes after, and any detail goes to an attachment. Done well, the whole email is four sentences and the reader can act in ten seconds.
What are the three email tags?
Decision, Action, and FYI. Decision means choose or approve something. Action means do something, often sub-typed as answer, review, send, or do. FYI means awareness only, no response needed. Tagging the subject line tells the reader what is needed before they open the email. Three tags is the standard, and almost every team should just use it.
How does email drive accountability?
Because a good email is a written, dated, two-sided commitment. The sender makes a clear ask with a date. The receiver either hits the date or names a new one out loud, “not by Friday, but by Monday.” That handshake is on the record and the clock is visible to both people, which is why email drives accountability like almost nothing else.
Email commitments vs. an email policy: which works better?
Both try to fix team email, but they work differently. An email policy is a set of rules imposed and enforced, often with disciplinary weight, and people tend to resist rules. Email commitments are shared agreements a team makes to each other and models from the top, reinforced by open accountability rather than enforcement. Commitments are more durable because people adopt what they choose and own, and resist what is imposed. The behaviors can look similar; the difference is whether the team owns them.
What should your email inbox look like?
Your inbox is a to-do list, not a filing cabinet. If something is in the inbox, it still needs an action from you. Everything else gets filed or archived the moment you have read it. Keep a separate “waiting on” view for the asks you have sent where the loop is not yet closed, and review it weekly.
Can sales or operations teams add their own email tags?
Yes, through one optional secondary tag. The three primary tags (Decision, Action, FYI) stay universal across the company and answer “what do you need from me.” A functional team can add one secondary tag that answers “what is this about,” such as an account or segment for sales, an issue type like expedite or quality for operations, or a workflow for finance. It stacks after the primary tag, for example “[Action][Expedite].” Keep it to one secondary tag from a short, shared list the team agrees on, so it routes work without recreating the noise.
Does this work for external emails to customers and vendors?
The writing principles do, the tags do not. Tagging only works when everyone shares the convention, so the subject-line tags (Decision, Action, FYI) are an internal protocol. Putting “[Action]” in an email to a customer reads as cold or confusing. Externally, drop the tags but keep everything else, especially BLUF: lead with the ask, one topic, a clear date, a body they can skim. Customers and vendors want the same clarity your colleagues do.
How do you measure email culture?
Email is one of the few culture domains with built-in metrics. Track emails sent per person, average recipients per email, average email length, and inbox volume, the exact things the commitments are designed to improve. Turn them into a simple scorecard and send it to the team weekly. Watching recipients-per-email and length tick down, and inboxes empty, reinforces the new habits and surfaces backsliding early, while it is still a nudge.