Home > KCS v6 Practices Guide > Section 2 The KCS Practices > The Solve Loop > Practice 3: Reuse > Technique 3.1: Search Early Search Often

Technique 3.1: Search Early Search Often

Table of contents
No headers

image010.gifSearching the knowledge base must become an integral part of all knowledge worker processes—search early, search often. The best practice for information capture is to search the knowledge base in real-time. The words and phrases we use to search are potential content to improve an existing article or to create a new article, if one doesn't already exist. Once we have captured a description of the issue and some information about the environment, we have enough context about the issue to search. By listening and searching early based on the requestor's description of the issue, we ensure we understand the issue as the requestor sees it and we minimize the risk of investing time in problem analysis and research on an issue that has already been solved.


Searching often is important because as we are working on the issue and learning more about the situation, we need to search using the new information to see what we collectively know about this or similar issues. 


Searching is not a one-time event but rather something that is done throughout the request-resolution process. The advantages of searching often include the following.

  • As new information is collected, a search should be done to see if a knowledge article about this issue or a similar issue exists. 

  • The articles found in a search, even if they don't directly address the issue at hand, can provide helpful perspectives from similar issues. This can provide ideas on how others have solved similar issues and help us identify clarifying questions.

  • It is particularly important to search the knowledge base one more time, before we save a new article, to be sure one doesn't already exist. 

Viewing 1 of 1 comments: view all
Comment added by Russ Brooks: Search every time you get a new clue. Searching throughout the process greatly reduces the chances you will end up creating a duplicate article. I don't think you should just search using the customer's context - you should definitely search using the customer context - but analysts in addition should search using their own context, and if an article that solves the problem or answers the customer's question is found - then make sure you add the customer's context to the article if not already there. If you are searching using customer context, and the system is capturing search phrases in the list of candidate article content (for new or modified articles) - then you are achieving 2 things with one motion.
Posted 23:56, 14 Apr 2016
Viewing 1 of 1 comments: view all
You must to post a comment.
Last modified


This page has no custom tags.


This page has no classifications.