We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
Just had to check in. Another year passes. Another "Planned" status. Just hilarious. Microsoft keeps telling the world how Teams user count exceeds Slack user count -- FALSE! We use Slack. But, as evidenced by this post, my company is officially using Teams so that Microsoft can claim that there are Teams installed base exceeds the Slack installed base. We would have a mass exodus in our dev teams IF we were forced to return to Teams. It is really that bad. And, this ticket is the chief reason for how bad Teams is. It has been years since developers complained about the interface. Years. And, another year passes.
What prompted me to indulge in this forum is that I was trying to trouble shoot an SSIS package. That package reports that a step failed validation, but refuses to reveal the error message. Refuses. Kind of like Teams refuses to update to a usable interface.
Teams is like this SQL Server function: SELECT ROUND(9.9,0). This will return an Arithmetic overflow. SELECT ROUND(8.9,0) does not. Seriously. Nothing simpler than a ROUND function and it fails. Somewhere there is Microsoft bug report where Microsoft claims that it is "Working as designed". Too crazy to make this up But, then again there is Teams where -- like the SQL Server group -- Microsoft Teams group REFUSES to fix the obvious..
I am a dyed in wool, all Microsoft developer. Rapidly moving to other technologies because of the above problems with Microsoft products. I fully expect to visit this site next year and still find this suggestion still waiting on Microsoft.
Good news! My group of Microsoft developers (and the rest of the company) is moving to Slack today! My company bought Office365 Premium that includes Teams -- which makes it "free" to use. But, even the "free" version of Teams costs too much. As a longtime Microsoft developer, this is a sad day. But, definitely a very good day now that we will have a tool for professional communication.
Teams UI is clearly a problem. But, I am much more concerned about a company -- Microsoft -- that antagonizes developers while publicly stating:
1. "Empowering developers"
2. "Microsoft has been a developer-focused company..."
3. "First, we will empower developers at every stage of the development lifecycle..."
Just a few samples from public statements. And, yet this thread -- primarily developers -- is pointedly ignored. The highest voted UI request ignored.
As reminder, developers and the managers who once were developers make software decisions. Antagonizing recommenders and decision makers is usually considered a negative in sales and marketing.
Teams UI is embarassing. To pointedly ignore your core constituency ... priceless.
Of course, that is just my opinion. I could be wrong.
"still in the works".
Not sure how to take that. I am pretty sure that the Teams team does not understand "compact".
1. Hiding or moving the Reply button has been declined. The Reply button is a major contributor to unused space. Moving or hiding the Reply button is a major step toward a compact layout
2. Teams auto hides comments!!!!! Actual comments. Actual information is auto hidden. But, all the wasted white space remains. Wow. Talk about not getting the message about "compact". For 10,000 years of human communication, humans have iteratively compressed the white space in order to have denser information because denser equals easier and faster. That is why we use alphabets and not heiroglyphics. Compress the white space NOT the information!
For the record: "compact" means more information, less wasted space.
Clearly, Microsoft if NOT reading this thread.
A few weeks ago, on an investor website called SeekingAlpha, the subject of MSFT (Microsoft stock symbol) came up. Developers supposedly are key to Microsoft's strategy. And, then a couple of the comments below the article brought up Teams as a "brand damaging" application. Brand damaging. Interesting choice of words.
Flash forward a couple of weeks and Microsoft announces the the purchase of github with the words "empowering developers" in its announcement. And, then there is Teams -- widely hated by developers as evidenced by the 598 comments and 4,583 votes for a "Professional" layout.
An interesting conflict of priorities at Microsoft. It will be interesting to see how it turns out.
The comment below had a great deal of right justification ... removed. Ironic.
Based on the 585 comments so far ...
Teams is not suitable for professional programmers.
and distracting lines
The right justification is crazy.
violates all of the
rules for communication.
is very, very low. And
noise is very, very high.
It is apparently
difficult to communicate
this concept to those who
handle the requirements
Make this comments
section use the
same layout as Teams.
And, see if you find it
as I do.
And, could you please
give us the ability to copy
& paste code?
I am glad that Microsoft has
many who like this type
of layout. But, it appears
from the comments
that professional programmers are not
in that group of happy campers.
Teams (as best as I can tell) emulates Facebook and Pinterest: big bold around names, avatars that get their very own column, lots of distracting colors, white space as well as boxes that absorb space and add noise. All of this noise makes it very difficult to read or use for communication between professionals. Emphasis on "use for communication".
If the goal of Teams is professional communication, then please remove ALL of the distracting elements -- or provide a means to do so.
As noted by others, the signal strength of Teams is very low and the noise level is high. To be useful, the signal to noise ratio must be dramatically improved.
As a developer specializing in and with many certifications for the Microsoft stack, I had much higher expectations for Teams.
I downloaded and installed the latest Teams version this morning (3/28). Could not tell a difference although it is possible it compressed slightly.
Please remove (or provide a setting that removes) all whitespace -- emphasis on "all". As part of that white space removal, please move the Reply button up to the Name line. Reply is effectively white space because it adds no information. Currently there is white space between every message -- a single pixel line is sufficient for a separator. White space makes the information less dense which slows reading. And white space is an effective full stop that further slows reading. I believe that removing whitespace was the intent of the original request of "create a professional compact chat layout"
You should experience significant improvements in copy & paste of images within Teams, as well as to & from Teams. We are aware of a few remaining issues, but the most common cases are resolved.
Thanks again for your patience on this one.
Co-worker copied an image into Teams. It cannot be copied out of Teams. Selecting the image and right clicking presents an option to copy ... but it will not copy. Attempted on multiple machines.
Image was of a 20 second spike in operations that needed to be investigated. We have a need to and should have been able to share this image beyond the initial limited team.
Feature request is still being worked upon.
This feature request is still being reviewed. The team is working hard to make numerous changes with regards to notifications, but they haven’t forgotten about this item.
I hope to have more details soon.
Missing notifications is so common where I work that most of the time, IF a developer bothers to send a message using Teams, they walk over and let you know.
Chat traffic has dropped significantly since we moved to Teams for reasons such as this one. Its just easier to use another communication method.
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
Agreed. For my money, remove the Reply button completely -- or provide a setting to do so. It wastes space AND it causes a great deal of confusion. Once a Reply thread is started, then it jumps ahead in the sequence such that other replies -- that did not use the Reply button -- are lost. At the very least, provide a setting -- per room -- to remove Reply. A simple hide works.
3 votesJim shared this idea ·
When we first got Teams, this was a problem. Now that people have actually used Teams, it is no longer a problem because most people stopped using chat. And, one of those reasons was this exact problem: it is very difficult to switch between conversations.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
7 votes2 comments · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →