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.
Rollout of the new conversation button to the general public is complete! Enjoy.
838 commentsComments are closed
Good news, only took you 18 months.
Miguel Caldeira commented
I just hope you put 'Start a new conversation' on top of the screen :)
Jacob Andersson commented
FINALLY!!! Looking forward to see how it can improve
Can you share a screenshot or anything so we can see what it might look like?
Geraldine S commented
Looking forward to getting this change!
ed hansberry commented
So 2 more months of disconnected replies? :-(
Glad it is getting fixed, but so so so long.....
This happens constantly, and is such a headache to deal with. i can't even move a conversation, so we just have to tell new users 'yeah, we know, we cant fix it' and gives such a bad first impression of MS Teams that onboarding becomes harder for no good reason. Glad to hear this is being resolved very soon.
Michael Saulters commented
The default behavior when I click in Teams needs to BE 'Start a new conversation' or if a chat with someone is active then 'Type a new message'. Half a dozen times a day I alt-tab over to Teams or I click on it and start to type, but nothing happens because I didn't click in that little message area.
Many of our users push the wrong one when using the PC, but this does not happen on the Mobile App because the Mobile App layout is better. Consider adopting the Mobile App layout for the reply and new conversation buttons.
Had to create this https://imgur.com/a/GKM3RK0 so that i can teach team members how to chat on Teams. Very few people get it for some reason.
Skype DESPERATELY needs persistent popup alerts with the option to set them to "always on top".
I USUALLY never see IM's from Skype / Lyncs
Just dump the entry field for New Conversation
Change the existing 'Format' icon (the A with a pencil) to a button saying "New post"
The only thing to add would be to focus the cursor on the Subject line when the editor opens.
Can't see this taking more than ten minutes.
Everything will work just as it is! Moreover, Subjects would be encouraged (A Big Win as this option is underutilised and forgotten about) as would @mentions.
Then you could use the space gained from removing the New Conversation area for features to search, or list Subjects etc
Especially if you have changed to the dark theme.
My department uses Teams a lot and so everybody gets this distinction. But it's enough to include one or two people in a conversation who don't get it and they overpower the rest of the channel, as they start new threads for every message and others need to switch to replying to these new threads (but the newbies will just create more) or imitate them (thus validating the newbie's way of using Teams).
I think in the short term it could help if after pressing Enter in the new conversation box the focus was put in the 'Reply' box of the new thread. This way a person who's just used to writing a bunch of messages one after another would do so in the same thread.
The reply button should not be on the bottom of every message, its a waste of space. It should be anchored to the right and vertically the middle of the message
Michael Marks commented
I am now leading the roll out of Teams at my second company and this is probably the biggest issue I've noticed. It was a minor issue at company #1 (median age ~30), but at company #2 this is a huge problem (median age ~50).
No matter how many times I demonstrate the difference and importance between 'Reply' and 'Start a new conversation', people still mess it up. Quite frankly, I can see why, and unfortunately, this is hindering adoption.
My 2 cents based on my experience and the suggestions in this thread:
1) Require an explicit action by the user to start a conversation and passive action to reply to an existing one. Right now the explicit action is actually required to reply (i.e. they must click on the reply button). This results in users passively starting to type with the intent of replying, but they are actually starting a new conversation. Making 'start a new conversation' a button like in the Android app could be a simple solution.
2) Make threaded conversations optional for a channel/team, thus making it so a channel could be like a group chat. I used Slack extensively in grad school, and I do miss the free flow of conversation that this promotes. Plus, I've noticed that people of all ages have no issues with the concept of group chat.
I'd be more than happy to do some beta testing for this if you need it.
Keep up the good work! I still believe in your product even if my co-workers don't.
Our use of Teams has brought about the following paradigm.
Outlook (email) is all comms in and out of the company.
Teams (posts) is for all intra company communication.
This works very well and is increasingly 'obvious' over time!
Subsequently, having two text entry boxes confuses this.
I would suggest getting rid of the New Conversation entry field and replacing the 'Format' button as a 'New Post' button. This would:
Opens the full format text editor (but also focuses on the Subject by default).
But offer a dropdown for recipients to auto @mention people.
Then disappears leaving only 'Reply' entry areas.
But also add another side panel/dropdown of all Subjects in the Channel (with a date/time?).
Think about it. All of a sudden the concept of threads is enforced, @mentions are encouraged and a concept of streamlined, 'embedded' email-esque threaded conversations becomes simple, obvious, highly knowledge imbued and contextual.
I agree, I think a more well defined separation between the conversation would help. I seems natural to just start a new conversation for every comment. Then it becomes just one long conversations instead on many active ones at once. Thanks
On Android the use of a FAB for new conversation fixes this perfectly. Just copy that on the desktop app!