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).
Thats like saying you can drive your car with your feet, the car doesn't enforce driving by hands. The point of this post is saying that slack has these shortcoming by the nature of its design. You can make as many arguments as you want defending it, but everything has a design that influences usage.
That's a slightly odd analogy, but let's go with it. You're right that you can drive a car in ways that are dangerous, and the car doesn't enforce safe driving. The law is what enforces the way you drive (by punishing you for driving dangerously). This is exactly the same as company rules to ensure Slack is used properly. So, yeah, I guess it works pretty well, and people who use Slack badly are "foot-drivers".
In the same way, slack is frictionless to post one-liners; you have to go out of your way to post a multi-liner (and I personally have the constant worry I'll miss the shift and post half-finished in such systems).
It doesn't matter if the law (company) says to drive by hands; you have to be really intent on driving with your feet to get into a car and do such a clearly unnatural thing. It's difficult to imagine someone new getting in and thinking this must be the correct position, because the car does not support it naturally. It can be done, but only while dealing with friction.
Then compare slack to a bbs forum, where people naturally post paragraphs. Not coincidentally, the act of posting has more friction; CLRF is a newline, posting is a button off at the bottom of the page. To get a better ratio of value (writing) to friction, you'll simply have to write more and post less.
The law (company) can enforce unnatural behavior onto its populace, but when the law is unclear or unstated (or ignored) on the particular matter, the natural activity depends on the environment.
And slack is very clearly predisposed to a particular kind of posting.
Expecting people to use Slack in a way it wasn't designed for can only result in failure or constant friction.
one line at a time
no caps or periods
stream of thought
enter each time
I posted a parody of this style a while back:
It takes so much cultural pressure, moaning and nagging to use Slack in a high signal-to-noise manner that I'm quite bearish on it's long-term prospects, and applaud OP's effort at building a system designed more for collaboration than shitposting.
^ as
i never new
* knew
^ is something else
* is to correct
and never use the edit button!
I meant *
thanks
I still fear the web UI. I guess emailing out bullet lists was against the implicit use case the gmail UI team had in mind.
Stuff like this definitely changes how tools are used.
Also, when replying to a long mail thread, showing you the previous list of recipients and requiring you to select those that you want to include in your next mail. Could limit CC sprawl quite a bit.
This way I don't have to worry about hitting Enter at the wrong time. I can also preview the message so I see exactly how it will be formatted, and no one has to see the "mike is typing" messages while I edit.
I also went to the extreme of creating a private Slack team just for myself. I was using the personal channel trick and found that if I included an image in my talking-to-myself message, and then pasted it to another channel, it didn't automatically display the image in that channel. I guess Slack figured the image had already been displayed somewhere within the team even though it wasn't in a public or private channel. I have a feeling this has been fixed by now.
Most companies have a wiki for document, but how many of them can stay up to date? Discussions happen all the time, and they often require changes to previous documents. Maybe an ideal tool is one can capture team communication, present it in a organised way, and let people edit it later for a more polished view.
Do you want to spend time training workflow and enforcing best practices, or a tool designed around desired workflow?
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.
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.
Everything old is new again. (And Usenet is even still there.)
I'm still convinced that Usenet gets ignored precisely because it is federated and mature - it is harder to extract nickels from than a centralized service; user-surveillance and other ad-related choke points are fragmented, it works already, there are already robust end-user filters.
(I also believe Twitter should have been an RFC, not a startup.)
For anyone who wants to build similar stuff for internal use - NNTP is probably not going to be the right choice unless you have a large number of sites. For a startup, IMAP has everything you need built-in for shared, threaded group messaging that looks a fair-bit like usenet (from the client's perspective). If you don't have strong ideas about UI or workflow, you can use an MTA to read and respond, and you're done. If you want your own UI, there are a huge number of IMAP libraries out there for just about any language you want to use.
"Old" tech is a goldmine.
I have this reaction to _so many_ online services these days.
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 ?
Exorbitantly fast?
Snappy responsive?
Real-time? (Haha)
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.
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.
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.
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.