Michael Rayman

My feedback

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

    We’ll send you updates on this idea

    76 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This item is still under review by the feature team. I have no details as to when a decision might happen.

    -Warren

    Michael Rayman supported this idea  · 
  2. 2,915 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    79 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
    Hopefully this will move back up in the queue soon.

    -Warren

    Michael Rayman supported this idea  · 
  3. 1,954 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    73 comments  ·  Public » PowerBar  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Rayman supported this idea  · 
  4. 3,891 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    341 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Rayman supported this idea  · 
  5. 309 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    Thank you all very much for the great response. The survey is now closed. The feature team will be reviewing all the data that was gathered and responded based on the findings.
    Again, thank you for helping us make Microsoft Teams the best it can be.
    -Warren

    Michael Rayman supported this idea  · 
  6. 63 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Rayman supported this idea  · 
  7. 140 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Rayman supported this idea  · 
  8. 4,214 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    445 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Rayman commented  · 

    I second the request for wireframes of what the UI would look like to separate the reply from a new conversation. On this separation, this is a difficult UX challenge to solve. Slack and other tools simply don't have to solve this problem because they don't support threaded conversations within a single channel.

    I can see how having this feature could be beneficial, but even the problem it tries to solve eventually surfaces again when you have so many different threaded conversations in the same channel's history, you have to hunt in the channel history to find the conversation you want to reply to or read updates from. It simply makes more sense to see the most recent messages always at the bottom of the chat history so it's a totally flat list of messages organized in time. There may be no way to make everyone happy unless you provide an option by which some can disable threaded conversations on a per-channel basis. I would imagine this would be rather easy as direct message chats don't have this threaded feature.

    Finally, let me just say that the way Teams is currently implemented where your focused text field is always ready to make a new conversation is just so unnatural. Instead, the vast majority of users expect the default text field that has focus after each press of ENTER is to make a reply to the last conversation not start a new one, especially when people are chatting back and forth real time.

    I feel the default behavior should be this:
    * DEFAULT: type a message, press ENTER, type another message, press ENTER. these all are in the SAME conversation
    * Explicit Action: there should be an explicit action to make a NEW conversation so that this is not the default

    Right now, it's the opposite.

    Michael Rayman supported this idea  · 

Feedback and Knowledge Base