7 ms·
I've noticed the people who dislike IM tend to be weaker communicators in general. Compared to email, IMs tend to have less context and are generally short and
by kenhwang 7y ago
I've noticed the people who dislike IM tend to be weaker communicators in general.
Compared to email, IMs tend to have less context and are generally short and to the point but otherwise unstructured. There's a pressure to respond quickly, and part of responding quickly is typing less words. Condensing thoughts to a minimum number of words is a harder skill than it seems; people tend to compensate for low quality communication with more words. Then there's still all the drawbacks of email: typing proficiency, spelling, grammar, and asynchrony.
Compared to mouth words conversations, IM doesn't have inflection or body language to help with tone. It's also not as fast as live conversations so it's easier losing context and easier to get overwhelmed with multiple conversations happening concurrently.
I personally love IM because it's easier to have multiple simultaneous conversations with more throughput and less latency than email normally achieves. I think of IM like async programming, when one conversation gets blocked, I can work on another. Mouth-to-mouth communication is like a singled threaded I/O, you're wasting resources (time) when you're blocked, but if you're not blocked you're more efficient since there's no context switching (so a heavily one sided conversation/lecture). Email is like multithreading, context switches are more expensive and the amount of work done per context switch needs to be big enough for it to be worthwhile. They all have merits and use cases.
- Pokepokalypse 7y agoIM's also great for keeping a whole team or group in-sync with a current team activity or sprint. If everybody on the team is aware of how to properly use IM, (and when to use an alternate means) - then most of the bad effects talked about in the ranticle are easily overcome. I'm not even sure it's possible to do remote work without IM.
- kenhwang 7y agoKeeping a group in sync is also possible (and I'd say preferable) via email, since current objectives and sprints don't change very quickly at all relative to the speed of conversation, and both have natural paper trails. But if your current objective is something like triaging a complex outage or live event, IM works beautifully for that. I've done remote work via long conference calls before and it works for certain types of work; I agree that IM is much more preferable.
- tasty_freeze 7y ago> I'm not even sure it's possible to do remote work without IM. As someone who has been working from home for 15 years, I'm here to say it only takes one counter example (me!) to say of course it is possible to work remotely without it. Recently I was forced to adopt slack on top of all the other communication channels in use (phone, webex, email). Perhaps it is a generational thing (I'm in my 50s), but I greatly prefer to talk or use email for both my personal and professional life. The two modes of communication are different enough that they fill different purposes. IM seems to be an awkward in-between mode of operation. I HATE getting a slack message, with the expectation that I'm always ready to be interrupted, and I owe a prompt reply. Typical slack interaction. I'm head down debugging something when slack clacks at me. I click on the app, and it says: "hey". The person on the other side is just probing to see if I'm really there. So I reply, "I'm here". But I can't go back to my work because I know a single sentence is going to interrupt me again very soon. Slack helpfully tells me "So and so is typing..." and I continue to sit like a dummy, waiting for it. Eventually the message arrives which was important enough to interrupt my flow and which began emptying my the cache of information I had amassed while debugging: "Are you working on bug #1234, or does someone else have it?" So I type, "Yes, I'm working on it right now." I close the window and try to get back in the flow, but 60 seconds later, slack clacks again at me. I open the window. "OK, thanks" it reads. Boy, that was a real productivity booster. And before someone snidely says that I'm a grumpy, out of touch programmer -- my reviews would indicate otherwise. Yes, it is nice that IM leaves a paper trail that a phone call doesn't, but typically there is one or two important points that come out of conversation and I can quickly add them in my TODO file.
- kstenerud 7y agoThat's a prime example of poor IM skills. Messaging someone "hey" is a productivity killer, as you said, for the reasons you said, which is why you just shouldn't do it. Healthy IM communication should go a little more like this: Working, working... beep alt-tab "Hey, are you working on bug #1234, or does someone else have it?" "I'm working on #415, so someone else has it." alt-tab working, working... beep alt-tab "Do you happen to know where the Davidson account files went? I can't find them anywhere :/" "No, sorry. Maybe try the Z: drive?" alt-tab And if you don't want to be interrupted by anything except critical things, set "do not disturb" mode.
- barrkel 7y agoI don't agree at all. I don't like IM because I'm in either of two states while in a conversation: * Distracted from my work that requires concentration while someone slowly asks me questions * Blocked in my work until someone slowly answers my questions (Yes, these are two sides of the same coin.) If my work mostly consisted of conversations, it wouldn't be a problem. But my work doesn't. IM is slightly better than email for getting people to answer all points, but an email thread with inline replies would be my overall preference, like in newsgroups back in the day. However most people nowadays treat email as an inefficient IM, and only answer the first or last points. A Google Doc with collaboration in comments is a viable alternative, especially for something where there's a product (e.g. design or decision) from the conversation.
- jay_kyburz 7y agoThis. We use slack at work, but not really as an IM, its more like an easy to use message board. I have slack closed most of the time and only check in a few times a day. If somebody has a problem they need an answer too right now, they can call me.
- rolleiflex 7y agoWe've actually just built what you're using at work: Slack, but async. It's an extension of the message board idea, using Reddit-like threads within a Slack context in place of live chat. The free version is live (it's used as a P2P message boards): https://getaether.net https://getaether.net. I think you guys solved it pretty well, but in the case you want a dedicated tool for your workflow, we're currently piloting the private version, happy to give you access if interesting. (email in profile)
- dijit 7y agoOn the surface. This sounds like how Microsoft teams is designed. (More of a message board with comment threads) Do you know how Aether aims to be different?
- 7y ago