Async Communication: Slack & Email Phrases for Developers
5 exercises on async communication phrases. Choose the most natural and professional option.
0 / 5 completed
1 / 5
You want to start a Slack thread on an important technical topic before any code is written. Which opening is best?
Option C is excellent async communication. It names the topic precisely (API rate-limiting approach), states the purpose (get alignment), explains the timing rationale (before we code anything), and signals more detail follows (see below). 'Hey guys, question' (A) is too vague — readers don't know whether to engage now or later. 'FYI everyone' (B) signals low urgency and no need for input, which is wrong for an alignment thread. 'I have a question about the API' (D) is marginally better but still doesn't name the topic or purpose. Good thread openers front-load topic, purpose, and context so people can self-select engagement.
2 / 5
You notice staging hasn't been seeded in two weeks, but it's not urgent. How do you flag this without demanding action?
Option A is the gold standard for non-urgent async flagging. It pre-empts concern ('low priority'), states the concrete observation ('not seeded in two weeks'), and offers to take ownership ('happy to fix it if nobody else is on it') — which prevents the diffusion of responsibility. 'This is not urgent but look at this when you can' (B) is too vague. 'Staging is broken but it's fine' (C) is contradictory — if it's broken, it's not fine. 'Somebody should fix staging at some point' (D) is classic 'somebody' language — it will be ignored. Own the action or explicitly name a handoff.
3 / 5
You've opened a pull request and want to request an async review. Which message is most useful for reviewers?
Option D is a model async review request. It opens the PR, signals no urgency ('no rush, happy for async comments'), and focuses attention ('main thing I want eyes on is the pagination logic in lines 45-80'). That last part is the most valuable — it tells reviewers exactly where to spend their energy. 'Can you review my PR?' (A) gives no context and no focal point. 'Review this please' (B) is a command with zero information. 'PR is up — LMK thoughts' (C) is casual but also has no focus. Directing reviewers to specific lines or logic saves everyone time and produces higher-quality feedback.
4 / 5
You need to inform the team that a third-party API key is expiring, but no action is needed from them. Which message is most professional?
Option B is the complete FYI message. It names the item (third-party API key), gives a specific date (Friday), explicitly removes the burden from the team (no action needed), and commits to an owner and timeline (I'll rotate it Thursday EOD). 'Just so everyone knows, the API key expired' (A) uses past tense — if it's already expired, that's an incident, not an FYI. 'Heads up about the API key' (C) requires a follow-up message just to understand what the heads up is about. 'The API key is going to expire, just letting you know' (D) is honest but leaves who will act and when completely unclear.
5 / 5
You sent a message three days ago and still need a response. How do you follow up without sounding passive-aggressive?
Option A is the professional follow-up. 'Circling back' is the standard async follow-up signal — it's gentle, not accusatory. 'Still relevant' confirms the issue hasn't resolved itself. 'If you have a moment this week' signals it's not a crisis while keeping a time horizon in view. 'I sent this three days ago and nobody replied' (B) is passive-aggressive and makes the reader defensive. 'Can someone please respond to my message?' (C) sounds frustrated and demanding. 'Just checking if anyone saw my previous message' (D) implies the team is ignoring you. Follow-ups should assume good intent and make it easy to respond.