Knowledge Repository of Insights

We manage various types of content within knowledge management systems. When we envision a knowledge management system, examples of insights that were discovered in the organization typically come to mind - insights that only one expert, experienced, and special, remembers.

These pieces of knowledge constitute the organizational memory and represent the pinnacle of knowledge that we seek to manage. Nevertheless, when we come to manage knowledge within an organization, we often discover that the knowledge we manage is simpler and more basic. This is not surprising, since there is no point in managing insights (the "penthouse" of knowledge) if we are not managing the basic content (the "foundation floors").

However, there are cases where insights themselves require management. An example of this, which recurs in every organization, is the knowledge gained and/or collected during investigation operations. Regardless of when the knowledge was learned, the central question is how to organize it so that it can be effectively reused.

Here are several important principles for establishing a knowledge repository of insights:

1. Each knowledge item will be cataloged according to several organizational characteristics defined in advance. This will make it easier for the searcher to locate relevant knowledge items. This will make it easier for the organization to perform a push process of recommendations for knowledge that could be relevant in similar future cases.

2. Each knowledge item will be tagged with its author and, where available, an accompanying document. An insights repository typically contains highlights, the bottom line. The person behind the knowledge is important, both in terms of credit and in filling in the missing knowledge that was not presented in the insight.

3. Each "candidate" item for the repository will be examined against defined criteria (filtering process):

   1. The item is not trivial (for example, it is recommended to involve customers in the process) but has real added value.

   2. The item is agreed upon and does not give rise to disagreements.

   3. "Time significance" - it is preferable to provide an insight that teaches practical experience with time concepts.

4. Work methods will be defined for integrating repository items into work processes where knowledge is required (launching a new project, malfunctions, etc.). Work methods will be defined for collecting new content and examining the relevance of existing content. Each new item will be attached with a date for examining its validity and relevance.

A knowledge repository of insights is usually the "cream" of knowledge management. Build it with sensitivity and wisdom!

---

Want to know more about lesson learned?

Here are some articles you might find interesting:

• A New Perspective on Insights

• Lessons Learned - Creating the Right Atmosphere

• Unleashing Creativity: Bridging Frameworks for Effective Lesson Learning