Better visual delineation between `Reply` and `Start a new conversation`
It's very confusing to new users that there is a difference between replying to an existing conversation and starting a new one within a channel. This is a visual thing as much as anything else. The 'reply' buttons are not naturally attractive if you just want to start typing a message. There should be a logical gap between the bottom of a conversation and 'start a new conversation'. 'Start a new conversation' needs to be separated visually, as if it's a second order command rather than a first order...reply.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
Could you as a quick fix … shade the reply area differently, to make it pop out?
Corey Derochie commented
Another way to solve this that I would actually prefer would be for conversations to be tabbed or somehow separated horizontally instead of stacked vertically. I've found the vertical stacking a very annoying visual experience and would prefer different conversations to be different visual threads. Then each thread can have its own distinct reply field.
Microsoft: We have this great idea for threaded conversations in a chat client!
Microsoft: I wonder why nobody has done this before?
Microsoft: Let's just make it, it's genius!
Everyone: ...wtf wait
Microsoft: Why is everyone complaining? Oh well, BLURRY VIDEO BACKGROUNDS!
Everyone: Fix your f***ing chat UI!
Microsoft: *continues playing with *****
-- 2 years pass --
Microsoft: People are still complaining, maybe we should prototype the primary use case of our app?
It is extremely painful to still deal with this obvious UI issue! Why not to just copy it from Yammer?
Greg Solon commented
What's the latest with this? Some people in our organisation have a New Conversation Button, whereas others do not - it doesn't seem to be dependent on a particular version. How is it some people have the button, but others don't?
Newer Teams users are constantly starting new posts when they mean to reply. With the high rate that intelligent people make this error, it's clearly a UI problem. Leads to fragmented posts like "Great question, what do you think Janet?" where Janet then is missing the rest of the context to know what question she's being asked.
Ed Hansberry commented
Please PLEASE make this a priority. At this point I'd be ok if you got rid of the "New Conversation" box entirely and made people click a button to start a new conversation. Anything - ANYTHING - is better than the chaos we have today.
Please prioritize this solution. It is super confusing that people keep starting new conversations for topics that already exist, these break the flow of the conversation. Especially if 5+ users interact in the same channel. Not to mention a whole department.
If at the very least add a new confirmation message to make sure they want to start a new conversation or they are replying to an existing one would be wonderful
Loving the new "New Conversation" button in the latest client BUT feedback from our users is that it is now causing confusion for users. It looks similar to the icon telling you to scroll down for new messages.
Keith Jones commented
One solution that would work for us: make replying to the current conversation the default action, and creating a new one to require a deliberate action.
When typing a response, have the default text there say:
Reply to current conversation. Type @ to mention someone. Type /new to start a new conversation.
To drive home the feeling of separate conversations, prompt for a subject when starting a new one. Keep it optional, but having subjects helps differentiate what's being discussed where and makes it easier to find specific topics while scrolling. If using subjects can be encouraged, that would be great.
Confusion over conversations / chat in channels is the single-most discussed drawback to using Teams over Slack in my org. As it goes, Slack is used for large organization wide chat and Teams gets used almost exclusively for private chat and document collaboration.
Would you mind clarifying why this change is taking so long?
Thanks MS Teams team
Lance Moonshower commented
Please get this done!!! This continues to cause major headaches and has people shying away from Teams because their conversations get so split up and hard to follow. It's to the point of people saying that even multiple thread emails are better because at least they can organize them. Come on MS!
I've been using Teams for two years now, and I *still* do this.
Every single time I do it, I painstakingly copy what I wrote, delete the message, and paste it back into the right place, both to avoid splitting the conversation and as negative reinforcement for myself - which helped, in that now I only do it once or twice a month instead of once or twice a week.
Most people aren't that OCD, though, and so conversations splinter into shards.
This is my least favorite thing about Teams.
Mike Taghizadeh commented
Agreed ... design needs to change.
just copy the system from Yammer and all is fine ;-)
Niclas Lindgren commented
It would help if you by default answered on the last thread instead of starting a new conversation by default, this is what is causing it all.
Definitely feel that you shouldn't have to click to reply - each convo should have a text box underneath with a completely separate button to start a new convo.....
Absolutely - in teams that are not tech savy we constantly get forked conversations because people think they're replying and start a new conversation instead! So referring back becomes a pain as there is no link in the reply.
Барсуг Енотович commented
The users are lazy typers, don't develop "Teams" like them, please!
The MS Admin should really change their comment about filling out the survey and needing feedback since the survey is now closed.