Jim

My feedback

  1. 206 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Public » Getting Started  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  2. 10,523 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1200 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim commented  · 

    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.

    Jim commented  · 

    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.

    Jim commented  · 

    "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
    https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16925779-hide-the-reply-button-under-every-message

    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.

    Jim commented  · 

    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.

    Jim commented  · 

    The comment below had a great deal of right justification ... removed. Ironic.

    Jim commented  · 

    Based on the 585 comments so far ...

    Teams is not suitable for professional programmers.

    There is

    too much

    white space

    and distracting lines

    and colors

    The right justification is crazy.

    Teams

    violates all of the

    rules for communication.

    Signal strength

    is very, very low. And

    noise is very, very high.

    It is apparently

    difficult to communicate
    this concept to those who

    handle the requirements

    at Microsoft.

    Suggestion:

    Make this comments
    section use the
    same layout as Teams.

    And, see if you find it

    as difficult

    to read

    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.

    Jim commented  · 

    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.

    Jim supported this idea  · 
    Jim commented  · 

    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"

  3. 720 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    183 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    Jim commented  · 

    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.

    Jim supported this idea  · 
  4. 732 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    135 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  5. 1,568 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    166 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    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.
    -Warren

    Jim commented  · 

    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.

    Jim supported this idea  · 
  6. 1,992 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    197 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Warren responded

    Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.

    As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
    For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”
    http://microsoftteams.uservoice.com/forums/555103/suggestions/19224826

    Jim supported this idea  · 
  7. 6,543 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    571 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    ~Alex

    Jim supported this idea  · 
  8. 34 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim commented  · 

    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.

    Jim supported this idea  · 
  9. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim shared this idea  · 
  10. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim commented  · 

    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.

    Jim supported this idea  · 
  11. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  12. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  13. 1,887 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    248 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.

    -Warren

    Jim supported this idea  · 
  14. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jim supported this idea  · 
  15. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  16. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Emojis and GIFs  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  17. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  18. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  19. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
  20. 45 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jim supported this idea  · 
← Previous 1

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.