Tips for knowledge base implementation

Pablo -

you might want to look at a true collaborative platform such as Confluence for this purpose, but before identifying a tool, define the objectives and the processes which the tool will support.

Kiron

I had a similar problem a few years ago (I was in construction business as well at the time). What I did was integrating various open source tools and frameworks (server side) to reach it.
If sharing and collaborating is all you need, I would start with Nextcloud (open source) and Nextcloud's web RTC plugin (for VOIP communications and conferences, real time collaboration), since it's multi-platform and works nice in all operating systems (server, desktop, tablet, phone).
My next step was integrating this platform with an ERP based PMIS (thus I had to develop it), where I've chosen Odoo (open source, community edition) as the framework to start from. So, the processes and knowledge areas are in the ERP part, the collaboration is in the collaboration tools more or less integrated with the ERP part.
It was time consuming and sometimes complicated, but in the long run - every action in my organization got tracked, registered, archived and the knowledge base gets bigger every day (sometimes every hour) and it was all worthy.

Pablo,
If you think the information will be needed for a short time, convenient software is a good solution. If you think the information will be needed for longer, organization determines whether or not it's useful.

I've dealt with these issues from the work group level all the way up through the very large enterprise level, and a big part of the challenge is that once the amount of stored knowledge grows, it becomes more and more difficult to find what you need without knowing exactly what and where it is.

I would recommend a KISS (Keep It Simple Stupid) approach. Try not to scatter the info across too many places or it's more places for people to forget. Keep it organized so people know where to look. Keep the data relevant and manageable. This gets harder as you increase the scale but it becomes very important to reduce clutter as time goes by.

The single most annoying problem I have faced my entire career is having access to a vast wealth of information, where you can't find what you need, and what you can find is useless. 100+ people in your situation is enough for data entropy to progress quickly.

You are referring to a Knowledge Management initiative within the organization. There are many considerations to be had when speaking of a true knowledge base.

From a project perspective, absolutely, centralizing content and having an established taxonomy will facilitate the availability and findability of related information.

Platforms such as Confluence or SharePoint will indeed help with this effort. But please be aware that simply adding a tool to your organization's repertoire does not provide a solution.

The right information, for the right people, at the right time, in the right context.