5 exercises — practice async small talk phrases in Slack, virtual coffee chats, and #watercooler channels. Learn to build genuine connection across timezones.
0 / 5 completed
Key phrases for remote watercooler and async small talk
"Celebrating finally fixing [X] — took me all week. Anyone else had a 'finally!' moment this week?"
"That deep work feeling is so good. What's the refactor — is it the [X] thing or something new?"
"I started reading [book] this weekend — already making me rethink [specific thing]. Anyone read it?"
"Do you find these things cross your mind from a [management / senior] perspective, or do you think about it differently?"
"The bit about [specific detail] really resonated — congratulations on that milestone."
1 / 5
Your team has a #watercooler Slack channel. Someone posts "Happy Friday everyone!" Which response builds the most genuine team connection?
Option B is the ideal watercooler message. It: (1) matches the energy ("Happy Friday!"), (2) shares a specific relatable moment ("flaky test finally passing") — this is deeply universal in software teams, (3) uses a light self-deprecating frame ("took me all week"), (4) ends with an open question that invites others to share similar moments. This is exactly what makes a #watercooler channel feel alive rather than performative. Option A is fine but gives nothing to respond to. Option C expresses negativity about the work week — this is relatable but sets a slightly deflating tone. Option D is polite but impersonal — it could have been sent by a bot. Rule for async small talk: share something specific + invite reciprocation.
2 / 5
Your manager schedules a 15-minute "virtual coffee" with you. After a brief check-in, which topic is best for genuine casual conversation?
Option B is excellent virtual coffee conversation. It: (1) shares genuine intellectual curiosity (you've been reading something), (2) creates a genuine question that a manager-perspective person can answer interestingly ("do you think about it differently from this side of the fence?"), (3) invites them to share their perspective rather than evaluate yours, (4) doesn't put them on the spot about performance or projects. The frame "from this side of the fence" shows you recognise the difference between IC and management perspectives — this signals maturity. Option A turns casual time into a work meeting. Option C turns it into self-promotion — virtual coffee is for connection, not performance. Option D is a valid goal but a jarring topic for a casual chat — it makes the whole coffee feel transactional. Save career conversations for dedicated 1:1 time.
3 / 5
Someone on your distributed team posts in Slack: "Just finished a 3-hour deep work session on that refactor. Feel like a different person." Which async reply best builds connection?
Option B is the async small talk gold standard. It: (1) validates the feeling with genuine empathy ("That deep work feeling is so good"), (2) shows curiosity about their work ("What's the refactor?"), (3) shows you remember context from previous conversations or sprint discussions ("Is this the auth module thing?") — this signals you pay attention, (4) invites them to share more. This is how you build real connection asynchronously. Option A is the minimum viable response. Option C introduces a complaint about meetings — even if relatable, it pivots the conversation away from their moment and toward your frustration. Option D is hollow corporate encouragement. In async small talk, the key technique is: reflect the emotion + ask a specific follow-up question.
4 / 5
You want to start a non-work conversation in Slack on a Monday morning. Which message is most likely to get genuine engagement?
Option B is the model Monday morning Slack message. It: (1) shares something genuinely interesting and specific ("A Philosophy of Software Design"), (2) includes a hook that anyone who's read it can respond to ("making me rethink how I name things") — specific enough to be real, (3) ends with an open invitation ("Anyone read it?"). This creates a self-selecting conversation: people who've read it can share reactions; people who haven't might get curious. Option A is pleasant but generic — it creates no thread. Option C is a gentle commiseration — relatable but slightly passive. Option D ("what's everyone working on") turns casual into a work check-in. Rule: in async chat, specificity is warmth. Vague positivity is noise.
5 / 5
A colleague in a different timezone posts a long message sharing a personal milestone outside work. You want to acknowledge it warmly but briefly. Which response is best?
Option B is the ideal async acknowledgement of a personal milestone. The critical technique: reference a specific detail from their message. This single element transforms a generic congratulation into genuine engagement. It signals that you actually read what they wrote, not just the opening line. Even in a brief response, specificity communicates care. Option A is warm but generic — it could be sent without reading the message. Option C is the minimum signal with minimum effort — better than nothing, but misses an opportunity for real connection. Option D over-loads with positivity ("inspiring story", "really proud", "cheering you on") — this can read as performative rather than genuine. A short message that references one specific thing they said is worth more than a long generic celebration.