Writing Async Technical Updates in Slack and Email
5 exercises — writing technical update subject lines, blocked status messages, decision requests, post-incident updates, and weekly engineering summaries.
0 / 5 completed
1 / 5
You need to send an async update about a deployment that succeeded with one caveat. Which subject line is BEST?
Async subject lines should be skimmable and actionable. A good subject contains: status signal (✅), what happened (deployed to prod), and the caveat with ETA. Option B gives a reader everything they need to decide whether to read further. Option D is too long for a subject. Options A and C are too vague.
2 / 5
You are blocked on a task because you are waiting for a staging database credential. Which async message BEST communicates your blocker?
Blocked status messages should include: (1) 🚫 or BLOCKED label for skimmability, (2) what specifically is missing, (3) who can unblock you, (4) impact on timeline. Option D includes all four. Option B is too brief. Option A is vague. Option C does not mention the specific blocker.
3 / 5
You need async approval for a technical decision. Which message BEST frames the request?
Decision request messages should: state the deadline, present options clearly with trade-offs, include a recommendation, and provide a clear response mechanism. Option D does all of this. Async decision-making requires enough information for readers to respond without a meeting — Option D enables that.
4 / 5
A production incident was resolved an hour ago. Which post-incident Slack message is MOST professional and informative?
Post-incident updates should include: status (✅ Resolved), time window, root cause summary, fix applied, customer impact, and link to post-mortem. Option B covers all of these. This format helps stakeholders understand severity, closes the incident communication loop, and points to deeper analysis without burying readers in detail.
5 / 5
It is Friday afternoon. You need to send a weekly engineering update to your team channel. Which structure is MOST effective for an async audience?
Weekly engineering updates should be structured with clear sections readers can scan. The emoji-prefixed sections (✅ Shipped, 🔧 In Progress, 🚫 Blocked, 📅 Next Week) create instant visual hierarchy. Option D also includes a risks section — valuable for stakeholders making decisions. Options C and A are too vague; Option B provides no information.