3 ms·
Remove asynchronous interruptions and go back to old-fashioned synchronous interruptions (scheduled meetings, either in person or calls/video chats) for the stu
by geofft 9y ago
Remove asynchronous interruptions and go back to old-fashioned synchronous interruptions (scheduled meetings, either in person or calls/video chats) for the stuff that requires high-bandwidth communication and asynchronous non-interrupting queues (emails, or other similarly-shaped things like tickets or wiki page edits / comments) for the stuff that requires low-bandwidth communication and more intensive thought / work.
If you need asynchronous interruptions, pre-Slack and even pre-email culture had ways to do this - phone calls, pages, knocking on people's doors - but they were viewed as rare and exceptional, and the coworker who would knock on your door all the time to ask if you saw the message they just sent was viewed as rude and distracting.
- deleted 9y ago[deleted]
- rowyourboat 9y agoI'ld much rather be IM'ed or emailed than called or paged. If I am called, the phone rings or the pager beeps, and I have little choice but to interrupt my work. My slack client, on the other hand sits in the system tray, silently displaying a little blue or red dot. I can open chat when I feel like it, or ignore it until such a time when I am not concentrating on something else. Asynchronous communication is empowering: You can choose when you communicate and when you want to concentrate. Synchronous communication does not afford you that luxury.
- TeMPOraL 9y agoThe problem is, chats are being interpreted as synchronous - you are expected to be available and to reply in real-time.
- rowyourboat 9y agoI found that to be a problem of organizational culture, not of chat itself. In my experience, if it was culturally fine to interrupt other people's work, quick answers were expected via chat, too. If it was the organization's culture to let people work without unscheduled interruptions, that extended to the expectations around chat, too.
- TeMPOraL 9y agoIndeed. However, chat facilitates this particular kind of organizational dysfunction much more than e-mail; that's probably why people pin the problem on chats.
- geofft 9y agoWhy is using Slack in this workflow superior to using email? I also know if I have unread emails via the tray icon or mobile app badge, same as with Slack. Is it just that short frequent messages in email feel weird?
- rowyourboat 9y agoThat, the superior handling of short-message group conversations and the fact that the number of people who could email me is vastly greater than my team members on slack. As such, I tend to check slack relatively frequently, while I check my emails only twice a day - I do not have push notifications enabled for email. Basically, slack means a usually-within-2-hours response time, while email means same-or-next-workday response time.
- IshKebab 9y agoHow is email non-interrupting but Slack is? You can enable/disable notifications for either of them and respond to either when you like.
- geofft 9y agoCulture and expectations. Same reason I'm listing video calls as non-interrupting when they certainly are capable of interrupting: set expectations that scheduled meetings are normal and unannounced calls are for emergencies. If you can make your Slack non-interrupting, fantastic, but probably the advantages over email are slim.