Skip to content
Writing Style Library

Email

A business message designed for the inbox scan - subject line doubles as summary, body leads with action, and the reader never needs to re-read to know what is being asked.

Email

Section titled “Email”

Business email is not a letter. Letters open with pleasantries and build toward the point. Email readers scan - they do not read start to finish, and they especially do not read the part before the point. An effective business email leads with the subject line as a compressed summary and opens the body with the purpose and required action, not with a greeting that delays both. The test is simple: can the reader act on this email without re-reading it?

The subject line carries more weight than most writers give it. It is the only text many recipients will read before deciding whether to open the message. A strong subject line is specific enough to act on: “Review and approve Q2 budget draft - needed by Friday” outperforms “Q2 Budget” in every measurable way. The subject line is the summary; the body is the detail.

Email is durable. Unlike a Slack message, email creates a record and travels beyond the immediate team. This means the action requested must be explicit (who does what by when), the context must be self-contained (assume no conversational history), and the tone must be appropriate to the relationship, not just the channel. An email that requires a follow-up question to understand has failed at its job.

Canonical template

Section titled “Canonical template”
Subject: [Specific topic - action needed, decision required, or FYI - date or deadline if relevant]


[One sentence: what this email is about and what action, if any, is needed from the reader]


[2-4 sentences of context or supporting detail - only what the reader needs to act]


[Explicit next step: what, who, by when]
[Optional: secondary next step or offer to discuss]

When to use

Section titled “When to use”

Email is the right format when you need a durable record, when you are reaching external parties or stakeholders outside the immediate team, or when a request has a specific owner, deadline, or approval gate. It is also appropriate for formal announcements to a broad or mixed audience where structure and tone reflect organizational relationships.

When not to use

Section titled “When not to use”

Email is the wrong format for quick back-and-forth that belongs in a chat channel, for real-time coordination during incidents, or for topics so sensitive they require a conversation before anything is put in writing. If the message will be read inside a high-noise thread rather than a personal inbox, the format advantage is lost.

Pairs well with

Section titled “Pairs well with”

direct-communicator, executive, candid, matter-of-fact, warm

Often confused with

Section titled “Often confused with”

slack-message: Slack messages are designed for team channels, are ephemeral, and tolerate a conversational opening. Email creates a record, travels outside the team, and must be self-contained - the subject line and body structure carry obligations that a Slack message does not.

Instruction

Section titled “Instruction”
Write as a business email. The subject line should be specific enough to act on - it doubles
as the summary of the message. Open the body with the purpose and required action immediately,
not with pleasantries. Include only the context the reader needs to take the next step. State
the next step explicitly: who does what, by when. The reader should be able to act on this
email without re-reading it. Match tone to the relationship - direct but not cold for colleagues,
slightly more formal for external or senior recipients.

Template

Section titled “Template”

See the Email template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Direct Communicator, Executive, Candid, Matter of Fact, Warm

Avoid with

Section titled “Avoid with”

Pastoral, Reverent, Devotional Reflection

Often confused with

Section titled “Often confused with”

Slack Message

Examples

Section titled “Examples”

From: Maya Chen <maya.chen@company.com> To: eng-platform@company.com Cc: Priya Raman <priya.raman@company.com> Subject: Starting Monday: 30-day async standup trial - post by 10am local, no more 9am Pacific call

Team,

Starting Monday May 19, we are running a 30-day trial of an async-first standup. The 9am Pacific sync call is paused for the trial. Here is what you need to do and why.

What changes

  • Post a daily update in #team-standup by 10am your local time. Three fields, pinned template at the top of the channel:
    • Shipped (last 24h)
    • In progress
    • Blocked / at risk - @mention the person who can unblock
  • The Thursday 9am Pacific slot becomes a 60-minute working session, not a status meeting. Agenda posted Wednesday EOD.
  • On-call engineer reads #team-standup by 9am Pacific each day and responds to blockers within 30 minutes during business hours.

Why now

Q1 attendance was 4.6/5 for US, 3.2/5 for India - because 9am Pacific is 9:30pm IST. We average 14 minutes per standup with about 4 minutes that actually changes someone’s behavior. And the verbal status doesn’t persist - we hit three duplicate-work incidents last quarter that a searchable channel would have caught.

What I need from you

  1. Post your first async update Monday May 19 by 10am local.
  2. If the template doesn’t fit your work that day, post anyway and say so. Consistency matters more than format for the trial.
  3. Bring friction to the Thursday session or DM me directly. We will review at day 15 and day 30.

If you have concerns before Monday, reply to this thread or grab time on my calendar.

Thanks, Maya

Maya Chen Engineering Manager, Platform maya.chen@company.com | Slack: @maya