Difference between revisions of "Knowledge map"
(→Summary) |
|||
| Line 14: | Line 14: | ||
== Summary== | == Summary== | ||
| − | Knowledge map was proposed by B. C. Brookes in 1980's. It is a useful [[Tools|tool]] in the field of [[Knowledge management|knowledge management]] | + | Knowledge map was proposed by B. C. Brookes in 1980's. It is a useful [[Tools|tool]] in the field of [[Knowledge management|knowledge management]] which facilitates [[Codification|tacit knowledge mining]] and the understanding of existing knowledge assets. Users will be able to navigate in a knowledge base more easily with the help of a detailed knowledge map. There are several types of knowledge map, one of which also can be used as a tool for personal knowledge management. |
== Description== | == Description== | ||
| − | Explicit knowledge implies declared knowledge (i.e. knowledge that is conscious to the | + | Knowledge map is the output of knowledge mapping which is a process to determine where knowledge assets are in an organization and how knowledge flows operate within the organization. |
| − | knowledge bearer). Explicit knowledge is why it is not a problem for the employee to tell | + | |
| − | about rules and obviously learned facts. Very often this knowledge is already written down in | + | Explicit knowledge implies declared knowledge (i.e. knowledge that is conscious to the knowledge bearer). Explicit knowledge is why it is not a problem for the employee to tell about rules and obviously learned facts. Very often this knowledge is already written down in books. The most important aspects of knowledge can be illustrated by using a knowledge map. Such a tool is helpful in the transfer of knowledge from departing employees to their successors (see Fig. 4). |
| − | books. The most important aspects of knowledge can be illustrated by using a knowledge | + | |
| − | map. Such a tool is helpful in the transfer of knowledge from departing employees to their | + | |
| − | successors (see Fig. 4). | + | |
[[File:Knowledgemap.PNG|thumb|right|500px|Fig. 4. Example of a simplified knowledge map]] | [[File:Knowledgemap.PNG|thumb|right|500px|Fig. 4. Example of a simplified knowledge map]] | ||
| Line 28: | Line 25: | ||
== References == | == References == | ||
| − | [1] | + | [1] [[Development of Knowledge Portals for Nuclear Power Plants - document as published|Development of Knowledge Portals for Nuclear Power Plants]] |
| + | |||
==Related articles== | ==Related articles== | ||
[[Knowledge mapping]] | [[Knowledge mapping]] | ||
Revision as of 02:34, 25 October 2013
,
Definition
Knowledge map is an overview of knowledge assets in an organization. It shows the distribution and correlation of knowledge as well as provides navigation for potential users so that they can find desired knowledge properly.
Summary
Knowledge map was proposed by B. C. Brookes in 1980's. It is a useful tool in the field of knowledge management which facilitates tacit knowledge mining and the understanding of existing knowledge assets. Users will be able to navigate in a knowledge base more easily with the help of a detailed knowledge map. There are several types of knowledge map, one of which also can be used as a tool for personal knowledge management.
Description
Knowledge map is the output of knowledge mapping which is a process to determine where knowledge assets are in an organization and how knowledge flows operate within the organization.
Explicit knowledge implies declared knowledge (i.e. knowledge that is conscious to the knowledge bearer). Explicit knowledge is why it is not a problem for the employee to tell about rules and obviously learned facts. Very often this knowledge is already written down in books. The most important aspects of knowledge can be illustrated by using a knowledge map. Such a tool is helpful in the transfer of knowledge from departing employees to their successors (see Fig. 4).
References
[1] Development of Knowledge Portals for Nuclear Power Plants
