3 ms·
For better or worse, I think Slack’s approach of opt-in threading is effectively the default at this point. If users’ (technical or otherwise) mental model assu
by tfehring 5y ago
For better or worse, I think Slack’s approach of opt-in threading is effectively the default at this point. If users’ (technical or otherwise) mental model assumes that messages can get sent to a channel, but the software only allows messages to be sent to a thread, that disconnect could result in lots of unexpected behaviors.
For what it’s worth, I personally prefer Slack’s approach over Zulip’s - I think threading is a really important feature, but requiring it for every message creates excessive and unnecessary friction.
- conradludgate 5y agoI think if you could type a message, and it could use some heuristic to determine a sensible thread title for you automatically, that would improve the experience quite a bit
- tfehring 5y agoYeah, I think that would help a lot. I think I’d personally go a step further and make thread titles optional, I generally don’t think they add much value over just reading the first message in the thread. Even with that change, though, I’d still rather have threading be opt-in. Not every message fits well into exactly one thread.
- gilbertbw 5y agoPersonally I’ve found the ability to move messages between / split threads (topics) helps a lot with this in Zulip. We moved from Slack, and those that struggled with threading there mostly picked it up over a few weeks.