That and sometimes the connectedness of their tools means that switching to some new technology means opening a massive can of worms. I've moved my company over to M365 but we are going to continue to use Slack rather than Teams due to the sheer amount of bots and integration we have set up in Slack. It's just not worth the time to re-engineer for the marginal benefit.
But that can be a downside for finding stuff. If everything is in one spot, each time you're looking for something you may have to look through everything. If everything is split up over X spots, you usually only have to look through 1 / X amount of stuff in the spot you're searching.
I just want to say I kind of hate Teams but I am not convinced by this argument. Google has the whole internet for example, but it's relatively easy to find things. And segmenting a search space in X spots is easy, so you can get the same effect in just 1 place.
Yeah. And it will find mountains of stuff for you to wade through, a lot of which you could have avoided (since you know it has nothing to do with this humongous chat app, if it had been made available to search elsewhere in stead of in Teams). So now maybe you won't even find what you're looking for in the sea of search results.
This is related to the "directories vs tags" discussion, and that whole "the kids don't even know what files are any more" thing.
Never used Teams myself, but this sounds more plausible to me. MS stuff mostly works fine, but you need to buy into the ecosystem fully. Usually Unix people try a few MS things, try to use it just like their Unix things, and bash it because it's not exactly the same.
