> If you want to exclude your Customer Data from helping train Slack global models, you can opt out.
So Customer Data is not used to train models "used broadly across all of our customers [in such a way that ...]", but... it is used to help train global models. Uh.
The caveats are for “local” models, where you would want the model to be able to answer questions about discussions in the workspace.
It makes me wonder how they handle “private” chats, can they leak across a workspace?
Presumably they are trying to train a generic language model which has very low recall for facts in the training data, then using RAG across the chats that the logged on user can see to provide local content.
It's one thing if the input is the published internet (even if covered by copyright), it's entirely another to be using private training data from corporate water coolers, where bots and other services routinely send updates and query sensitive internal services.
We're literally discussing switching to Teams at my company (1500 employees)
I think we start to recognize this at larger scale.
Slack easily saves a ton of time solving complex problems that require interaction and expertise of a lot of people, often unpredictable number of them for each problem. They can answer with delay, in a good culture this is totally accepted and people still can independently move forward or switch tasks if necessary, same as with slower communication tools. You are not forced to answer with any particular lag, however slack makes it possible when needed to reduce it to zero.
Sometimes you are unsure if you need help or you can do smthing on your own. I certainly know that a lot of times eventually I had no chance whatsoever, because knowledge requires was too specialized, this is not always clear. Reducing barriers to communication in those cases is crucial and I don't see Slack being in the way here, only helpful.
The goal of organizing Slack is such that you pay right amount of attention to right parts of communication for you. You can do this if you really spend (hmm) attention trying to figure out what that is and how to tune your tools to achieve that.
Even receiving a message and not responding can be disruptive and on top I’d say being offline or ignoring messages is impossible in most companies.
Regarding “receiving a message”: my devices are allowed only limited use of notifications. Of all the messaging/social apps only messages from my wife in our messaging app of choice pop us as notifications. Slack certainly is not allowed there
Async communications are critical to business success, to be sure -- I'm just not convinced that chat apps are the right tool.
Just don't use the "Team" feature of it to chat. Use chat groups and 1-to-1 of course. We use "Team" channels only for bots: CI results, alerts, things like that.
Meetings are also chat groups. We use the daily meeting as the dev-team chat itself so it's all there. Use Loops to track important tasks during the day.
I'm curious what's missing/broken in Teams that you would rather not have chat at all?
The only downside is their mobile app is a bit unreliable, in that it sometimes doesn't load threads properly.
It's not customer data anymore.
Monies.
> We're literally discussing switching to Teams at my company (1500 employees)
Considering what Microsoft does with its "New and Improved(TM)" Outlook and love for OpenAI, I won't be so eager...
https://www.producthunt.com/categories/team-collaboration
There's also a Lot of "Best Slack Alternatives in 2024" and such.