Your knowledge base does not need more pages

A knowledge base can grow every month while becoming less useful. Teams add project notes, policies, recordings and how-to pages, but employees still ask the same questions in chat. The problem is usually not a lack of content. It is a lack of structure and ownership around the moment knowledge is needed.

Organise around tasks and decisions

People rarely search for the internal name of a programme. They search for what they are trying to do: approve a discount, onboard a supplier, launch a campaign or request access. Use task language in titles, navigation and search metadata.

Create one canonical answer

When several pages cover the same question, users choose the one they find first. Designate a primary page, redirect or archive competing versions and link supporting detail from the canonical answer. Duplication creates uncertainty even when every page is accurate.

Give every important page an owner and review trigger

A review date alone often becomes an ignored notification. Tie review to an event such as a policy change, product release, team restructure or system migration. The owner should understand the process well enough to update the answer, not simply confirm that the page exists.

• Use short titles written in the language of the reader.
• Show the last meaningful update, not every formatting edit.
• Archive aggressively when a process ends.
• Capture unanswered search terms and repeated support questions.

Put knowledge inside the workflow

A correct page is still hard to use if people must leave the system where work happens, guess a keyword and scan a long document. Surface relevant guidance in request forms, CRM records, service tools and collaboration channels when possible.

The goal is not a complete library. It is a smaller set of trusted answers that are easy to find, easy to maintain and close to the work they support.