3 ms·
> these folks haven't even bothered to actually use the software and realize how much more it does beyond sending messages back and forth Are you saying that s
by criddell 5y ago
> these folks haven't even bothered to actually use the software and realize how much more it does beyond sending messages back and forth
Are you saying that sending messages back and forth involves a lot more complexity that you don't see or that Slack does a lot more than just messages?
- tshaddox 5y agoThat's kinda a "gotcha" question, because it's not clear what your definitions are. For example, is authentication (single sign-on, etc.) part of what you describe as "sending messages back and forth"? Are files, screen sharing, video calls, etc. still "just messages"?
- criddell 5y agoI didn't intend it to be a gotcha question. > Are files, screen sharing, video calls, etc. still "just messages"? I wouldn't think any of those as messages that a basic message-only client would have. I guess that's the distinction I was after - was the person I replied to talking about all the complexity of a basic message-only client, or were they talking about the complexity of all the stuff beyond that.
- jacobr1 5y agoI suspect most people in the "Slack is a just a pretty IRC," are discounting the non-text-messaging features. Beyond both the items already mentioned and the ease of adoption, the major benefit to slack is the integration ecosystem. SlackOps is a really big thing. Making slack the glue across variety of operational systems to coordinate the activity of a team and allowing that team to communicate about it, provides a ton of value. And importantly, allowing this to happen organically with non-IT staff creating their own workflows (in the way that people invent alls sorts of min-apps in spreadsheets) is pretty powerful.
- criddell 5y agoWe never used it for anything except messages. Now we're on Teams. I'd be curious how many users were like us - messages only?