In short. A wiki answers “where is it written?”, document management “which is the right version, and who may see it?”, knowledge management “what are we about to lose, and where do we start?”. The three fit together, provided the knowledge management layer can read the other two: that is what connectors are for.
The confusion is expensive. Many organisations buy a wiki believing they are doing knowledge management, then find three years later that they have three thousand pages and still no idea what a departure will cost them. These are not the same tools, and they are not the same questions.
A wiki answers: “where is it written?”
Confluence, Notion, MediaWiki, SharePoint pages: they store text, version it, comment on it and find it again. Excellent for writing together and for retrieving what has been written. Blind, by construction, to what was never written.
Document management answers: “which is the right version, and who may see it?”
Life cycle, approval, retention, traceability, compliance. Indispensable in a regulated industry. But a flawless document management system still does not tell you how many people know how to perform what the document describes.
Knowledge management answers: “what are we about to lose, and what do we do first?”
It starts from knowledge and people, not from files. It measures a criticality, counts the holders, looks at scheduled departures, appoints who must learn what, and organises the handover — interviews, mentoring, validated experience feedback, mastery tests. Documents are attached evidence there, never the starting point.
Do you have to choose?
No. The three layer well together, on one condition: that the knowledge management layer can READ the other two, in order to attach each document to the knowledge it describes. That is exactly what connectors do: your wiki and your document system stay in place, and the measurement sits on top.
The most frequent case is detailed here: Confluence and knowledge management.
Try it free for fourteen days — no credit card.
See also: Confluence and knowledge management: measuring the risk · SharePoint and knowledge management: the connector · Notion and knowledge management: measuring what is critical · DMS and knowledge management: Alfresco, Nuxeo, CMIS, WebDAV · Knowledge management system: a 12-point evaluation grid · A knowledge ERP: what your ERP does not manage
Frequently asked questions
Does a document management system do knowledge management?
No. It manages the life cycle, approval and retention of documents. It does not say how many people can perform what the document describes.
Which wikis and document systems can KnowledgeCapital read?
Confluence, Notion, SharePoint pages and libraries, CMIS 1.1 or WebDAV document management systems such as Alfresco, Nuxeo or Nextcloud, and intranets.
Do we have to pick just one of these tools?
No. The three layer on top of each other: the wiki to write, document management for versions and compliance, knowledge management to measure risk and organise the handover.