4 ms·
A small, but impactful design choice we made in creating Twist was to leave out the online presence indicator. I imagine you could address this in Slack by jus
by onion2k 9y ago
A small, but impactful design choice we made in creating Twist was to leave out the online presence indicator.
I imagine you could address this in Slack by just having everyone set themselves to 'Away' by default.
One of the things that I've found useful in Slack is turning off the "Someone is typing" message (the option is in the Display Options). I used to wait for someone to post if I knew a message was coming. Now I can drop in and out of a channel more easily. Similarly, I've muted almost all the channels I'm in so now I only need to check if someone notifies me.
The point I'm making is that Slack doesn't necessarily work the way you want right away, and that you might need address a few cultural problems with the way your team uses it. You need to think about how your team communicates, consider why people do annoying things in it, and come up with solutions that work. At the most extreme that might be writing a competitor product but for most companies there just needs to be a little more tolerance of people not answering immediately and a little consideration that gifs can be unhelpful.
- amelius 9y agoIt sounds like you kind of ended up with e-mail :)
- csours 9y agoI would like to see a meaningful discussion of the tipping points between various forms of communication. ie: Phone call when you need immediate, high-bandwith dialog; IM when want to chat, but don't need instant responses; email when you want persistent communications, etc Those are very brief, single faceted views, and there are a lot more factors.
- amelius 9y agoAnd then there is Google Docs for persistent, collaborative communications.
- dsr_ 9y agoUsenet news. 1. You enter groups devoted to large topics (like "all company" or "software development" or maybe "Smith Project") 2. You see conversations delimited by subject lines, completely threaded, with full history. 3. You normally reply to a message with another message, quoting or not, and your message is threaded in. 4. The tools are good for showing you what you haven't read yet. 5. You can ignore a topic forever. 6. You can have filter highlight topics where your name or email address or a keyword is mentioned. 7. You can seamlessly fall back to email for private conversations. 8. There's an archive that goes back to the limit of storage space. 9. Usenet is, of course, easy to distribute and federate.
- edejong 9y agoWow, I love all these features! You're not saying it: 10. Has open-source implementations, 11. Allows HTML formatting, 12. Has a hierarchy of topics, splitting up topics in a generic way, 13. Is blazingly fast, 14. AND allows referencing specific articles using an URI scheme: https://tools.ietf.org/html/rfc5538 https://tools.ietf.org/html/rfc5538 ?
- wst_ 9y agoBlazingly again? I wish people stop using words only because it's cool to do so.
- edejong 9y agoI'm a non-native speaker. I'm guessing you're saying the adjective is dated and reading it again it does sound like that. Still, i was trying to say 'faster than the usual fast' Exorbitantly fast? Snappy responsive? Real-time? (Haha)
- dsr_ 9y agoUsenet was not historically real-time because of several things: 1. There were a lot of servers. 2. The servers were not arranged in an optimal network. 3. The network was full of cross links, many of which made no topological sense. 4. Not every server carried all newsgroups. 5. There were a lot of users, who read a lot more than they write. 6. Binary messages (when carried) grew to huge sizes (for the time). 7. Network links were very slow by today's standards. 8. Disks were slow, small and expensive by today's standards. 9. Every ISP felt it had to provide free Usenet service, but few of them did it well. With modern hardware, Usenet could be as close to realtime as you expect email to be -- dominated by people's attention and writing speed. And carried over TLS, of course.
- csydas 9y agoI would agree that culture is a major factor - we briefly implemented Slack a few years back at a company before I left, and I watched it drive our Senior Programmer nuts, as we didn't really have good solid rules or behavioral standards for Slack. I'm not talking about a tome of laws and regulations, but just a few simple things like "Don't spam chats with non-work related items", "Don't spam looking to get someone's attention", etc. The Senior in question was an older guy who had a lot on his plate and and a bit of a short fuse. It absolutely ended up driving him nuts as now instead of relatively quiet and ignorable chat messages, he was getting spammed and pinged by absolutely everyone at once, and those in the office with less on their plate definitely treated Slack like their own IRC channel for shitposting. Poor support from our management in general, and a poor delineation between private channels and public channels resulted in a lot of private rants being exposed publicly (not just from the Senior), and the end result was Slack was shelved for the time being and the Senior Programmer left the company. My new place of employment utilized a multi-tiered approach, using Skype for quicker questions (with rooms dedicated to specific topics or aspects of the work), and anything requiring more than a sentence or two of background being regulated to an internal message board system. Our management is quick to shut down too much spam, and everyone in general is taught about the expected etiquete of the chat. Without such precautions, I think it's too easy to fall into the more casual "shitposting" that is common for message boards and the chatrooms of old. Workplace chats are meant for very narrow and specific purposes, and it needs to be enforced that these are not the places to be spamming the latest gif you found on reddit/imgur.
- Eridrus 9y agoI think giphy integration is a huge mistake for Slack. I used Flowdock at my last job and it didn't really have the problems people tend to talk about wrt Slack. We also had separate channels for separate teams, so it wasn't one big free for all.
- hfauq 9y agoThe online presence indicator is one of the problems created by Slack. Using real-time chat is the actual problem, whether it's Slack or Hipchat, or anything alike. Real-time is great sometime, but I don't think you should use it all the time: - Real-time chat happens quickly — one line at a time — discouraging full, thoughtful conversations. - Topics are all jumbled together in a channel so it’s nearly impossible to piece together the full conversation. - Important team knowledge — like what decision did we make and why? — gets buried and lost within hours (even with powerful search). - The real-time nature of communication excludes anyone who’s not there in the moment it takes place. - Constant notifications eat into your time and attention. - Even if you’ve turned off notifications, the fear of missing out on something important keeps pulling you back into the app. - It slowly creates a culture that prioritizes being available over doing good work.
- onion2k 9y agoReal-time chat happens quickly — one line at a time — discouraging full, thoughtful conversations. Slack supports shift+CRLF for line breaks, so users can write epic poems broken up in to hundreds of stanzas if they want to. Using Slack as a one-line-at-a-time chat service is a choice that a user makes. Slack itself doesn't enforce it. Topics are all jumbled together in a channel so it’s nearly impossible to piece together the full conversation. Only if users interrupt the current conversation with something else. Again, this is a cultural choice that users make. It's not a Slack thing, or even a chat thing. Also, Slack does support threaded conversations (albeit with a pretty horrible UI). Important team knowledge — like what decision did we make and why? — gets buried and lost within hours (even with powerful search). I totally agree. Slack is not the right place for documenting important stuff. Nor is a different chat app, or email. Important knowledge should be put in a knowledge management app (eg a repo wiki for code, or a Word doc for business related things).
- dood 9y agoIt is true that Slack allows multi-line posts and discrete conversations, but both go totally against the grain of the system design. Expecting people to use Slack in a way it wasn't designed for can only result in failure or constant friction.
- foepys 9y ago> One of the things that I've found useful in Slack is turning off the "Someone is typing" message (the option is in the Display Options). I used to wait for someone to post if I knew a message was coming. Now I can drop in and out of a channel more easily. I've also noticed that being in the dark about some things regarding real-time communication makes me happier. E.g. I disabled WhatsApp's "read" and "last online" indicators not because I don't want others to see mine but because they are useless information that only made me wonder about other peoples intentions. When somebody has read the message and didn't respond, it doesn't mean that they never will but that they were otherwise busy. Just knowing about that didn't keep me from wondering, only turning it completely off did. If I was able to turn off the "typing..." and "online" status, I would, too.