Knowledge Base and FAQ
Level 4 · Notes for a team
How a searchable store of answers lets people help themselves. Writing a useful FAQ, and passing what you know on before you leave.
Course contentsLesson 6 of 6
Level 1 · What you are saving
Level 2 · Taking notes
Level 3 · Note systems
Level 4 · Notes for a team
After this lesson you can
- Say what belongs in a knowledge base
- Write an FAQ entry people can use
- Plan a handover so knowledge is not lost
11 mincovers 3 glossary entries
Worth reading first: Knowledge Silos and Wikis
How do you write answers people can find on their own?
A knowledge base is a searchable store of written answers, guides and fixes. An FAQ is its simplest form: the questions people ask most, each with a short answer. Both let people help themselves instead of asking a person. A good one answers the question before anyone has to send it.
The test of a knowledge base is search. People type their problem in their own words, such as reset password. If the article is titled credential recovery procedure, they will not find it. Title each article with the words people actually use.
A good entry starts with the answer, then gives the steps, then the reasons. One problem per article. Screenshots help, but go out of date fast, so add them only where words fail. Each article needs a date and an owner, so stale ones can be found and fixed.
An FAQ should come from real questions, not guesses. Look at the emails, tickets and chat logs. The questions that come up every week go on the list. A list of questions nobody asks, written to sound helpful, wastes the reader's time.
Knowledge transfer is passing what you know to the next person, so it is not lost. It matters most when someone leaves or changes role. The explicit part goes into the knowledge base. The tacit part needs time together, with the new person doing the work while the old one watches.
A handover that is only a document misses most of it. Plan a few weeks of overlap if you can. Go through the real tasks, not a summary of them. Write down who to call for what, because knowing who to ask is knowledge too.
The common mistake is to write a knowledge base once and leave it. Products change and steps change. A wrong article is worse than none, because people trust it. Check the most-read articles every few months, and delete what is no longer true.
Worked example
A help desk cuts its queue
Olivia runs a small help desk that gets 300 tickets a week. She finds that 10 questions make up 120 of them.
She writes one article for each, titled with the words people use in their tickets. Three months later, those 10 questions bring in 40 tickets a week.
The words for this lesson3
Check yourself
Where should the questions in an FAQ come from?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.