Skip to content
IT Canvass
Service management deep-dive · Lesson

Knowledge management

Quick answer

Knowledge Management captures what the organisation knows, fixes, how-tos, policies, so users self-serve and agents stop solving the same thing twice. Done well it is the single biggest lever on ticket deflection.

Key takeaways

  • Knowledge bases & articles
  • KCS: knowledge in the flow of work
  • Access and feedback
  • How it connects
  • Common mistakes

Knowledge Management captures what the organisation knows, fixes, how-tos, policies, so users self-serve and agents stop solving the same thing twice. Done well it is the single biggest lever on ticket deflection.

Knowledge bases & articles

Content is organised into knowledge bases (IT, HR, Facilities), each with its own owners, categories, workflow and access. Articles move through a lifecycle:

Draft --> Review --> Published --> (Retired) a publish workflow enforces review before anything goes live

KCS: knowledge in the flow of work

The strongest programs follow Knowledge-Centred Service (KCS): agents create and improve articles while resolving incidents, not as a separate chore. A resolved incident becomes a draft article in one click, capturing knowledge at the moment it's freshest.

Access and feedback

User Criteria
Controls who can read or contribute to each base, the KB equivalent of ACLs. Prevents leaking internal content.
Search & suggestions
Surfaces articles in the portal and inside the incident form as contextual suggestions.
Feedback & flags
Readers rate usefulness and flag stale content for review.
Versioning
Track article revisions and republish safely.

How it connects

Articles deflect incidents at the portal, publish problem workarounds, and increasingly feed AI search and Now Assist answers, which are only ever as good as the underlying knowledge.

Common mistakes

  • No review lifecycle, so articles go stale and lose trust.
  • Ignoring user criteria and leaking internal content to end users.
  • Treating authoring as a side project rather than part of resolution (KCS).
  • No feedback loop, so bad articles are never found and fixed.

Want to learn this properly?

Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. The top-level container for articles is a:

    • A. Knowledge base
    • B. Catalog item
    • C. Business rule
    Show answer

    A. Knowledge base

    Knowledge bases hold categories and articles.

  2. The typical article lifecycle is:

    • A. Draft → Review → Published → Retired
    • B. Open → Closed
    • C. New → Resolved
    Show answer

    A. Draft → Review → Published → Retired

    Articles are drafted, reviewed, published and eventually retired.

  3. KCS encourages agents to:

    • A. Never write articles
    • B. Capture knowledge while resolving incidents
    • C. Delete old incidents
    Show answer

    B. Capture knowledge while resolving incidents

    KCS builds knowledge as part of resolving work.

Frequently asked questions

What does the term Knowledge management refer to in ServiceNow?

Knowledge Management captures what the organisation knows, fixes, how-tos, policies, so users self-serve and agents stop solving the same thing twice. Done well it is the single biggest lever on ticket deflection.

What is the ITSM role of Knowledge management?

Articles deflect incidents at the portal, publish problem workarounds, and increasingly feed AI search and Now Assist answers, which are only ever as good as the underlying knowledge.

What is the practical takeaway on Knowledge management?

Content is organised into knowledge bases (IT, HR, Facilities), each with its own owners, categories, workflow and access.

What tends to go wrong with Knowledge management?

No review lifecycle, so articles go stale and lose trust. Ignoring user criteria and leaking internal content to end users. Treating authoring as a side project rather than part of resolution (KCS).
CallWhatsAppEnquire