Difference between revisions of "Knowledge map"

From NKM WIKIDOC
Jump to: navigation, search
(Related articles)
(Definition)
 
(122 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Jiajie}}
 +
<!--
 
{{Tellervo}}
 
{{Tellervo}}
  
{{Jiajie}}
+
{{Tidy3}},
 
+
{{Comment}}
+
  
 
{{Consolidation stage}},
 
{{Consolidation stage}},
 
+
-->
  
 
==Definition==
 
==Definition==
{{PAGENAME}} is {{ {{PAGENAME}} }}
+
{{ {{PAGENAME}} }}
  
 
== Summary==
 
== Summary==
Knowledge map shows the distribution and correlation of knowledge as well as provides navigation for potential users so that they can find desired knowledge properly. Knowledge map was proposed by B. C. Brookes in 1980's. It is a useful [[Tool|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.
+
A knowledge map is a tool which presents a selected [[Knowledge|knowledge]] domain and the connections within it in a graphical form. Knowledge maps can take several forms, e.g. [[Concept map|concept map]] or [[Process map|process map]]. They can also be created for different purposes including a map of the knowledge of one person or a map of [[Knowledge asset|knowledge assets]] of a whole organisation.
  
 
== Description==
 
== Description==
 
===Overview===
 
===Overview===
 +
Knowledge map is a symbolic representation of a selected knowledge domain and the output of [[Knowledge mapping|knowledge mapping]]. The form of knowledge maps may vary including [[Concept map|concept maps]] and [[Process map|process maps]]. The components of knowledge maps usually include the so-called background which is the context where the map is produced, the elements of the maps and the relationships between the elements. The last of which is the essential feature of a knowledge map compared to other ways of documenting knowledge, e.g. lists. An example of a knowledge map is provided in Fig 1.
 
[[File:Example of KMM.jpeg|thumb|right|500px|Fig. 1. Example of a knowledge map]]
 
[[File:Example of KMM.jpeg|thumb|right|500px|Fig. 1. Example of a knowledge map]]
Knowledge map is the output of [[Knowledge mapping|knowledge mapping]]. Knowledge map usually does not contain concrete knowledge, but it is knowledge itself. (See Fig. 1)
 
 
===The functionalities of knowledge map===
 
Knowledge map has the following functions:
 
#'''Indicate the location of knowledge assets in an organization:''' The basic function of knowledge map is to tell users where they can get knowledge and to provide navigation for them. Similar to information explosion, sometimes there is excessive knowledge in an organization, which is over the limit for a person to handle. In spite of search engines, knowledge map can be a good manner to retrieve knowledge in a logical way.
 
#'''Help to discover tacit knowledge in an organization:''' With the overview picture of knowledge assets in an organization, it is more likely to discover tacit knowledge in certain fields. Behind the corelation of knowledge, there might be some experts and knowledge owners from whom tacit knowledge can be captured.
 
#'''Improve the self-learning ability in an organization and guide newcomers:''' Users(or employees) can learn new things by navigating in a knowledge map. Moreover, knowledge map is greatly helpful to newcomers and let them get into their roles quickly.
 
#'''As a summary list of knowledge assets in an organization:''' Knowledge map can be regard as a summary list of knowledge assets in an organization, which helps to evaluate the current status and maturity of knowledge management.
 
  
 
===Types of knowledge maps===
 
===Types of knowledge maps===
There are at least three types of knowledge maps:
+
The literature review of Eppler [1] provides several possible categorisations for knowledge maps:
[[File:Knowledgemap.PNG|thumb|right|500px|Fig. 2. Example of concept-oriented knowledge map]]
+
* [[Knowledge process]]: Knowledge maps can be used as tools for [[Knowledge process|knowledge processes]], e.g. [[Identification|identification]], [[Learning|learning]], [[Sharing|sharing]] and storage.
#'''Concept-oriented knowledge map,''' or [[Concept map]] also can be considered as "[[Taxonomy|taxonomy]]". This type of knowledge map is often used in knowledge base or [[Content management|content management]] systems. (See Fig. 2)
+
* Knowledge domain: Knowledge map always concerns itself with a knowledge domain, e.g. strategy, maintenance, waste management.
#'''Process-oriented knowledge map,''' or [[Process map]] uses business processes in an organization to make connections among related knowledge. Users can follow the processes and use the handy knowledge by means of a process-oriented knowledge map.
+
* Content of the map: The elements of maps may be for example ideas, people (network map), documents, data, learning objectives
#'''Social-oriented knowledge map,''' or [[Personal network map]] or shows the social relationship of users(or employees) as well as their expertise and competencies in a knowledge map.
+
* Users: Some knowledge maps might be just for personal use and some for use of a whole organisation.
 +
* Form of the map: The form of a knowledge map may e.g. a table, [[Concept map|concept map]], [[Process map|process map]], hierarchical list.
 +
* The way of creating the map: Maps may be produced automatically, by a group work, edited iteratively etc.
  
===How to build a knowledge map===
+
===Benefits of knowledge maps===
#Establish a work team including knowledge management specialists, technical experts and typical user representitives if necessary.
+
For [[Nuclear organization|nuclear organizations]], there are several benefits of using knowledge maps, including
#Identify potential users such as employees, partners or customers and capture requirements from them.
+
* Knowledge map can be used as a summary of the organozation's [[Knowledge asset|knowledge assets]]. It provides better overview and a more efficient and memorable representation and communication of [[Knowledge asset|knowledge assets]].
#Determine the purpose of building a knowledge map, clarify its applicable scope, structure, type, etc.
+
* As knowledge maps include structure in form of links between the elements of the map, they help in understanding the structure of [[Knowledge asset|knowledge assets]].
#Collect and analyze knowledge in the organization field by field. Classify and categorize the knowledge in terms of users' requirements. (Interviews and surveys might be needed.)
+
* Knowledge maps may indicate the location of the knowledge assets in an organization, provide faster access, and improve finding the relevant knowledge. Often the amount of knowledge in an organization is over the limit for a person to handle. In addition to search engines, knowledge maps can be a good way of [[Retrieval|retrieving knowledge]] in a logical way.  
#Make connections among knowledge. Use appropriate tools to describe or present the knowledge map.
+
* As the representation of knowledge in knowledge maps can be made logical, they may help in judging the quality and maturity of knowledge assets and in understanding how to develop knowledge assets.
#Evaluate the result of knowledge map, keep updating and improving.
+
* Knowledge maps can be used for representing [[Implicit knowledge|implicit knowledge]] and locating [[Tacit knowledge|tacit knowledge]]. With the overview picture of knowledge assets in an organization, it is more likely to discover tacit knowledge.
 +
* Knowledge maps improve [[Learning|learning]] both of the organization and individuals. Organization learns via increased understanding of its knowledge assets and better evaluation of them. Individuals learn both via using the maps and via [[Knowledge mapping|creating them]], and the maps may prove to be useful e.g. for the newcomers in the job induction process.
  
 +
===Creating a knowledge map===
 +
Creating a knowledge map is described in [[Knowledge mapping|this article]]
  
 
== References ==
 
== References ==
[1] [[Development of Knowledge Portals for Nuclear Power Plants - document as published|Development of Knowledge Portals for Nuclear Power Plants]]
+
[1] Eppler M., A Process-Based Classification of Knowledge Maps and Application Examples, Knowledge and Process Management, Volume 15 Number 1 pp 59–71 (2008), http://lpis.csd.auth.gr/mtpx/km/material/knowledge%20maps.pdf
  
==Related articles==
+
===Other potentially useful literature===
[[Map (disambiguation)]]¨
+
[2] Ermine J.L., Boughzala I and Tounkara T., Critical Knowledge Map as a Decision Tool for Knowledge 
 +
Transfer Actions, "Electronic Journal of Knowledge Management 4, 2 (2006) 129-140, http://hal.archives-ouvertes.fr/docs/00/47/03/87/PDF/10.1.1.85.873_1_.pdf
  
[[Map]]
+
[3] Balaid, Zibarzani, Rozan, A Comprehensive Review of Knowledge Mapping Techniques, JOURNAL OF INFORMATION SYSTEMS RESEARCH AND INNOVATION, http://seminar.utmspace.edu.my/jisri/download/F1_FinalPublished/Pub9_Comprehensive_KnowledgeMapping_Techniques.pdf
  
 +
==Related articles==
 
[[Knowledge mapping]]
 
[[Knowledge mapping]]
  
Line 58: Line 58:
 
[[Process map]]   
 
[[Process map]]   
  
[[Personal network map]] 
+
[[Category:Knowledge map]]
+
[[Causal map]] 
+
 
+
[[History map]] 
+
 
+
 
+
[[category:Tools]]
+
[[category:Competency]]
+
[[category:CSA]]
+

Latest revision as of 09:24, 21 December 2015

Jiajie.png

Definition

A map of a selected knowledge domain.

Summary

A knowledge map is a tool which presents a selected knowledge domain and the connections within it in a graphical form. Knowledge maps can take several forms, e.g. concept map or process map. They can also be created for different purposes including a map of the knowledge of one person or a map of knowledge assets of a whole organisation.

Description

Overview

Knowledge map is a symbolic representation of a selected knowledge domain and the output of knowledge mapping. The form of knowledge maps may vary including concept maps and process maps. The components of knowledge maps usually include the so-called background which is the context where the map is produced, the elements of the maps and the relationships between the elements. The last of which is the essential feature of a knowledge map compared to other ways of documenting knowledge, e.g. lists. An example of a knowledge map is provided in Fig 1.

Fig. 1. Example of a knowledge map

Types of knowledge maps

The literature review of Eppler [1] provides several possible categorisations for knowledge maps:

  • Knowledge process: Knowledge maps can be used as tools for knowledge processes, e.g. identification, learning, sharing and storage.
  • Knowledge domain: Knowledge map always concerns itself with a knowledge domain, e.g. strategy, maintenance, waste management.
  • Content of the map: The elements of maps may be for example ideas, people (network map), documents, data, learning objectives
  • Users: Some knowledge maps might be just for personal use and some for use of a whole organisation.
  • Form of the map: The form of a knowledge map may e.g. a table, concept map, process map, hierarchical list.
  • The way of creating the map: Maps may be produced automatically, by a group work, edited iteratively etc.

Benefits of knowledge maps

For nuclear organizations, there are several benefits of using knowledge maps, including

  • Knowledge map can be used as a summary of the organozation's knowledge assets. It provides better overview and a more efficient and memorable representation and communication of knowledge assets.
  • As knowledge maps include structure in form of links between the elements of the map, they help in understanding the structure of knowledge assets.
  • Knowledge maps may indicate the location of the knowledge assets in an organization, provide faster access, and improve finding the relevant knowledge. Often the amount of knowledge in an organization is over the limit for a person to handle. In addition to search engines, knowledge maps can be a good way of retrieving knowledge in a logical way.
  • As the representation of knowledge in knowledge maps can be made logical, they may help in judging the quality and maturity of knowledge assets and in understanding how to develop knowledge assets.
  • Knowledge maps can be used for representing implicit knowledge and locating tacit knowledge. With the overview picture of knowledge assets in an organization, it is more likely to discover tacit knowledge.
  • Knowledge maps improve learning both of the organization and individuals. Organization learns via increased understanding of its knowledge assets and better evaluation of them. Individuals learn both via using the maps and via creating them, and the maps may prove to be useful e.g. for the newcomers in the job induction process.

Creating a knowledge map

Creating a knowledge map is described in this article

References

[1] Eppler M., A Process-Based Classification of Knowledge Maps and Application Examples, Knowledge and Process Management, Volume 15 Number 1 pp 59–71 (2008), http://lpis.csd.auth.gr/mtpx/km/material/knowledge%20maps.pdf

Other potentially useful literature

[2] Ermine J.L., Boughzala I and Tounkara T., Critical Knowledge Map as a Decision Tool for Knowledge Transfer Actions, "Electronic Journal of Knowledge Management 4, 2 (2006) 129-140, http://hal.archives-ouvertes.fr/docs/00/47/03/87/PDF/10.1.1.85.873_1_.pdf

[3] Balaid, Zibarzani, Rozan, A Comprehensive Review of Knowledge Mapping Techniques, JOURNAL OF INFORMATION SYSTEMS RESEARCH AND INNOVATION, http://seminar.utmspace.edu.my/jisri/download/F1_FinalPublished/Pub9_Comprehensive_KnowledgeMapping_Techniques.pdf

Related articles

Knowledge mapping

Concept map

Competency map

Process map