Drop the "Wiki"
Multi-Wiki considered harmful. Our company already has "a wiki". Then Microsoft Sharepoint encourages a proliferation of "wiki" sites, and now we have another entirely separate place for more "wiki" pages.
The main advantages of a wiki are:
1) everyone can participate -- any problem or oversight can be corrected by any user
2) search -- finding things is easy
Having an endless supplies of wikis, where you can't search between them, and not everyone can even view them all, seems to defeat the main benefits of a wiki. Now every channel, in every team, has their own "wiki". And they're "private" by default.
Not only that, but it's namespace pollution -- if you tell someone to update the wiki, how do they know which one?
PLEASE, drop the "feature" of having a wiki from this software.
If you had implemented a full contact system, with support for multiple addresses, and pseudonyms, for every user of the system, that would be terrible. Because Microsoft Teams is not the place for it. Hopefully the product manager would see that, and fight to remove it. I see having a "wiki" in MS Teams the same way.
Joel Elliott
shared this idea
30 comments
-
Larkin
commented
I agree with Jevgenij, Ian, Mark and to a dregee Tim. Don't call this a wiki if it does not have wiki features (that also goes for SharePoint, but Teams' wiki is not even close). If you want a notepad, great: call it that, or steer users to OneNote.
Microsoft should stop abusing the term 'Wiki' ... if it doesn't allow wikimarkup and features like MediaWiki, Confluence, any of the numerous true Wiki softwares & implementations.
-
Jevgenij Martynenko
commented
The place to put some notes might be a valid use case for Teams channels.
But it should not be named Wiki. -
Dev
commented
I'm not sure this was ever meant to be a full wiki, just a place to put editable but semi-static information, like 'how to use this Team' and any team-specific etiquette. Having one of these per team then makes sense. I guess it could be called something else... I use it, but would prefer to be able to populate it with my own default text.
-
Anonymous
commented
"I don't wanna use this feature, no one else should use it either. I know better than you"
-
Anonymous
commented
Totally disagree. The wiki in Teams is very useful. I love how you can call people out in there, inviting commment.
-
Peter McDermott
commented
I agree it isn't helpful to have a Wiki for each channel. At the same token, without being able to add screenshots, the Wiki is very limited. Image and embed support, maybe???
-
Anonymous
commented
I use the Teams Wiki for my project status reports. It work well until I need to move them up or down. I can't drag and drop so it takes ages :(
-
Tim Conroy
commented
Sorry to differ here guys, but here's an alternate idea... add Sharepoint wiki support in Teams. More importantly, add search support for wikis the user has access to.
Not everyone uses Sharepoint, and for the primary purported purpose of Teams (intra-company communication/collaboration), having a SIMPLE (Sharepoint, I'm looking at you) wiki is a good feature, as long as it's usable.
-
Ian Holmes
commented
Microsoft, I am very disappointed in you about this wiki thing. You honestly give administrators the ability to enable Memes, yet we can't perform simple data governance and compliance tasks on these dumb Teams wikis? Let us turn them off. Like Joel said above, we already have a Sharepoint, at best having a team wiki is redundant, at worst it may lead to noncompliance!
Give us an option to turn off these wikis!
-
Mark M
commented
Agree the amount of wikis is confusing.
I see the value of this ability simple as a Notes page and that what we use it for, not as a 'wiki' per se