🏠 / Blog

A Discord User's Guide to Mastering Slack

Author: Kirill Igumenshchev
Published: 8/7/2024

For users accustomed to Discord’s chronological, graph-based conversations, migrating to Slack can be disorienting. Slack’s threaded model is a fundamental architectural departure designed for asynchronous work, but it requires a new mental model. This guide provides tactical workflows to help you master Slack and even replicate some of Discord’s familiar functionality.

Key Takeaways

• Embrace Threads: The core workflow is replying in threads (T key). Avoid posting replies in the main channel to keep conversations organized.
• Fork Conversations Intentionally: Use the “Also send to #channel” checkbox to surface an important discussion from a thread to the main channel.
• Simulate Quote-Replies: Press L to copy a message link and paste it in your reply. Slack automatically unfurls the link to provide context, approximating Discord’s quote-reply.
• Master Key Shortcuts: Use T to reply in a thread and Ctrl+K to quickly switch channels.

Standard Slack Reply Workflow: Threads

Use threads for all replies. The intended methods are faster, and replies cannot be retroactively moved into a thread.

• Mouse: Hover over a message. Click the “Reply in thread” icon.
• Keyboard: From the message input box, press the Up Arrow key to select the most recent message. Continue pressing Up to navigate to older messages, then press T to reply in a thread.

Advanced Thread Management

• Use the “Threads” View: The sidebar’s “Threads” view aggregates all followed conversations into a single inbox for efficient tracking.
• Follow a Thread: To monitor a conversation without replying, click the three-dot menu on a parent message and select “Follow thread.” This adds it to your “Threads” view without sending a notification.

Anti-Pattern: Editing to Reply

Avoid replying in-channel and then editing the message to add an @mention. This action does not create a thread, fails to notify thread followers, and clutters the main channel.

Simulating Quote-Replies with Message Links

When a single thread contains multiple conversational branches, or you need to reference an older message, you must manually provide context. Slack does not support nested threads, but you can simulate quote-replies using message links. This is the most effective way to approximate Discord’s functionality.

The workflow is to copy a message’s link and paste it into your reply. Slack automatically unfurls the link, showing a preview of the original message.

Mouse Workflow:

1. Hover over the target message.
2. Click the three-dot menu and select “Copy link”.
3. Paste the link into your reply.

Keyboard Workflow: For power users who prefer a keyboard-centric workflow:

1. Navigate between panes (Ctrl+F6 in the browser) to focus the channel or thread history.
2. Use arrow keys to select the target message.
3. Press L to copy the message URL to your clipboard.
4. Navigate back to the message input box and paste (Ctrl+V).

Forking a Thread

Fork a thread when a side discussion evolves into a distinct topic. This moves the conversation into a new parent thread in the main channel.

Forking with “Also send to #channel”

To fork a thread, check the “Also send to #channel” box when replying.

1. In the original thread, type the reply that will start the new topic.
2. Check the “Also send to #channel” box below the input field.
3. Send the message.

This action posts the reply as a new parent message in the main channel and notifies everyone, not just thread participants. Use this intentionally to surface a key update to the entire channel.

Keyboard Navigation: After typing your message, press Shift+Tab to focus the checkbox, then Spacebar to toggle it. Note that Slack often remembers the state of this checkbox for subsequent replies in the same session, so be mindful of its status.

Alternative Forking Methods

Use these when a sub-topic requires a smaller audience or becomes a self-contained project.

• Group DM: For focused discussions (2-4 people). Announce the move in the original thread: “Moving this to a DM with @personA,” and paste the original thread link for context.
• Temporary Private Channel: For larger workstreams. Create a new channel (e.g., #temp-project-feature), announce the move, and post the original thread link for context.

Power User Tips for Discord Converts

These tips map common Discord power features to their Slack equivalents.

• Master the Quick Switcher (Ctrl+K or Cmd+K): The fastest way to jump between channels, DMs, and workspaces.
• Customize Notifications with Keywords: Configure keyword notifications for specific terms (e.g., a project codename) beyond per-channel settings.
• Embrace Asynchronous Status: Use “Do Not Disturb” (DND) schedules to protect focus time. The culture prioritizes productivity over “online” status.
• Use Huddles for Quick Syncs: Use Huddles for impromptu voice calls. They are temporary and end when the last person leaves.
• Leverage Advanced Search Modifiers: Master search modifiers like in:#channel-name, from:@username, has:link, and date filters (before:, after:) to pinpoint information.
• Explore Slash Commands & Integrations: Use built-in slash commands like /remind and explore the app directory for integrations like Google Drive or Jira.

For a deeper dive into the design principles, market trends, and academic research behind these different chat architectures, see the companion post: Analysis: Why Quote-Reply is Superior to Slack’s Model for Professional Communication.

Microblogging Post

A Discord user’s survival guide for Slack:

1. Thread Everything: Always reply in threads. Select a message, press T. This keeps channels clean.

2. Simulate Quote-Reply: Select a message, press L to copy its link, then paste it in your reply. Slack unfurls it, adding context.

3. Surface Threads Intentionally: Use the “Also send to #channel” checkbox to fork a key discussion from a thread to the main channel. Use sparingly.

4. Navigate Fast: Use the “Threads” view as your inbox and Ctrl+K to instantly switch channels.

Full guide for power users: https://kirilligum.com/blog/migrating-from-discord-to-slack/

#Slack #Discord #Productivity #Workflow