3 ms·
> conversations that would be faster on slack I'm still searching for the golden goose "conversation" that's actually faster on Slack. Sure, a quick back and f
by SkyPuncher 4y ago
> conversations that would be faster on slack
I'm still searching for the golden goose "conversation" that's actually faster on Slack. Sure, a quick back and forth or check in is actually faster.
I have yet to find a meaningful discussion that's actually faster on Slack. It seems like they always drag out as sparsely filled, 45 minute threads. Nearly everyone of these would have been better served by a 10 minute call.
- bombcar 4y agoFaster can mean less clock time (Zoom will almost always win) or less “involved” time - each person reads the thread and responds when they have time, which uses less of their time but more clock time. It can work either way, depends on the type of discussion. Often the best is to hash as much out in chat as you can and then meet to finalize.
- SkyPuncher 4y agoThe problem is it still requires mental load to switch in and out of that conversation. You also create inequality on the team since threads rewards the fastest to reply. This is a lot easier to manage on a Zoom call.
- theonething 4y ago> still requires mental load to switch in and out of that conversation In my experience, sitting through a boring meeting while trying to appear engaged is way more mentally draining. > You also create inequality on the team Actually, I see the opposite, that video conferencing favors the most extroverted.
- bombcar 4y agoAll methods can create equality issues, which can be a reason for using a variety. I’ve noticed that the way Teams “collapses” threads that often the last to reply is the only one read besides the opening post.