Difference between revisions of "Knowledge mapping"
Line 16: | Line 16: | ||
The most important aspects of knowledge can be illustrated by using a [[Knowledge map|knowledge map]]. | The most important aspects of knowledge can be illustrated by using a [[Knowledge map|knowledge map]]. | ||
+ | |||
+ | ===How to build a knowledge map=== | ||
+ | #Establish a work team including knowledge management specialists, technical experts and typical user representitives if necessary. | ||
+ | #Identify potential users such as employees, partners or customers and capture requirements from them. | ||
+ | #Determine the purpose of building a knowledge map, clarify its applicable scope, structure, type, etc. | ||
+ | #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.) | ||
+ | #Make connections among knowledge. Use appropriate tools to describe or present the knowledge map. | ||
+ | #Evaluate the result of knowledge map, keep updating and improving. | ||
===Examples=== | ===Examples=== | ||
Reference [1] | Reference [1] |
Revision as of 16:03, 31 May 2014
Template:Consolidation stage,Contents
Definition
Knowledge mapping is The process of creating a knowledge map
Summary
Description
a process to determine where knowledge assets are in an organization, and how knowledge flows operate within the organization. Evaluating relationships between holders of knowledge will then illustrate the sources, flows, limitations, and losses of knowledge that can be expected to occur. see also Concept map.
Knowledge mapping involves such activities as data gathering, survey, exploring, conversation, gap analysis and synthesis. It's fundamental work and also an infrastructure of knowledge management which should be done in an early phase and needs continuous maintenance.
The most important aspects of knowledge can be illustrated by using a knowledge map.
How to build a knowledge map
- Establish a work team including knowledge management specialists, technical experts and typical user representitives if necessary.
- Identify potential users such as employees, partners or customers and capture requirements from them.
- Determine the purpose of building a knowledge map, clarify its applicable scope, structure, type, etc.
- 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.)
- Make connections among knowledge. Use appropriate tools to describe or present the knowledge map.
- Evaluate the result of knowledge map, keep updating and improving.
Examples
Reference [1]
References
[1] Day, J., How Knowledge Mapping is Being Used to Integrate Plans for Safe and Reliable Operations, In International Conference on Human Resource Development for Nuclear Power Programmes: Building and Sustaining Capacity Strategies for Education and Training, Networking and Knowledge Management, IAEA CN‐215, 2014, pp. 167-169.