I'd love to hear about things like unintuitive UI, the way notifications work, Slack channel integrations required from 3rd party vendors, Slack bots, permissioning, etc. - the actual business logic that's holding you back I suppose.
2. I don’t want to innovate on “back office”. Slack works, is sufficiently affordable, and costs no social credit with employees.
3. I know I won’t run into problems in the future. This kinda ties into (2), I don’t want to innovate on back office, but to make it concrete: Deel, Rippling and the other M$ AD clones all integrate with Slack to set up permissions and SSO with zero effort.
4. Slack has lots of sensitive info about us and pur customers, which makes it SOC-2 relevant. I want to use “industry standard” tech for anything compliance related. Though I don’t recall that this would have ever been a problem on security questionnaires, and not many years ago Slack was the “young kid on the block” themselves & managed, so idk if this is actually a valid point.
—
If you give me a feature parity clone of slack for half the price, I’d certainly switch, but anything less than feature parity and I probably wouldn’t. I don’t need to or want to take risks on internal tooling.
If the reasons for choosing Slack instead of Discord are business reasons, the choice is not holding a business back. If a choice is not holding a business back, then that's the very obvious reason.
Right now Instagram is our Bread and butter for communicating with the community but there are limits.
Truthfully, I want to migrate more Folks to Fediverse