There is no reason that Teams and Chat should be different top level categories in the left navigation. They are the same thing, perform exactly the same function, and making two different items simply confuses the navigation and makes badge notifications and discoverability much more difficult to use.

Please combine Chats into the Teams tab so that you can browse all conversations in one place rather than needing to navigate to different tabs to see different conversations.

Chats and channels perform essentially the same function, which is talk to some people and collaborate. Forcing the user to check two different lists to see if somebody is messaging them is a really bad experience, it is like having two different chat apps.

This is one usability issues that makes Teams less usable for collaboration than both Slack and Skype.

The far left navigation panel seems to have a whole lot of blank space just calling out to be filled with things, and there is plenty of functionality within Teams that could be put there so users could reach it faster. That big gap between Files and Feedback is wasted space!

You should let individual users decide what goes in this space by giving them the ability to pin additional things they want there. I use the 'Saved' functionality a lot for example. It would be nice to have it out there only one click away. Perhaps I think a certain person, bot, or channel is important enough to deserve placement out there. Or how about a certain Tab somewhere.

Give the user the choice and allow them to make Teams their own!

When starting a NEW conversation in a Channel, the subject line should be displayed by default and not hidden underneath the rich text expand button. Subject lines are very useful not only to let people know what that conversation is about, but also for searching later to return to the conversation after it has scrolled away some. We've enforced this on a few times internally using the honor system and have seen considerable success with keeping conversations on topic and getting people using the threading features.

You wouldn't send an email without a Subject would you? Why should Teams be any different?

Dear Admins, please get on the same page as your design teams and support staff, they’re giving users contradicting information.

I just had a conversation with Microsoft Support about the ability for a Skype user to talk to a Teams user…basically at this time there is no such thing as interoperability despite their documentation regarding coexistence modes.

The very minute a user even tries Teams just once…they break the ability to use Skype to talk to you if you’re using Teams. Apparently it’s been in this broken state for months and is “by design.”

Here’s the quote from the rep, “Teams is designed to only send messages to Skype for Business if the recipient has NEVER used Teams. Once the recipient like USER B has signed into Teams (even just once), all messages from other Teams user like USER A, would ONLY be sent to Teams.”

The support rep even admitted Microsoft’s documentation does not match this current broken system. There is no actual migration path from Skype to Teams, there is no actual interoperability. If you have a 1,000 users and just one tried out Teams then you have to decide either everyone uses Skype or everyone uses Teams, nothing in between.

It’s crazy but the truth is you can safely disregard everything in this article: docs.microsoft.com/en-us/microsoftteams/tea..

I’m desperately trying to keep Slack at bay in my organization, but this just gives Slack users more ammunition.

Microsoft, please get it together and provide us true interoperability that matches up with your documentation.