In my opinion this is very much a double-edged sword. At my organization we have one person (maybe self-appointed) who, when seeing a question asked on a more general channel, invariably responds with something along the lines of “have you checked #super-niche-channel-probably-only-useful-in-this-exact-case?” When I see one of those questions pop up, I usually try to guess the particular sub channel that he’ll try to redirect the asker to but am rarely successful.
But my org may just be using slack wrong. We do have thousands of channels and the same order of magnitude employees. Maybe guidelines about the granularity of channels would be helpful.
Or maybe Slack is just not for me: e-mail is my preferred method for asynchronous comms and I prefer phone calls for synchronous comms because I think the slight friction in having to pick up a phone to make a call helps limit throughout and improves quality of requests. And for info repositories I prefer a curated wiki page to discussion threads for both search and comprehension.
This point is so important.
Some folks seem to think that chat threads can serve properly in this role but in my experience both Slack and MS Teams are nearly useless in the role of "info repository."
Sadly I think Slack was largely marketing and timing: federation was nontrivial (unlike email).
Back in roughly 2015-2016, some of friends were using Slack at their company and were making fun of how antiquated and uncool HipChat was — even though HipChat had all the same functionality. HipChat had the advantage of being a fast, native app, while Slack was a slow Electron wrapper around a web page. But Slack nailed the UX. It had the aesthetics of a generation of "post-Web 2.0" apps that were coming out that were more real-time and shipping as Electron apps. HipChat just looked old school. Pretty soon my company was on Slack, too.
It also helped that Slack quickly got support for a much richer set of integrations with other apps. HipChat had a bunch, but I think Slack realized this would be the number one way to beat the competition, and they spent a ton of effort on building out this side of the platform. Slack, of course, also had the advantage of focus; HipChat was made by Atlassian, who had a lot of different products to spread their focus more thinly.
Around the same time we saw a similar battle between Google Hangouts and "old school" apps like WebEx and GoToMeeting. The latter were/are native apps, rock stable, but fundamentally uncool. Hangouts was browser-based and super flaky, but somehow cool because they were the latest generation of web UX.
What's interesting right now is that Zoom, a thoroughly clunky and uncool native app (very similar to WebEx or GoToMeeting in that sense) has somehow gained enormous market share, despite the existence of decently mature web-based alternatives. Maybe because Google managed to mess up its chat/videoconferencing so badly.
And I think Zoom beat Hangouts because you could invite someone to a meeting and they didn't need to create an account to join.
- Horrible text editor compared to slack (no inline code, no syntax highlighting, lists barely worked, undo barely worked) - notification preferences (per channel) we’re lacking. - no threading support - UI was laggy compared to slack. - there was an very limited set of emojis. - no good mobile app. - few and limited integrations (notably I use GitHub, Jira, and Outlook integrations for slack).
Still hipchat was far better than Teams is today.
No log-in required — just enter the 10 digit code and your name.
Particularly due to the choice of the word "understate."
I know for sure that AOL[1] and Yahoo [2] had enterprise messaging services available for some time, but I think they had both shut down that option because of lack of uptake before Slack was started or at least before it rose to promenence. I'd guess MSN had that feature too, but I don't specifically remember. Segregated scopes being the only option makes a big difference though, and timing is also important; Yahoo was making cool products and killing them because there wasn't enough traction only for the market to show up later for years before Google made that cool. Startup idea: look through old Yahoo new product press releases for ideas that worked but were before their time; if Google did it years later and abandoned it, then it's been shown that an independent team can build it, so you probably can too.
[1] https://www.crn.com/news/channel-programs/18829405/aol-final... https://www.computerworld.com/article/2564773/aol-phases-out...
[2] https://www.internetnews.com/enterprise/yahoo-extends-im-to-... https://www.cnet.com/tech/services-and-software/yahoo-soups-... https://www.cnet.com/tech/services-and-software/yahoo-scraps...
If one answers that with just "workplace chat messaging", Slack looks redundant and unnecessary since the world already had IRC, ICQ, AOL AIM, Yahoo Chat, Skype, etc.
E.g. in the early Facebook years (~2005), Zuckerberg and his team used AOL AIM as their chat system at work because Slack didn't exist. Early Twitter is another example where Jack Dorsey and coworkers used AOL AIM for workplace chat. (Indeed, Jack even said he got inspiration for Twitter from AIM's "away status" feature)
So we have to find the differentiator of Slack that attracted businesses to adopt it instead of just using IRC or Skype:
- Slack lets people subdivide the chat space into "virtual rooms" or "channels" as a 1st-class concept. This is something that the older AOL AIM, Skype, Pidgin client, etc didn't do. This feature is helpful for businesses because you have multiple projects or teams where multiple people collaborate with various subsets of employees. The older chat systems enabled 1-to-1 messaging based on userid but not on "topics" with 1-to-many participants.
- Slack userids are scoped to the company which is more acceptable for private chats within the business. In contrast, the userids in AOL AIM were global ids and therefore not constrained to the particular company's communication. (Slack added ability to chat outside the company recently in 2021: https://www.google.com/search?q=slack+chat+with+other+compan...)
- IRC had topic channels but corporations don't want to hassle with admins setting up internal IRC servers and plain IRC doesn't have desired features such as chat history without additional effort (i.e. IRC bouncer). In contrast, using Slack for workplace chat is just a few clicks in the cloud.
In short, Slack had a combination of some extra useful features and near-zero admin (cloud).