Slack Etiquette

slack_etiquette.md

1. Clear Channel Naming Conventions:
   • Project Channels: Use a consistent format like project-<name> for channels related to specific projects. For example, project-acme-website.
   • Functional Channels: Prefix functional channels with their purpose, such as design-, devops-, or marketing-.
   • General Channels: Create general channels like general, announcements, and random for broader discussions.
   • Location-Specific Channels: If your team is distributed, consider channels like london-team, nyc-team, etc.
   • Avoid Abbreviations: Use clear and descriptive names to avoid confusion.
2. Review Channels Regularly: Periodically review your channels to ensure they remain relevant and organised. Consider archiving channels that are no longer active or necessary.
3. Use Notion for Permanent Information: While Slack is great for real-time communication, consider Notion as the primary repository for permanent information. Use Notion for documentation, processes, and company-wide knowledge. It provides a structured and organised way to store and access essential resources. For ephemeral discussions, stick to Slack, but for anything that needs to stand the test of time, turn to Notion.
4. Promote Public Discussions: Whenever possible, keep discussions public. Use appropriate channels or create new ones for specific topics. Public discussions foster transparency and allow everyone to benefit from shared knowledge. Remember that while Slack messages are ephemeral, some information might not have made its way to Notion yet.
5. Know When to Use @here and @channel: Use these mentions judiciously. Avoid spamming the entire channel unless it’s genuinely urgent or relevant to everyone.
6. Embrace Threads: Threads are essential for effective collaboration. Use them to keep ongoing conversations organised within a channel. Threads prevent unnecessary notifications for everyone else in the channel.
7. Designate a Non-Work Channel: Create a random or similar channel for casual conversations. Encourage teammates to share non-work musings there. It builds trust and camaraderie among team members.
8. Review and Edit Messages Before Sending: Take a moment to review your messages before hitting send. Clear, concise communication reduces the need for follow-up questions.
9. Use Slack for Ephemeral Communications Only: Reserve Slack for real-time discussions, quick questions, and updates. For more permanent information, consider using other tools like documentation systems or email.

Remember, a well-organised knowledge base ensures that everyone has access to accurate and up-to-date information, while public discussions encourage collaboration and transparency. 🚀📚🗣️