Productivity at Workbeginner

Async Communication Master — Write Messages That Don't Need Follow-Ups

Write Slack messages, updates, and briefs so clearly that nobody needs to ask clarifying questions.

Copy & Paste this prompt

You are a remote work communication expert who has helped distributed teams eliminate 60% of unnecessary meetings.

Help me communicate something asynchronously so clearly that no follow-up is needed.

What I need to communicate: [DESCRIBE THE MESSAGE]
Audience: [WHO READS THIS?]
Channel: [SLACK / EMAIL / NOTION / PROJECT TOOL]
Urgency: [FYI / NEEDS INPUT / NEEDS DECISION / BLOCKING]

Create:

1. THE MESSAGE — BLUF principle (Bottom Line Up Front):
   - First line: conclusion, decision, or ask
   - Context: why (only what's needed)
   - Details: supporting info
   - Action required: what, from whom, by when
   - Decision default: "If no response by [date], I'll proceed with [option]"

2. FORMATTING — Bold key points, bullets, headers, TL;DR, thread-friendly

3. AMBIGUITY CHECK — Flag vague words, missing context, implicit expectations

4. RESPONSE OPTIMIZER — Yes/No questions, multiple choice, deadline, specific person

5. VERSIONS — Adapted for Slack, email, and meeting notes/Notion

#async#communication#remote-work#slack#writing

Works with

chatgptclaudegemini

💡 Pro Tips

•If your Slack message is >5 lines, it should be a doc with a summary
•Always include a default action — what happens if nobody responds
•'@sarah, which option?' gets answers. 'Team, thoughts?' gets zero.

✨ Example Output

SLACK VERSION:
🔔 **Decision needed: API rate limiting** — @sarah @mike by Friday EOD

**TL;DR:** Choose token bucket vs sliding window. I recommend token bucket. If no objections by Friday 5pm, I'll start Monday.

**Options:**
A) Token bucket (my rec) — simpler, 2 days
B) Sliding window — more precise, 4 days

👍 for A, or reply with concerns.