Problems in the enterprise Knowledge Base Wiki

It is believed that many companies use the Open source Wiki web app to build their own internal Wiki services, such as Media wiki, Gollum, Doku wiki, Jswiki, etc.

However, the truly usable enterprise Wiki system does not appear, why?

First, the Enterprise Wiki goal is to assemble documents, precipitate technical results, facilitate search to improve efficiency, reduce maintenance costs, and avoid a transition to a small number of employees to form a dependency.

The current internal wiki system has a basic problem, that is naïve to think that there is no incentive, no interaction, no KPI indicators, the company's employees will be like Wikipedia enthusiasts as active, expensive to complete the task of the time to enrich the wiki system nobody cares about.

Second, there is a difference between the wiki and Wikipedia, which is that the document relies heavily on a project's scenarios and artifacts, and lacks the ability to connect to project-related & deliverables.

The result is the separation of the descriptive text from the entity's outcome document, which is prone to a serious consequence of information truncation and the disappearance of cohesion.

Finally, without a user base like Wikipedia and a lack of industrial management drivers, wikis are mostly empty shelves, and no one is going to write it.

Above!

Problems in the enterprise Knowledge Base Wiki