I really like Teams. I do. But the current chat layout is not suited for professional chats. It's way to space consuming. It looks like something imported from MSN with smiley's that take half of the screen. I would say that Slack have nailed it because they focused on the ability keeping a tight window with lots of chat text visible. In Teams the window is full and starts scrolling after like 10 sentences.
We are working on a design with more density in mind. Until this design is solidified we are putting this item back to Under Review.
Seriously almost a year to remove white-space, to say this is quite disappointing is an understatement. I agree with Accuraty/Jeremy, we are done here are well. Moving to slack and integrate software there instead. There is obviously little to no commitment here to the software.
Accuraty / Jeremy commented
Ok, done here. We are moving to Slack. Complete fail by Microsoft here. I was so excited by the potential here, but zero progress after waiting a year and getting only lip-service promises of progress coming soon... what an incredible disappointment.
Scott Schwalm commented
Is there any update on this? I have been trying to sell my team on teams, but the layout is one of the biggest complaints. We are not a bunch of pre-teens sending emojis back and forth. We need a professional layout.
Charles Rube commented
I didn't realize how significant this one was until I started getting a lot of feedback. There's just too much empty space and makes it less efficient than alternatives (I'm trying hard to sell Teams to a very Slackey company).
Until this 1 thing is fixed/adjusted - Microsoft Teams is unusable. Back to Slack...
Just bad overall. UI is not thought out. Please review Slack or any other chat/message system and see how they do it. Its very confusing and unclear to read or participate in Team Conversations. Make that like chat - its very frustrating! People hate SharePoint - but you made it just like SharePoint. Please redo Team Conversations to be useful or Microsoft teams will die a painful death like most anything Microsoft does social related.
code sharing is awful in teams please use word wrap so i dont have to scroll for days to read
Bill Lockhart commented
I'm here because this was the first, initial impression that my team had for what needed to be worked on as we trial this product. Part of the issue is that they have the icon for the person on the left, then they have their name and timestamp *above* the text (so, likely unnecessary repetition of information), and they leave in place the "<--Reply" indication for every comment (it could be a right click). Removing these two and placing elsewhere or dealing with it differently would help in reducing the space between comments and getting more of the past conversation on the screen space you already have open.
Luis Garcia commented
Still waiting x 11...
Susan Kennedy commented
Ditto comments made so far. Way behind Slack yet having to switch at work. Please improve ASAP.
I apologize Warren, but this is not an update. We need an *actual* update. Give us an idea of what we'll be getting. Prove to us that this is actually being taken seriously and worked on. If a new user or org is shown Slack and Teams, why on earth would someone choose Teams? This is coming from an admin who has made Teams a central part of my company's daily process.
The promise of Teams is a tool that will evolve and be heavily integrated into other Microsoft products. The look, feel and usability of this program as it stands does not deliver on this promise or offer a better experience than the competition.
Sergio Nesbitt commented
Looks like some version of this is already active. If you shrink the window it does do some compact adjustments on the fly which I find meets the need. Have others tried?
Does soon mean months from now? Because last time "soon" was mentioned about 4 months passed before we heard back.
Sean Ellis commented
"No additional update details"
Sorry to be negative, but are you really working on it? Really?
OK, let's avoid details and instead focus on some broad brush questions which are unlikely to change in the few days it should take to implement this feature...
- Will this be an option? (And if not, why not? You will never please a wide user base with one layout - see previous posts ad nauseam.)
- How much more compact will it be? Let's say, a ballpark figure for, say, how much text you can fit in an 800x600 quarter-screen window, compared to speech-bubble mode. 1.1x? 1.5x? 2x?
- Why is is taking so long to make what should be minor parameter changes to the text layout engine?
There's still a week before Christmas - that should be plenty of time to come back with a reply.
The chat consumes way too much real-estate. The bubbles are not necessary. It's not necessary to float them to different sides of the screen - it's unclean. When you type several sentences in a row it doesn't collapse them together. This results in metadata like your username and time&date takes up the majority of the space.
In fact the whole "reply" feature turning it into a threaded chat is going to end up causing more confusion that benefits. It doesn't promote a flowing timeline collaborative chat.
Slack is successful for a reason. Focus more on what works and less on integrations with numerous other office365 features you want to sell.
Thanks for the update, really looking forward to migrating from Slack. This might have been a case where an initial, quick, 'good enough' effort might have helped you more than trying to deliver the perfect thing :)
Jesse McNaughton commented
@Chris Webb: this entire thread is about providing an option for a cleaner, tighter UI. Emphasis on "option." In an ideal world, the entire UI would be configurable, with each individual feature having a separate setting - I could remove the reply button, but you could keep it.
That said, don't presume to tell me that I'm using the product "wrong." It doesn't matter how the product was intended to be used, it matters how customers want to use it. Starting threads is great for interjecting an asynchronous response, but is not a reasonable "default conversation mode" for most users - at least not the users I've interacted with.
Chris Webb commented
Teams already doesn't make it new picture and timestamp for replies, the problem is your starting new conversations for every single chat, use it for how it is dsigned with threaded conversations. Same with getting rid of the reply button, that doesn't make sense and is a huge issue for people that actually do use threaded conversations. If anything reply needs to be more defined and the new conversation should be a button.
Other items can't argue with.
Thanks for update Warren, kind of a let down thou because we seem to be told this is coming soon, then deploying soon, to more info later, transparency would be better than just being left out to dry. Even if you guys told us, testing the new UI was bad, and we need to go back to the drawing board or something is better than just sitting here wondering.
Can we get details of what "worked on" means?
Still being discussed if anything will actually be done?
Design plans in place and being developed/tested?
Teams is unusable in most corporate environments with the way it currently looks plain and simple. 1 year later and not a single thing has been done is crazy.
Please stop the 'one size fits all' BS. Your audience isn't 12. This is (supposed to be) a professional tool. Just give us options to choose from like any good personalizable UI. Seems like you're wasting development energy and time trying to satisfy everyone with a single UI density.