We want to extend a huge thanks to all of you who have engaged with us on this topic of compact chat. Your input has been invaluable and helped inform our design and decision-making.

As we look to 2019, we will be pursuing plans to continue to make the product more and more space efficient. We see this as a guiding design principle, as well as a backlog of requests from UserVoice that we catalogue, discuss, debate, brainstorm and problem solve.

This principle is also why we will not be making a sharp design turn towards a permanently heavy dense design. Our user base is a wide range of people — such as high school students, the visually impaired, open source developers, and your every day knowledge worker. Because of our broad reach, we must maintain a standard of usability that meets many visual needs.

Lastly, we are seriously considering a compact mode. This would be an option — a switch, you might say — that makes everything quite dense. We are entering a new phase of product development that makes this more possible than before. To that end, I’m changing the title of this request to “Compact Mode.” We’ll keep you abreast of these plans as we learn more ourselves.

Meanwhile, we really appreciate your patience, your feedback, and your support of Teams. Thank you for being part of #MicrosoftTeams!

Sincerely,
Suphatra

Hi everyone, thank you for your patience since the last update.

We want to extend a huge thanks to all of you who have engaged with us on this topic of compact chat. Your input has been invaluable and helped inform our design and decision-making.

As we look to 2019, we will be pursuing plans to continue to make the product more and more space efficient. We see this as a guiding design principle, as well as a backlog of requests from UserVoice that we catalogue, discuss, debate, brainstorm and problem solve.

This principle is also why we will not be making a sharp design turn towards a permanently heavy dense design. Our user base is a wide range of people — such as high school students, the visually impaired, open source developers, and your every day knowledge worker. Because of our broad reach, we must maintain a standard of…

Both would be good, but I'd lean to density first over compact. Also a big win that i know was mentioned related to this UI enhancement was making separate threads more clearly distinct...so threads don't blur together, and so the reply to most recent thread doesn't blur to the box for a new thread post at the bottom (where users accidentally start a new thread when they intend to reply to the last thread). Is something like this still forthcoming for the UI enhancments?

Noticed it has been over 2 years since this request was submitted. And pretty sure it has been at the top of the list for most (if not all of that time). I gather from survey you all are looking at some additional/related changes, which is fine, but it would be great if MS would just implement the base feature that has been requested here (the ability to change access to a given channel to be a subset of the full membership of the group) sooner rather than later, and then add other changes at a later time if you decide to do so.

we are getting requests weekly to be able to make channels available to subsets of the members of the team (i.e. privatized to that subset of users rather than all members of the team). Without this ability, users have to make an entirely separate team for each different audience. Sometimes a team wants a channel to only be visible to some members of the team, while still keeping that channel within the context of that team (rather than making a separate team/location). Please implement this.

I get the save as option, and use it myself, but i also know people in my company that have paid for 3rd party product just to have a drag/drop UI to get emails/attachments into sharepoint; so from a user experience perspective, it can make a significant difference.

We have thought this through and decided to prioritize other user-requested items, so this one has been declined. But please don’t stop telling us what you want, because we’re still working to get many of those done. We’re listening and appreciate your support and patience.

The general channel can be home for the entire team, but presumably each channel (which is a folder in the "files" doc library and has its own conversation) would be nice to be able to nest sub-channel for further organization of sub folders of files, and for separating out sub-topics of conversations/projects