Slack etiquette debates emerged as companies adopted the platform, with workers developing strong opinions about thread usage, @channel abuse, emoji reactions, DM appropriateness, and whether ”👀” was passive-aggressive or just acknowledging messages.
The Unwritten Rules
Slack users developed tribal knowledge: use threads (don’t clog main channel), avoid @channel except emergencies (notifies everyone), emoji reactions replace unnecessary replies (saves noise), DMs for sensitive topics, status updates for availability. However, these norms were rarely documented, creating confusion for new employees. Violations sparked frustration: @channel for lunch invitations, not using threads for conversations, or demanding immediate DM responses.
The Always-On Culture
Slack’s real-time nature created pressure to respond immediately, blurring work-life boundaries. The green dot (online status) made availability visible, creating guilt for stepping away. Some workers felt obligated to respond to messages after-hours or on weekends. Status updates like ”🌴 On vacation” still resulted in messages, with senders assuming you’d “see it when you’re back” but creating notification anxiety. Organizations struggled with “right to disconnect” when Slack made everyone constantly accessible.
The Notification Overwhelm
Popular Slack workspaces could generate hundreds of messages daily across dozens of channels. Strategies emerged: aggressive channel muting, Do Not Disturb schedules, keyword notifications only, or declaring “Slack bankruptcy” (marking everything read without reviewing). Some companies experimented with “Slack-free days” or encouraging async communication over real-time chat. The tool designed to reduce email instead created new communication burdens.
Sources: