ITIL Knowledge Management: Articles, Self-Service and Keeping Knowledge Alive

The same question is asked a hundred times because the answer is in one person’s head. When that person leaves, the answer leaves too. Knowledge management maintains and improves the effective, efficient and convenient use of information and knowledge across an organisation. In service management, it makes support faster, makes self-service possible and protects the organisation from the loss of its experts.

Data, Information, Knowledge and Wisdom

LevelDescriptionExample
DataRaw factsError code 0x80070005
InformationData put in contextThis code means “access denied”
KnowledgeInformation combined with experience, used to actAccess-denied errors on this application are usually fixed by resetting permissions
WisdomJudgement about when and how to apply knowledgeKnowing when a reset is inappropriate because of a security concern

Explicit and Tacit Knowledge

Explicit knowledge can be written down: procedures, articles, diagrams. Tacit knowledge lives in people’s experience and is harder to express: the instinct of a senior engineer that “this smells like a DNS problem”. ITIL refers to the SECI model, which describes how knowledge moves between the two forms through socialisation (sharing experience), externalisation (writing it down), combination (joining pieces of explicit knowledge) and internalisation (learning by doing). Good knowledge management encourages all four.

What Goes in a Knowledge Base

  • How-to articles for users: reset a password, connect to Wi-Fi.
  • Troubleshooting articles for agents: symptoms, checks and fixes.
  • Known errors and workarounds from problem management.
  • Runbooks and procedures for operations teams.
  • Policies and service information: support hours, service levels, contacts.

The Lifecycle of an Article

  1. Create: capture the solution as it is found, ideally during the ticket.
  2. Review: check accuracy, clarity and security (no passwords or personal data).
  3. Publish: make it available to the right audience, internal or public.
  4. Use and rate: link articles to tickets and ask whether they helped.
  5. Update: refresh when the service changes or feedback shows a problem.
  6. Retire: archive outdated articles so they stop misleading people.

Writing Good Articles

  • Use a title that matches how users describe the problem (“Cannot connect to Wi-Fi”, not “WLAN authentication troubleshooting”).
  • State who the article is for and what it solves in the first lines.
  • Use numbered steps, short sentences and, where useful, screenshots.
  • Include what to do if the steps do not work.
  • Record an owner and a review date.

Knowledge-Centered Service (KCS)

A popular approach in service desks is Knowledge-Centered Service, in which knowledge is captured and improved as part of solving problems rather than as a separate task. Agents search before they solve, reuse an article if one exists, fix it if it is wrong and create one if none exists. This keeps the base current and tied to real demand. KCS is a separate methodology from ITIL, but they fit well together.

Self-Service

A good knowledge base is the foundation of self-service. If users can find an answer in two minutes at midnight, they do not need to raise a ticket. Make the search forgiving, show the top articles on the portal and offer suggestions as users type a ticket summary. The ability to deflect tickets is one of the clearest returns on investment in ITSM.

Worked Example

A service desk notices that “VPN error 809” is the top contact in a month. An agent writes a short article: symptoms, the router setting that causes it and the fix. After publishing, they add the article to the VPN page on the portal and to the chat bot. Over the next month, contacts for that error fall by more than half, the article is rated helpful by most readers and the agents have a standard answer. The problem team also uses the data to ask for a permanent fix.

Metrics

  • Share of tickets that link to an article.
  • Article views and helpful ratings.
  • Self-service resolution rate.
  • Number of articles past their review date.

Common Mistakes

  • Creating large numbers of articles that no one reviews, so the base fills with errors.
  • Writing for the author rather than the reader.
  • Treating knowledge as a separate project instead of part of daily work.
  • Failing to retire outdated content.
Key takeaways
  • Knowledge management makes information available when and where it is needed.
  • The SECI model shows how tacit and explicit knowledge convert into each other.
  • Capture knowledge while solving tickets, review it, rate it and retire it when outdated.
  • A good knowledge base enables self-service and reduces ticket volume.

Related Lessons