Teams Rolls Out New Conversation Button

%3CLINGO-SUB%20id%3D%22lingo-sub-1652458%22%20slang%3D%22en-US%22%3ETeams%20Rolls%20Out%20New%20Conversation%20Button%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1652458%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EAdding%20a%20New%20conversation%20button%20to%20the%20Teams%20client%20user%20interface%20might%20seem%20like%20an%20insignificant%20UI%20tweak.%20However%2C%20keeping%20replies%20with%20their%20topics%20is%20important%20because%20it%20helps%20users%20find%20information%20and%20helps%20compliance%20searches%20assemble%20full%20conversations.%20Not%20many%20would%20think%20about%20how%20a%20UI%20change%20affects%20compliance%20and%20eDiscovery%20searches%2C%20but%20we%20do%E2%80%A6%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2020%2F09%2F10%2Fteams-rolls-out-new-conversation-button%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2020%2F09%2F10%2Fteams-rolls-out-new-conversation-button%2F%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1652458%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1658458%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Rolls%20Out%20New%20Conversation%20Button%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1658458%22%20slang%3D%22en-US%22%3E%3CP%3EVery%20exciting%20news%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1694107%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Rolls%20Out%20New%20Conversation%20Button%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1694107%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3BI%20really%20wish%20we%20could%20make%20this%20optional.%26nbsp%3B%20On%20a%20small%20screen%20it%20really%20eats%20up%20real%20estate%2C%20and%20always%20makes%20me%20thing%20I%20have%20unread%20messages.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1694361%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Rolls%20Out%20New%20Conversation%20Button%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1694361%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F801875%22%20target%3D%22_blank%22%3E%40Gregory_Kempenich%3C%2FA%3E%26nbsp%3B%20I%20hear%20you...%20and%20others%20have%20voiced%20the%20same%20concern.%20But%20the%20Teams%20product%20group%20did%20lots%20of%20testing%20with%20users%20before%20they%20made%20their%20decision.%20Overall%2C%20I%20think%20it's%20reasonable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1703108%22%20slang%3D%22en-US%22%3ETeams%20Rolls%20Out%20New%20Conversation%20Button%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1703108%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20this%20button%20optional%20would%20be%20very%20helpful.%20In%20the%20past%20this%20was%20just%20a%20text%20box%2C%20and%20now%20we%20have%20to%20click%20the%20%22new%20conversation%22%20button%20to%20then%20click%20into%20the%20text%20box%20to%20reach%20out%20to%20one%20another.%20Sure%2C%20this%20is%20only%20a%20couple%20of%20seconds%20per%20instance%2C%20however%20this%20adds%20up%20and%20undercuts%20efficiency.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1719281%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Rolls%20Out%20New%20Conversation%20Button%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1719281%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efor%20people%20who%20know%20how%20to%20answer%20to%20existing%20topics%2C%20the%20new%20button%20is%20just%20an%20aweful%20time%20and%20workflow%20killer!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
MVP

Adding a New conversation button to the Teams client user interface might seem like an insignificant UI tweak. However, keeping replies with their topics is important because it helps users find information and helps compliance searches assemble full conversations. Not many would think about how a UI change affects compliance and eDiscovery searches, but we do…

 

https://office365itpros.com/2020/09/10/teams-rolls-out-new-conversation-button/

8 Replies
Highlighted

Very exciting news, @Tony Redmond 

Highlighted

@Tony Redmond I really wish we could make this optional.  On a small screen it really eats up real estate, and always makes me thing I have unread messages.

Highlighted

@Gregory_Kempenich  I hear you... and others have voiced the same concern. But the Teams product group did lots of testing with users before they made their decision. Overall, I think it's reasonable.

Highlighted

Having this button optional would be very helpful. In the past this was just a text box, and now we have to click the "new conversation" button to then click into the text box to reach out to one another. Sure, this is only a couple of seconds per instance, however this adds up and undercuts efficiency.  

Highlighted

@Tony Redmond 

 

for people who know how to answer to existing topics, the new button is just an aweful time and workflow killer!

Highlighted

I agree.  We've set up a channel to track who takes which email in our shared inbox and it's better that each one be a new convo every time.  

Highlighted

@Tony Redmond This is an awful feature that our organization does not need. How can we disable?

Highlighted

@echapman AFAIK, you can't.