Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Except the entire use case for teams in our organization (and I'm sure many others) is basically just to chat and make calls. None of the extra stuff is useful to us.
Also you can look at slack which would also be a communications/collaboration platform, and weirdly enough the UX is fine and usable without training. Just admit MS shat the bed and made some Frankenstein abomination that no one knows how to use correctly. It's pretty typical of Microsoft (and apple too) to just deflect that the user is doing it wrong instead of admitting they could improve the experience.
To add to your RV analogy, Microsoft is selling an RV to moms and dads that just want to drop their kids to school. Sure sometimes they go on vacation and the RV is nice, but it's not what the user needs. It's also exactly why users hate it, they are given a monster truck just to go to the shop. (Plus in the case of software, they could have it transform as needed. The communication part could look like a regular sedan, but instead you are forced into the RV format at all times)
Slack and Teams are not the same, Slack is a communications app, not a collaboration app.
I know how to use Teams properly, and I have entire departments (government, universities, etc) that I have trained to use it and they get mad every time their IT departments try to introduce a new product that Teams (and M365) already handle just fine.
Mom and Dad didn't do their fucking research before buying it and didn't bother to read the fucking manual after they did buy it.
Don't tell me the average user is correct when I get called into help offices multiple times a year that are still using Excel sheets to manage their vacation requests, manage their tasks on a blackboard on the wall of the office (even though they're half remote), build their HR forms in Adobe, and have network drives with 90,000 files in 20,000 folders where nobody can find anything all while already owning M365 licenses.
People aren't using Teams' integrated collaboration features properly, and it's not because they're worse than their existing processes and they have some sort of magic ultra-efficient system already, it's because they simply do not know how to use them properly.