Forum Discussion

forbesn's avatar
forbesn
Copper Contributor
Jan 04, 2021

Knowledge Management Solution Recommendations

I've been tasked with finding a Knowledge management solution for our IT department.  This would mostly be for our own staff.  Something techs and system admins could search.  It would contain info on installing and troubleshooting software and hardware.  It needs to be able to easily incorporate images.  We add a lot of screen shots to our documentation.  Our programmers are also looking at a tool for code management and documentation but it would not have to be the same tool as their needs are quite different.  I've been tasked with this because I seem to be the only one who actually writes documentation.  I have multiple OneNote documents that I've set up in a SharePoint library.  While this works for me, I cannot seem to get others to create their own or to search for my documentation - they are always asking where some document is at.

 

My boss dislikes SharePoint and originally thought Teams was a better location for our documentation.  While good for project management, I don't like it for a permanent documentation repository.  Search just doesn't work that well in it yet. (And we create too many teams and channels in my opinion.)  It took him awhile but after using Teams for some documentation himself he understands my frustrations with it.   So I'm supposed to look at other options.  Before I download multiple Wiki solutions to try, can someone make some recommendations on how to go about a knowledgebase within Office 365?  The existing wiki solutions in SharePoint are cumbersome.  I've also tried Blog posts - but adding the images is a pain - although the blog posts seem to be the most searchable.

1 Reply

  • Jennifer1421's avatar
    Jennifer1421
    Copper Contributor

    Hello Nancy, you mentioned you created a SharePoint library...but that you "...cannot seem to get others to create their own or to search for my documentation". How is your naming convention? I had this issue and what worked was getting users involved in creating a very simple straightforward naming convention - using terms the team collectively agreed on. Just a thought. I am interested in what you find with a knowledge base in Office 365.

Resources