How to build an enterprise knowledge base
To build an enterprise knowledge base, name which documents count as the rule, who may read them, and which copy is current, then attach the source to every answer. A reply can start as a draft. Questions about people, legal commitments, money, or anything the company says externally need the owner of that topic to approve them before they count.
On this page
List the documents before you add search
List the policies, product notes, and operating steps, and write down the owner and the location of each file. Without that list, search returns the old draft and the current text together.
A question that comes up once, and has no stable document, can stay with the owner. A question that repeats every week and already has a written source is the one worth putting in the knowledge base.
Keep one current copy
If the same policy sits in chat, in email, and on a shared drive, write down which location wins. The others can remain. Search should not treat them as the current text.
When the current copy changes, change the location and the date on the list in the same step. Change only one of those, and people still receive the expired sentence.
Send the reader back to the source
When someone asks in ordinary language, the reply should name the document and where it sits. A paraphrase alone cannot be checked later against the version that was current.
If nothing in the library answers the question, say that it was not found. Do not add a sentence that only sounds complete. Once that sentence is forwarded, it becomes an internal rule with no source.
Keep the permissions the file store already has
A folder a person cannot already open should stay closed inside the knowledge base. What can be searched is the material the company chooses to include, plus the permissions the file store already enforces.
If those permissions are still messy, narrow the folders first, then open search. Pulling in the whole shared drive also releases files that were not meant to be read.
The owner still approves the sensitive answers
A draft can save the time spent hunting for a file. Decisions about people, legal judgement, money, and any statement the company makes outside still wait for the owner of that topic.
Before the work starts, write three things: which folders are in, which location is current, and which topics must be reviewed. Leave those three unwritten, and the knowledge base is only another place to store files.