I cant agree with @juliusindi more.
For context, our primary use case is using Microsoft Teams with software engineers and developers. What we've seen happen in our org, is a development team will cling to the "Teams" or "Chat" persona of Microsoft Teams, but not both.
The Teams persona and the individual channels offers certain features we wish Chat had; like inbound notifications, better bot integration, calendars, tab features, @'ing a Tag, etc... But, for our engineers, they don't collaborate well through the primary "Post" functionality of a Team. A post is the mainstay of collaboration in a Team, and it is very clunky for this kind of communication. A post has mandatory threading as everything is grouped into a "conversation". It is greedy with vertical space. Its more akin to a Twitter / X feed for a Team.
The Chat persona, specifically Group Chat offers features that we wish the Teams had; like not requiring everything to be in a Conversation, with mandatory threads. Easy to compose chat UI (easier than a Team channel), with fewer clicks and mouse interaction. Its more natural to collaborate in a Chat, than a Team Channel Post. Back and forth about getting work done is easier to process in Chat, than a Post format.
Why can't you create a Tab in a Teams Channel, which is formatted like a Chat, but inherit the features of that Team Channel? Then the busy, back and forth, collaboration can happen in the Chat tab. And the long standing Posts, announcements, general discussion can happen in the Posts tab? To recycle this idea, you could create multiple Chat tabs in a Team Channel, and key them to conversations, then archive them for reference later. Or, we could assign a Chat to a Team, without a Channel as a parent. As a kind of "Random" or "Misc" Chat to be used for sharing the best meme's of the week :smirking_face:
To quote Microsoft support documentation:
"When you go to any channel in Teams the very first tab is Posts. Think of this as one big group chat. Everyone who has access to the channel can see messages in Posts."
Source
I would argue, that the majority of collaboration between users of Microsoft Teams, who come from an engineering background, do not view the Posts tab as an avenue for group chat. The user experience drives these individuals away from Posts, and into Chat. So, bring the two together so we avoid context switching, and mainstream our collaboration.
