We don't have guidelines, but if we did, here's what I'd like to see:
*Keep random comments in a "random" channel so I can unsubscribe if I want
*Don't post in a channel when a DM will work
*Only start a thread when you think there will be more than 1-2 replies
*Think long and hard before adding a new channel
*If you really need a specific person to see something specifically, tag them (because I'm definitely not reading everything)
Nice points.
Most of the things could be covered by common sense.
We have a naming policy (p** for projects, m*** for management, etc.) and some SLAs. Not a lot of policies, but that works.
Our main focus is removing unnecessary interruptions at a team level. I wrote a blog post highest impact actions. Here are the tips from the post:
Read more about each tip on the blog (https://tellspin.app/blog/reduce-interruptions-tips-for-slack/)
Ahhh clever on the Slack etiquette. Did you disable @here globally, or just have a broad policy to not use it, and then keep it enabled just in case it's really needed someday?
Three major considerations I have been using to evaluate the plethora of options available: 1. Effortless/non-intrusive: It shouldn't feel like a video call 2. Price: As this app would be complime...
I've been looking to try something new for knowledge/documentation storage for a little while now. Confluence has always been there, but I find it to be relativly limited for the cost and additiona...
Hey guys, first post here. As part of my work, I have to deal with and respond to a lot of incoming messages from different chats: Linkedin/WhatsApp/Signal/IG. I try to use Unreads/Archive features...
That's a great idea on the Random channel; we literally were discussing how #random is only for truly random, non-work stuff this week.
And I still feel like #general is the weirdest channel that I'm never certain how to use best 😅