Forum Discussion
Wiki/Knowledgebase/Information Sharing
We're trying something new and more Teams-centric for training 'wikis'. We didn't like Teams wikis because they aren't searchable, we're not a big OneNote company so that was a bit complex, and we haven't rolled out SharePoint Online outside of teams usage, so we created a public team and just use the conversations in the channels as a 'wiki'. The channels serve as a high level topic table of contents.
Conversations are easily searchable, each topic is a separate conversation (make sure it has a title), the newest ones show up at the bottom, you can actually ask a question on a topic and have a reply right there. We know we'll have to moderate it to make sure topics don't disappear or other postings. We don't expect a lot of people but it was a fun project to just see how it would work.
- Chad WestMar 14, 2019Brass ContributorI like the concept, but immediately I could see our users abusing a system like that as a workaround for a helpdesk and would forgo the creation of tickets/emails.
- Robin NilssonMar 14, 2019Bronze Contributor
Good point. We might find abusers as well, but thought we'd try it out. I'd rather we could have read-only users of course but that doesn't exist in a team. I wanted to see if we could get users to help other users - our help desk doesn't usually get involved in training issues. And they don't work on anything else without a service desk ticket.
I'm an expert at using the wrong tool for solutions :) Anything more formal and we'd use SPO and site pages.
- Norman YoungMar 14, 2019MVP
I'm an expert at using the wrong tool for solutions :)
LOL.