4 ms·
This resonated well with me. I've always preferred email to chat, for many of the reasons cited in the article. The trouble is, it's too far to the right. So
by tyingq 9y ago
This resonated well with me. I've always preferred email to chat, for many of the reasons cited in the article.
The trouble is, it's too far to the right. Some people don't respond for days. So we have tools with instant response expectations, and ones with variable expectations. Nothing with clear "within a day" expectations. Email used to be that way, until too many peed in that pool.
- lloeki 9y ago> Nothing with clear "within a day" expectations. Email used to be that way, until too many peed in that pool. Slack, then Mattermost, solved that for us. Our email inboxes became crowded with banter, notifications, as well as info that should be tracked in a centralised place. It was a mess because email became a kitchen sink. So now we use GitLab for most of the serious "this better be tracked" stuff, Mattermost both for the off- and on-topic live chat, and email takes back its natural place when interacting with third parties (those we didn't onboard on GitLab), reply-soon-enough, and notifications (including GitLab ones, which thus covers "reply-soon-enough+should-be-tracked" in a seamless way). The key point is having the three tools together, personally configured as each user sees fit WRT notifications, allows for each tool to blend with each other over the gradient of possible use cases.
- TeMPOraL 9y ago> Nothing with clear "within a day" expectations. Email used to be that way, until too many peed in that pool. This is pretty much purely a social issue, and should be set by the management / work culture directly. Nobody can force you to reply to an e-mail any more than they can force you to reply to a Slack message. Because in private, I try to push as much communication as possible through e-mail exactly so that I don't have to reply to anyone within 24 hours if I don't feel like it.
- tyingq 9y agoUnfortunately, it spans farther than inside the company. There's suppliers, outside counsel, partners, customers, etc. Voice for that sort of thing is dying too, because people either disable, or don't check voice mail.
- toomuchtodo 9y agoI'm in an enterprise environment; the death of voice is greatly exaggerated. Voicemails? Not dead, just moved to text transcription delivered to my email from unified messaging.
- tyingq 9y agoNot dead for you. Too many of my colleagues and customers ignore it for me to use it. I can't keep track of which ones still listen to them. Edit: Yes, it's a people issue . Wasn't trying to frame it as a tech one. We've ended up with two paths, reply now (slack, other IM, sms) or reply/maybe/never (email/voice). For people reasons, as you say. There have been some attempts to use tech to solve it. Google's inbox, for example, might have helped unclutter so you could see what was important.
- toomuchtodo 9y agoJust as easy for them to ignore emails, IMs, or Slack messages. It's not a tech issue, it's a people issue.
- TeMPOraL 9y agoFWIW, in my country voicemail was probably dead on arrival. I'm yet to know someone who actually relied on them and treated them as anything more than an annoyance (if someone calls you and gets redirected to voicemail, they usually disconnect, but sometimes that leaves an "emtpy" message which you'll get later notified about). About the only use of voicemail I've ever experienced is that in American movies (protagonist listening to their voicemail backlog on their landline seems to be a common trope).