Knowledge Base Fundamentals
The knowledge base at Meridian Parts has four hundred and twelve articles. Three of them were opened last month, one by the person who wrote it. The desk still answers the same eleven questions by hand every week. The article that answers each of them is in there somewhere, under a title nobody would ever type. It sits in a category that was renamed twice. It was written for a version of the system that was replaced the spring before last. Everyone agrees the knowledge base is important. Nobody has read it since the day it was announced. A knowledge base is not a place to put things. It is a thing people use, or it is a filing cabinet with a search box.
This series is about building the kind people use. It covers what a knowledge base is for, which is three jobs, and why most are ignored, which is three habits. It covers a structure that stays navigable after the first hundred articles. It covers ownership, so that every article has a name on it and a date it will be looked at again. Then come the first twenty articles, taken from the top of the ticket queue and written in a week. It covers maintenance without a documentation day, because the documentation day is never coming. And it covers a thirty-minute health check with ten signs and a fix for each. Start with twenty articles that answer real tickets. The four hundred can wait, and most of them can wait forever.
Articles in This Series
- What a Knowledge Base Is For, and Why Most Are Ignored
The three jobs (answer the user, answer the technician, remember the fix), why knowledge bases die, the test of a living one, and the purpose card. - A Knowledge Base Structure That Stays Navigable
Flat with good titles beats a deep tree, categories that mirror the ticket categories, articles named by the question, the search-first assumption, fixing a sprawl, and a starter structure. - Ownership: Every Article Has a Name on It
An owner per article and an editor for the whole, review dates, what happens when nobody owns, the handover when the owner leaves, and the ownership register. - The First Twenty Articles: Start From the Ticket Queue
The top twenty ticket types become the first twenty articles, written in a week with the whole team; what to skip for now; and the seed list worksheet. - Knowledge Base Maintenance Without a Documentation Day
Review on reuse, marking an article stale, the quarterly sweep, retiring rather than hoarding, the change that triggers a review, and the sweep sheet. - A Knowledge Base Health Check in Thirty Minutes
The ten signs of a sick knowledge base, the numbers to pull, the fix for each sign, and the health check sheet.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.