The wiki is too rudimentary.
It is cumbersome to even add a page to a wiki -- let alone find it afterwards. The wiki concept is not new. Standards, or at least the expectations, for what a wiki should work and look like are set. At a minimum, there should be a left panel to act as a content browser. I eventually found something like it. But, it's hidden by default! Why does it need to be hidden at all?
Also, I'm all for minimalist design. But, not at the cost of usability. Editing tools should always be visible. Wikis are meant to be edited to update information -- that's the point. So, hiding the editing tools by default to those authorized to edit seems strange.
Sam Hall commented
Microsoft shouldn't try to shoehorn a **** Wiki feature into Teams. Just provide the integration hooks for decent wiki platforms and be done with it. How much time and effort will the Microsoft Teams dev team have to waste on this feature which is fundamentally flawed? At least change the name to avoid confusion. It's more like a place where people post content that other platforms would consider "Sticky Posts" or at best it's a "Channel Notes" feature. A Wiki it is not.
More than a year after this post, I began adopting Teams.... and I agree with Albert and especially Steve Elkind
Steve Elkind commented
I agree. i view Confluence as perhaps the best wiki I've ever used, and I usually get forced to a poor MS substitute with reasons such as "SharePoint is a wiki". In Teams there are only two levels of hierarchy, and no easy hyperlinking to result in a richer hierarchy. I hate to say it, but the Teams wiki is way too limited to be of much use.