OBLYTECH Logo
Enquire Now
OBLYTECH Logo

ServiceNow / Practical guide

ServiceNow Employee Knowledge Articles That Get Used

ServiceNow employee knowledge articles become useful when they help a person make a decision or complete a task. A long article can still fail if its title does not match the question, its steps do not match the service path, or nobody owns the next review.

For employee-service and knowledge owners improving the usefulness of ServiceNow knowledge articles..

ServiceNow employee knowledge articlesemployee knowledge managementknowledge article design
Discuss this ServiceNow topic

Guide map

Make knowledge article review repeatable.

Start with the question employees ask

Begin with the search terms and requests employees actually use.

Answer the decision before adding background

Put the decision or first step at the top.

Write steps that match the service path

Use the names the portal and forms use for each step.

The practical framework

Create ServiceNow employee knowledge articles around real questions, clear decisions, useful steps, ownership, review, search language, and escalation.

Knowledge should sit inside the workflow rather than beside it as an unrelated library.

Start with the question employees ask

Use search terms, request descriptions, analyst questions, and repeated explanations to identify the real question. Employees may use everyday language while the article uses an internal service name. Include the language people recognise without turning the title into a list of keywords.

The opening should answer the question or explain the decision immediately. Background can follow when it helps the reader act.

Answer the decision before adding background

State who the article is for, what situation it covers, what the reader should do, and when the route does not apply. Use short steps for actions and a table when comparing choices or conditions.

Do not put an important exception at the bottom if it changes whether the process is safe. The ServiceNow solutions page is the relevant internal route when knowledge must support several employee and enterprise workflows.

Write steps that match the service path

The article should use the same names as the portal, catalogue item, form, or support route. If a step sends the reader to another workflow, explain what information they will need and what they should expect after submission.

A workaround should state its boundary and review date where relevant. Do not present a temporary action as a permanent policy.

Give every article an owner and review trigger

An article needs a content owner, subject reviewer, review condition, and retirement path. A review may be triggered by a process change, platform change, policy update, repeated failed searches, or an incident that exposes unclear guidance.

The knowledge base management service is the relevant internal commercial route for ownership, structure, review, and findability work.

Connect knowledge to search and escalation

Place useful articles where the question arises. Search should recognise relevant terms and provide a next action when no article is sufficient. An article should not leave the reader at a dead end when the situation requires a request, incident, or human decision.

Review failed searches and repeated escalations together. They can reveal missing synonyms, unclear titles, incomplete content, or a workflow that knowledge cannot solve.

Common questions

Questions teams ask about employee knowledge

How long should a knowledge article be?

Long enough to answer the question and explain the required action, but no longer than the reader needs. Use structure, short paragraphs, and clear headings rather than padding a target word count.

When should an article be retired?

Retire it when the service, process, policy, owner, or route no longer exists, or when a tested replacement provides the current guidance. Preserve the reason so people do not recreate the same outdated answer.

The research-grounded boundary

Employees use an article when it answers a question quickly and says what to do next. An article becomes unreliable when its steps stop matching the current form or route, so each one needs a named owner, a clear boundary, and a point where someone checks the result. Review it against the request it is meant to prevent, not only against its own wording.

Write each article around one decision a person has to make

An employee who searches the knowledge base is rarely looking for an article. They want permission to do something, the next step in a process they are already stuck in, or confirmation that a request will be handled. The knowledge manager’s first decision is therefore which decisions the knowledge base should resolve, and which should be sent straight into a request or a case. An article that tries to answer three decisions at once is hard to find, harder to keep current, and tends to be skipped by people who only needed one of those answers.

Choose the title from the words employees actually use

Titles are often a major part of what platform search matches on, so they can carry more weight than the body. Collect phrases from search logs, from the descriptions people type into a request, and from the questions agents answer most often. Then write the title in the employee’s words, with the internal service name placed second. An article called “Access to the finance reporting tool” will be found by people who know the tool by name. An article called “Finance reporting access procedure” will be found only by people who already know the procedure.

Where findability usually breaks

SymptomLikely causeUsual fix
The article appears only when the exact title is typedTitle and keywords use internal terms onlyAdd employee phrasing to the keywords and to the first paragraph
Two articles answer the same questionDuplicates created by different teamsMerge into one, redirect the other, and name a single owner
Searches return many results and none is usedArticles cover several decisions at onceSplit by decision, then link the pieces together
Employees read the article and still raise a requestSteps stop short of what happens nextState the route, the expected wait and the fallback
Searches with no result keep recurringNo article exists, or the content sits in a form search does not indexWrite the missing article or move the content into readable text

The table works as a diagnostic. Most findability problems are not about the search tool. They come from authors writing for the procedure rather than for the moment a person reaches for help, and from the absence of one owner who can see every article touching the same topic.

A structure that lets people act within a minute

  1. State who the article is for and the situation it covers in the first sentence.
  2. Give the decision or the action in the second paragraph, before any background.
  3. List the steps in the order the employee performs them, naming the place where each step happens.
  4. State when the article does not apply and where the reader should go instead.
  5. End with the escalation route, including who answers and what information they will need from the reader.

Connecting articles to the workflow that needs them

An article is most useful where the work starts. Link it from the catalog item it supports, from the help text on the request form, and from the virtual agent topic that handles the same question. Each link should carry the employee to the article at the point of need. A knowledge base that lives only in a separate library will be read by the knowledge team and ignored by everyone else. The knowledge article concepts behind that design are worth agreeing with the team first.

Signs that findability is improving

Track the searches that return nothing, the articles that are opened and then followed by a request on the same topic, and the feedback that asks whether the article answered the question. Read a sample of these each month, using the portal search analytics approach where the platform reports it. The aim is not a higher view count. It is fewer repeat requests for the same answer and fewer searches that end without an article being opened.

When an article is the wrong tool

If the answer depends on a field the employee must complete, a form with clear guidance is usually better than a long article. If the answer changes often, such as a rota, a live status or a price set by a third party, a link to the live source beats a copy that goes stale. Use articles for judgment, sequence and context, and let forms and status pages carry the rest. Plan the life of each article using the article lifecycle guidance.

Questions from knowledge managers

Should the title match the employee’s exact wording?

Not exactly. Use that wording as the strongest signal, then tidy it into plain English. Keep the internal service name in the body so that people arriving from a request or a support note can still recognize the article.

Can an article be offered in another language for a distributed workforce?

Yes, but each language version needs its own owner and its own search terms. A translated article that is never refreshed drifts from its source and sends readers the wrong steps without anyone noticing.

Who should approve an article before it is published?

The owner of the process it describes, not only the knowledge team. The knowledge team can check clarity and structure, but only the process owner can confirm that the steps match what really happens.

What should an employee do when they find a step that is wrong?

Each article should offer a feedback route on the page itself. Feedback that a step is wrong should reach the owner quickly, and the owner should either correct the article or mark it as under review so readers know. A routine knowledge quality review makes that step ordinary rather than exceptional.

Next step for knowledge content

If employees keep raising requests on topics that already have an article, the fastest diagnosis is usually a review of search terms and article ownership.

Contact OBLYTECH about your knowledge content.

A practical next step

Need a clearer ServiceNow operating model?

OBLYTECH can discuss the questions raised by this guide and the next review step. See the ServiceNow consulting services page for the commercial route.

Useful starting pointBring the current question, scope, ownership concerns, and evidence needs into the first review conversation.

Review ServiceNow consulting

ServiceNow guides on this topic

Guides from the Oblytech ServiceNow library that explain the practice behind this page.

More from the blog

Related reading