4 ms·

I'm curious about how the actual discussions go. I'm with you in that people default to no reaction (in writing or oral), except when there is an explicit reque

I'm curious about how the actual discussions go. I'm with you in that people default to no reaction (in writing or oral), except when there is an explicit request. In practice there's a ton of Slack messages I write that have no reaction whatsoever, but if they're in a thread with new messages coming after, we can all assume people commenting have read what was said before. That's the basic structure of a conversation. Announcements kind of messages, sent in isolation, are more tricky. But then, if it matters to have a reaction, we get used to explicitely ask for it IMHO (e.g. some event needs to be acknowledged), and it's kinda the same in a real time meeting: you'll also make sure people are listening and understood your announcement, and not doing something else on the side.

keiferski 2y ago
...if they're in a thread with new messages coming after, we can all assume people commenting have read what was said before... IME this actually isn't always the case, especially if it's a busy channel. And so it ends up being more effective to just book a 15 minute Zoom call with someone if you need to actually get their attention, rather than put a message in a channel and/or privately.
- makeitdouble 2y ago
  That sounds like the kind of reminder we'd do in a weekly team meeting or project review, but you might have different use cases in your mind. In general the cost of having a separate meeting is kinda high (apart from booking the spot, it generally also means an agenda and a transcript)