The Horror of Microsoft Teams
medium.com
The Horror of Microsoft Teams
1–10 of 344 posts
Re: The Horror of Microsoft Teams
#2A few more points, in case anybody in the Teams team is reading:
1. Implement filters. Filters for teams, filters for channels, filters for search results. I can't filter my Files by file type, so it's a mishmash of Word documents, OneNotes, Excel, Microsoft Project files, and PDFs. I can't even filter by channel, or search within a specific channel.
2. Search results: Implement filters, as above, but add the ability to sort by anything other than Date Modified. Unless I know a good portion of the document name or it's been modified recently, I'm forced to scroll through the list.
3. Skype integration: We already use Skype for Business. Why is Teams also reporting my missed Skype calls in addition to Outlook and Skype telling me the same?
4. Meetings: Is Outlook transitioning to an email-only client, or are we just going to have all functionality replicated across Teams/Skype/Outlook?
5. T-Bot: I've got this entity in my Chat sidebar; I guess it's the Teams version of Slackbot? Anyway, it sits there saying "What can I help you with today?" Slackbot gives me an example question to begin interacting with it, but T-Bot has the entry window greyed out with the text "Sending new messages to this bot has been disabled." It's not clear whether that's a Teams thing, or something my org did, but why is it even there if I can't interact with it?
While we're on Chat, there's a bunch of people listed in here that I sent a couple one-off emails to. I talk to more people than this; where are those? Why aren't they pulled from my Skype calls?
6. Calls: I see some contacts from one of my Skype groups, but it's also got contacts who a) I've already removed from that list, and b) don't even work at this company anymore. They're still crowding out the people I actually interact with regularly.
7. API integrations: I'm not even sure where to begin. Teams uses the Microsoft Graph API, which requires use of the Azure portal, and if you're already familiar with all that it might work for you. For the rest of us just trying to write a simple Python script integration (a la Slack webhook), it's a bit much.
I'm sure I could think of more, but this non-blog-post is already long enough.
Re: The Horror of Microsoft Teams
#3There's some fun inspecting this data, too..
Re: The Horror of Microsoft Teams
#4Re: The Horror of Microsoft Teams
#5Took me long to realise I was looking at the chat window and to follow along the threads..
Re: The Horror of Microsoft Teams
#6Additionally, you can't seem to attach a .json file... though renaming it to .json.txt works. It's frustrating for sure.
Thankfully they finally fixed some issues recently so I can copy chats out of Teams without running into too many problems.
The most frustrating and immediate drawback is the low information density. It's gotten slightly better, but I can still see only about 20% of the information in a chat that I can with Slack.
Also the automatic conversion of things like ;) to animated emoji... please give me an option to turn this off. You have to ctrl+z afterwards to just use the text.
Re: The Horror of Microsoft Teams
#7At my last job we figured out the fastest way to get your company off Teams: add the CEO to a chatty channel.
Re: The Horror of Microsoft Teams
#8I think Teams is pretty good, but then again my company had been using Cisco Jabber prior to it.
Relative to that experience Microsoft Teams would be a significant improvement in user experience.