Skip to content
Writing Style Library

Slack Message

A short, async-first message designed for team channels - direct, scannable, and respectful of the reader’s attention in a high-volume feed.

Slack Message

Section titled “Slack Message”

A Slack message in a professional context competes with dozens of others in the same channel. The reader skims. The effective Slack message acknowledges this and works with it rather than against it: the most important information appears in the first line, the message is short enough to read without scrolling, and any required action is explicit.

Canonical template

Section titled “Canonical template”
[One-line summary - the message should be understandable from this alone]


[Optional: 2-4 bullet points for supporting detail]


[Optional: @mention for required action]
[Optional: thread invitation for discussion]

When to use

Section titled “When to use”

Team status updates, quick questions, sharing a link with context, incident notifications, async decisions.

When not to use

Section titled “When not to use”

Formal communication requiring a paper trail, communication with external parties, emotionally complex topics that deserve more space.

Pairs well with

Section titled “Pairs well with”

operator, friendly-mentor, matter-of-fact, candid, warm

Often confused with

Section titled “Often confused with”

email: A Slack message is ephemeral, lives in a team channel, and can lean on shared channel context and conversational history. An email creates a durable record, travels beyond the team, and must be self-contained - the subject line and body carry obligations that a Slack message does not.

Tells

Section titled “Tells”
  • The most important information lands in the first line
  • Short enough to read without scrolling
  • Any required action is explicit, often with an @mention and a deadline
  • Scannable - bullet points and headers used when the message must run longer
  • Voice and tone matched to the channel, since the format itself is neutral
  • Spans a wide range, from a 3-word reply to a multi-paragraph update

Anti-patterns

Section titled “Anti-patterns”
  • Writing it as a self-contained durable record with a formal subject and full context - That is the confusable email; a Slack message is ephemeral team-channel communication that can lean on the channel and the conversation, where email must travel and stand alone.
  • Burying the point under a conversational warm-up before getting to it - The reader skims a high-volume feed; if the first line does not carry the message, it is missed in the scroll.
  • Closing a request with “let me know what you think” instead of a specific ask - A vague ask in a busy channel goes unanswered; the format works only when the required action names who does what by when.

Failure modes

Section titled “Failure modes”
  • Compresses into cryptic shorthand - brevity is pushed until the message is acronyms and clipped fragments that the reader cannot decode without asking - Be brief enough to scan, not so terse it needs a follow-up; if a teammate would have to ask “what do you mean,” add the few words that make it clear.
  • Fragments one thought into a burst of many one-line sends, each firing its own notification until a single message becomes a wall of pings - Group a complete thought into one scannable message; the channel rewards brevity, not a staccato of fragments that each interrupt the whole team.

Instruction

Section titled “Instruction”
Write as a Slack message for a professional team channel. Lead with the most important
information in the first line - the message should be understandable from the first line alone.
Keep it short enough to read without scrolling. If the message is complex, use bullet points to
make it scannable. Make any required action explicit and specific: "@alex can you confirm by
EOD?" not "let me know what you think." Match the channel's tone - standup channels are more
formal, social channels are warmer. Respect the reader's attention in a high-volume feed.

Template

Section titled “Template”

See the Slack Message template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Operator, Friendly Mentor, Matter of Fact, Candid, Warm

Avoid with

Section titled “Avoid with”

Pastoral, Reverent, Columnist

Often confused with

Section titled “Often confused with”

Email

Examples

Section titled “Examples”

Proposal: try async standups for 30 days starting May 19

Our 9am standup is hard on the India team and the info disappears after each call. Want to run an experiment:

  • Each person posts to #team-standup by 10am local time (3 fields: shipped / in progress / blocked)
  • Blocked items @mention the person who can unblock
  • On-call reads the channel by 9am PT and responds to blocks within 30 min
  • We keep Thursday 3pm as a real working session for anything that needs live discussion

@priya @arjun @deepa - this gets you out of 9:30pm standups. Want to hear your reaction first.

:thread: Drop thoughts in thread by Friday and I will send a final plan Monday.

Appears in diff-pairs

Section titled “Appears in diff-pairs”