Dunder Mifflin Team Hub
Share
Explore
Dunder Mifflin Team Hub
How We Work

icon picker
Slack Guidelines

Using Slack for your team! Consider using our Slack pack to easily send messages to channels or DMs right from your Coda Doc! We love to use this tool when managing projects.

You could also join and create channels from your Coda doc too.

Learn more on the
Slack Pack here
⁠
!

Summary

Following these guidelines will make us more consistent, predictable, and effective in our communication.
Make your availability clear.
Use status updates to let others know when you are away or when they should expect a delayed response.
When you’re not working, consider logging out or setting Do Not Disturb so that you can get out of “work mode” and recharge.
Assume best intent. Sometimes tone and context are lost in text.
Communicate using threads. In general, your message in slack should be either:
a response to an existing message, in the thread below that message.
a new thread, in which you case you should put the most important information or action items first, use bold text to highlight important pieces, and use line breaks or bullets to break up content.
Default to posting in public channels. Use private groups and DMs for sensitive material or for coordinating to avoid spamming public channels.
Abide by the conventions for @mentions, particularly when mentioning groups or in large or reserved channels like #announcements and #general (listed at the bottom of this doc).
We’re all responsible for our adherence to these guidelines, so:
re-read your message before you hit send.
when you think someone has strayed a bit too far from these guidelines, respond and politely let them know how they can communicate better.

Additional Resources

Slack help on
channels, sending messages, and other basics
⁠
⁠
Slack
tips and tricks
⁠
⁠

Gallery
Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.