3 ms·

Thank you for turning the conversation more polite. I agree with you about options having a cost. However, if so many of your users are complaining about somet

Thank you for turning the conversation more polite. I agree with you about options having a cost. However, if so many of your users are complaining about something, and if the complaint is about something as important as “losing messages,” then something should be done about it. It’s no longer enough to say that “but it works for some people” or to say that “options add complexity.” Our entire core team has discussed this. Nobody wants threads. They all lose messages due to this. But sometimes we accidentally respond to messages that start a thread. So, we want this option to be removed for the entire organization. But we can’t. It’s an option that’ll have cost, yes. But, it’ll be much simpler than many other complicated (and low value) things Slack has worked on in past two years. Those other things are also adding complexity, slowing down dev, increasing things to test, etc. And, again, this option solves a serious and fundamental problem of losing messages. So, it’s worth the cost for many of their users.

raldi 7y ago
If your team embraces threading, you'll soon see it's far superior re: not missing messages. See https://news.ycombinator.com/item?id=19758075 https://news.ycombinator.com/item?id=19758075 for some details on this; the gist is, when everyone threads, it’s easy to catch up when you’ve been away, and you automatically get notified when someone follows up on a topic you’ve been participating in. Are you familiar with the way you can cc: the channel on a thread comment when you’re concerned people might miss it?
rockostrich 7y ago
If your entire core team does not want threads, then police your company's slack to make sure people aren't using threads. The engineering org at my company decided that threads should be used as much as possible and when people don't reply to a previous message using a thread, they get told to use a thread next time. After months of doing this, noisy messages that are just replies to other messages have decreased significantly. Another alternative is having people always mark the checkbox that says "Also send to #channel". Vocal minorities shouldn't drive product decisions.

raldi 7y ago

If your team embraces threading, you'll soon see it's far superior re: not missing messages. See https://news.ycombinator.com/item?id=19758075 https://news.ycombinator.com/item?id=19758075 for some details on this; the gist is, when everyone threads, it’s easy to catch up when you’ve been away, and you automatically get notified when someone follows up on a topic you’ve been participating in. Are you familiar with the way you can cc: the channel on a thread comment when you’re concerned people might miss it?

rockostrich 7y ago

If your entire core team does not want threads, then police your company's slack to make sure people aren't using threads. The engineering org at my company decided that threads should be used as much as possible and when people don't reply to a previous message using a thread, they get told to use a thread next time. After months of doing this, noisy messages that are just replies to other messages have decreased significantly. Another alternative is having people always mark the checkbox that says "Also send to #channel". Vocal minorities shouldn't drive product decisions.