Live data from Hacker News

Collaborate with kindness: Etiquette tips in Slack

slack.com

61–70 of 124 posts

Re: Collaborate with kindness: Etiquette tips in Slack

#61
post #50

> Default to public channels for better workplace communication I have tried so hard to get people to do this, but it seems like a lot of my coworkers are honestly scared of "public" channels, and by "public" I mean a channel with only 15 or so people on it. They insist on DM'ing most things, and some just refuse to use chat at all; those will only communicate via email.

Sending a message in a public channel is psychologically akin to walking into a room full of people and just loudly proclaiming/demanding help. I don't think people are simply 'scared' to do it -- they just (rightly) intuit that it's somewhat strange and counterintuitive that it would be the preferred method over talking to an individual and building a rapport / friendship.

Sending a message in a public channel is psychologically akin to walking into a room full of people and just loudly proclaiming/demanding help.

Only if that room enables people to only hear shouts that include their name, where they can pause hearing shouts, where it's acceptable to ignore shouts if you're busy, and where there's someone recording the shouts in case someone has a similar problem later.

In fact, in almost all the ways that matter it's entirely different to shouting in a room.

Re: Collaborate with kindness: Etiquette tips in Slack

#62
post #52
post #50

Earlier quoted context omitted.

Sending a message in a public channel is psychologically akin to walking into a room full of people and just loudly proclaiming/demanding help. I don't think people are simply 'scared' to do it -- they just (rightly) intuit that it's somewhat strange and counterintuitive that it would be the preferred method over talking to an individual and building a rapport / friendship.

Also if you sound dumb it's out there for the public to see.

It's the job of everyone on the team, especially leads, to reply in ways that make sure everyone knows asking a dumb question is significantly better than being blocked.

I would prefer to answer dumb questions all day long than have people on my team grind to a halt for a day because they're scared of asking for help.

Re: Collaborate with kindness: Etiquette tips in Slack

#63
post #52
post #50

Earlier quoted context omitted.

Sending a message in a public channel is psychologically akin to walking into a room full of people and just loudly proclaiming/demanding help. I don't think people are simply 'scared' to do it -- they just (rightly) intuit that it's somewhat strange and counterintuitive that it would be the preferred method over talking to an individual and building a rapport / friendship.

Also if you sound dumb it's out there for the public to see.

I got past worrying about sounding dumb a long time ago. It’s the #1 thing that people need to get over imo

Re: Collaborate with kindness: Etiquette tips in Slack

#64
post #58

Collaborate with kindness: Etiquette tips in Slack: use email. - "1. Never send a direct message that just says “hey” or “hello.", write longer messages -> use email. - "2. "Write longer messages that scan quickly" -> don't use a chat app for your messages, use email. - "3. Use threads for effective team collaboration. Seriously." -> use a mailing list. - "4. Replace short follow-up messages with emoji reactions" ->…

>Replace short follow-up messages with emoji reactions" -> don't do anything when it's not needed.

I feel compelled to thank people after they've helped me. Thank you emails feel burdensome. Emoji responses are a happy medium. (You don't get notifications from emoji responses right? I've never used Slack)

Re: Collaborate with kindness: Etiquette tips in Slack

#65
post #19

> …the recipient gets a notification on that first “hey” that contains no information and potentially causes distraction. The person might see the indicator that you’re typing but is still left waiting for your full message. I would turn this around and call this a product design problem. Maybe Slack shouldn't send a notification when all you've said is "hey" and you're typing a follow-up message. Really, if you have…

Teaching people to replace "" with ", " is better than trying to design a filter for every salutation.

Re: Collaborate with kindness: Etiquette tips in Slack

#66
post #62
post #52

Earlier quoted context omitted.

Also if you sound dumb it's out there for the public to see.

It's the job of everyone on the team, especially leads, to reply in ways that make sure everyone knows asking a dumb question is significantly better than being blocked. I would prefer to answer dumb questions all day long than have people on my team grind to a halt for a day because they're scared of asking for help.

Yeah that is a good point, it's bad when you dump hours into something that could be figured out in a couple of minutes.

Re: Collaborate with kindness: Etiquette tips in Slack

#67
At risk of repeating what everyone else has said... My PM does the "Hey" thing. I do not multitask. I'm a serial tasker.

So I turned off all notifications on Slack. The only way I know I have a message is the red dot that appears in the panel icon.

Now, it's async again. When I even glance up to see if there are new messages... Red dot or no red dot

Re: Collaborate with kindness: Etiquette tips in Slack

#68

> Never send a direct message that just says “hey” or “hello.” I first started hearing people suggest this recently (within the past month or so). I never really understood why these message bothered people so much - they never bothered me and always actually seemed a bit more polite than just barreling forward with a question. But I guess if even Slack themselves are saying don't do that, it must really get on other…

[deleted]

Re: Collaborate with kindness: Etiquette tips in Slack

#69
post #59
post #51

Earlier quoted context omitted.

Sure -- or people don't want to clog up channels with what they perceive to be minutiae or very context-specific questions requiring some back-and-forth.

For which, I am thankful to them. Nothing better then dozens of irrelevant chat messages in larger group chats I am member of that I cant mute, because once in a while there is something important.

You should use threads for that.

Re: Collaborate with kindness: Etiquette tips in Slack

#70
post #59
post #51

Earlier quoted context omitted.

Sure -- or people don't want to clog up channels with what they perceive to be minutiae or very context-specific questions requiring some back-and-forth.

For which, I am thankful to them. Nothing better then dozens of irrelevant chat messages in larger group chats I am member of that I cant mute, because once in a while there is something important.

I mute them anyway because I won’t see the important message among all the chit-chat notifications, so I cut the middleman.
Post reply on HN