I think Teams is exactly excellent because it allows you to secure your collaboration tool. Especially valuable post GDPR where you really don’t want your non-tech savy employers putting privacy data into some online Trello board, or slack/discord for that matter. The fact that teams is just part of your 365 platform is soooo awesome in non-tech enterprise that it’s hard to describe just how useful it is. But basically we have 7000 employees in my shop, 20% of them them can’t name the operating system iOS/Android/windows when they call support. You want your IT to protect them from themselves, even if that’s obviously not how you would word it in your strategy.
Too much control is bad though, like you say, creating channels/teams/task-boards shouldn’t be too bureaucratic. We were a little too liberal when we first opened up, allowing people to name their own, which resulted in mail-list mayhem. Because Microsoft created an e-mail address with the name people chose. This resulted in the “specialised child care department” creating a “specialised childcare” e-mail address, that would show up in outlook. Which in term led to some rather important e-mails getting lost, because people sent them to the one of the now two “specialised child care” email addresses that wasn’t getting read.
We fixed this by moving creation into our own tool and using the 365 API, so people still get to name their own collaboration projects, but they get a “Teams - “ in front of the name, and that’s filtered out of the e-mail listing so they don’t show up in the outlook address book.
I don’t personally like Teams or Tasks all that much functionally wise compared to other tools, but the fact that they are part of our 365 security setup and the fact that we’ve already paid for them, means I’ll use them.