Make "Teams" and "Chat" the same Tab
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.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
Adam Oakley commented
I'm not sure if making them the same tab is the right answer but I voted because right now it's a little confusing.
Favorited channels should be at a higher level, I shouldn't have to open a team to get to a channel in my opinion
Eduardo Spitzner commented
It already exists a suggestion of this. I understand that is better vote in the same suggestion than crate a lot of paralels suggestions.
Samuel Sze commented
True, there are minor differences between the teams chats and direct chats... But in terms of navigation and notifications, knowing where to look for messages, I think it makes more sense to have them in the same list. What I am hearing from colleagues right now is that people find it hard to know when they are being messaged in Teams, and where to look for messages. If I get pinged and there are two different alerts badges for messages, thats confusing imho... This is something those other chat apps do better
Its 2 diffrent tab, one is alternative for Skype for Business other is for Groups Sharepoint, Planner, Notes etc.
Laurent Lee commented
There is no conversation blocks (like you can create several conversations, and people can reply to specific ones) in chats, or said otherwise, the chat is just a big single conversation.
I see a difference, but I agree with you that it's minimal.
Yoav Rheims commented
I don't know if Microsoft ever intended to do everything like Slack or Hipchat...
That's to say I see a difference between teams and team conversions.
Actually teams could still be a separate tab, but team conversations should be in the chat tab.
The core of this for me is that I need to be able to track multiple conversations both at a channel level as well as a direct level.
Yannick Laurent commented
I agree. interface too complex. too many tabs.
Sorry to mention Slack again, but it's one of his strenght : Lite interface. Onboarding is simple. That's the main key for adoption.
Chris Hendricks commented
Absolutely agreed. It's a broken record, I'm sure, but just look to Slack for how this can be cleanly done: channels up top, direct messages below, and if you minimize the UI bloat you could fit a dozen of each on a normal size window.
Caleb Begly commented
For those that don't like having to expand the team subgroups each time, you can make them stay expanded.
Click the three dots to the right of the team name, and click "Favorite".
Then that team and all its subgroups will remain expanded, and it will be easier to use. I don't know why they don't just add persistence to the expanded/not expanded state, or why it isn't expanded by default, but this does fix it.
Bruce Chapman commented
There is no need for three-level deep navigation. Please don't make me have to think about it. Show all chats / channels as equal importance, and you can throw in meetings/files if you absolutely have to.
Agreed. I feel like the Threaded format is unintuitive to most users, especially anybody familiar with literally any chat application in history, not just Slack - Skype, AIM, IRC, Jabber, etc. It's an awkward communication design that forces users in a channel to constantly think in terms of multiple partitioned conversation threads, rather than one single continuous chatroom. We get lots of complaints from team members not getting notified of new messages in a channel because people forget they need to @ the Team, and folks naturally want to just send messages with the main "Start a new conversation" text box instead of using their mouse to click Reply on a thread.
I understand the idea behind threading but to reiterate it's unintuitive to most people and since there's "regular" chatting in the Chat view it seems silly to not at least have the option for that modality in Teams view.
Mattias Nordgren commented
This is one of the main objections to start using Teams instead of Slack for us.It seems several other suggestions are touching on the same subject (see below).
We would ideally like the option to toggle between "chat view" and "threaded view" for each channel in the channel tab view for a team. Possibly combining this idea with an isolated chat view for a specific thread, as suggested in:
Other suggestions on this topic are:
There may be more like this, I only browsed to page 12...
Slack does a great job of this!
I find it annoying to have to switch between the chat and team panes all the time. It would be better if the list of channels and chats were combined and it would also mean I could see new messages more easily.
andy visser commented
Tedious and (as far as I can tell) not keyboard friendly.
I want to cycle between chats and teams like I cycle between tabs in a browser.