This set builds vocabulary for lightweight synchronous and asynchronous team communication tools.
0 / 5 completed
1 / 5
At standup, a dev suggests starting a lightweight, low-friction audio conversation directly inside a Slack channel instead of scheduling a formal video call. What is this feature called?
A huddle is Slack's lightweight audio (optionally video) conversation feature, started instantly within a channel or DM without the overhead of scheduling a formal meeting. It is designed for quick, informal syncs rather than structured calendar events. This lowers the friction for spontaneous real-time conversation.
2 / 5
During a design review, the team keeps a focused side conversation attached to a specific message without cluttering the main channel feed. What is this called?
A thread keeps replies to a specific message grouped together, separate from the main channel timeline, so a side discussion doesn't bury unrelated messages for everyone else. This structure supports focused conversations within a busy channel. It is a core mechanism for keeping asynchronous channel communication organized.
3 / 5
In a code review, a dev sets a temporary status indicating they are heads-down and shouldn't be interrupted with non-urgent messages. What is this called?
A status indicator signals current availability, such as being in focus time, to teammates without requiring an explicit reply to every message during that period. This sets async expectations proactively rather than leaving colleagues guessing about response delays. It supports healthier asynchronous collaboration norms.
4 / 5
An incident report shows a critical decision was made during an ad hoc huddle with no written record, causing confusion later. What practice would prevent this?
Because a huddle is a live, typically unrecorded conversation, posting a written summary of key decisions back into the relevant channel afterward preserves an async, searchable record for anyone who wasn't present. Skipping this step lets decisions get lost or misremembered. This practice mirrors the value of writing meeting notes after any verbal discussion.
5 / 5
During a PR review, a teammate asks why the team prefers threads and huddles over defaulting to scheduled video meetings. What is the reasoning?
Threads and huddles offer lower-overhead alternatives to scheduling a full meeting, letting a team resolve quick questions or short discussions without calendar coordination. They complement, rather than replace, scheduled meetings for topics that genuinely need structured, prepared discussion. Balancing these options is part of healthy remote and hybrid team communication.