Yeah, what you just said is probably the case for the majority of Slack's users, and I get that.
My perspective is framed by working with an EMS provider (PCB design & assembly) who does business in some highly regulated fields. We've started using Slack in the last couple months for some of our teams, and love it, but the idea of using it as a catch all strikes me as questionable.
If we used Slack for actually talking about the design/assembly portion of the business, and not just coordinating sales and marketing efforts, our customers would flip shit. And rightfully so.
I own a contract manufacturing company in China, had similar concerns. We implemented an open source Slack alternative that runs on our own server. Project is called Zulip --> https://github.com/zulip/zulip
I feel like I came across that as I was weighing the various options for us to try haha. Zulip is the kind of thing I'd love to give a shot, but I have to take into account people who won't be tech savvy enough to use something like that. Therein lies Slack's value to us.
At the end of the day, Slack is really useful, but I just don't see its use getting expanded much. At least for us. There's lots of stuff that just shouldn't get communicated across there. Coordination across the sides of the business that don't use Slack wasn't an issue in the first place, it was never really even considered afaik.
My perspective is framed by working with an EMS provider (PCB design & assembly) who does business in some highly regulated fields. We've started using Slack in the last couple months for some of our teams, and love it, but the idea of using it as a catch all strikes me as questionable.
If we used Slack for actually talking about the design/assembly portion of the business, and not just coordinating sales and marketing efforts, our customers would flip shit. And rightfully so.