Difference between revisions of "Knowledge mapping"
(→Common pitfalls) |
(→Related articles) |
||
| Line 42: | Line 42: | ||
[[Knowledge map]] | [[Knowledge map]] | ||
| + | |||
[[Concept mapping]] | [[Concept mapping]] | ||
| + | |||
[[Process mapping]] | [[Process mapping]] | ||
[[Category:Knowledge mapping]] | [[Category:Knowledge mapping]] | ||
Revision as of 10:26, 7 March 2016
Contents
Definition
The process of creating a knowledge map
Purpose and benefit
Knowledge mapping is a mapping process which creates a map of a selected knowledge domain, i.e. knowledge map. Knowledge mapping can be used as a tool to facilitate knowledge processes, e.g. learning, or business processes, e.g. evaluating the risk of knowledge loss. Knowledge mapping may be performed by just one person of his personal knowledge or on the level of the whole organisation or anything in between, and it can concentrate in the current situation or have a future oriented view.
Description
Knowledge mapping is a mapping process which can be used for managing knowledge or knowledge assets of an organization. The process of knowledge mapping involves defining the knowledge domain to be mapped and the relationships within the domain and creating a symbolic representation of this.
Knowledge mapping may concentrate on the current situation or have a future oriented view. It may concern itself with knowledge of one individual, knowledge of a team or knowledge of a whole organisation. Knowledge mapping can be used as a tool in several situations, e.g. determining knowledge loss risks or knowledge gaps or when facilitating knowledge processes.
Variations
The output of knowledge mapping is a knowledge map. The exact form of the output and the suitable mapping process depend on the objective of creating the knowledge map. The used process can be concept mapping or process mapping among others.
Reference [1] provides an example of a knowledge mapping process on an organizational level.
Success factors
- The availability of a suitable modelling software package is essential.
- Modelled knowledge should be validated by other experts and peers if possible.
- Ensure that the knowledge maps are available (read-only) for others to view. A portal or intranet is usually needed for this.
- Experience in the use of knowledge mapping software is essential – although most packages are very easy to use.
Common pitfalls
- Trying to model too broad knowledge domain. This may lead to too complex knowledge maps which are difficult to understand.
- Modelling readily known and understood information.
- Providing only a superficial view of the selected knowledge domain. There are knowledge domains which can not be captured on a single page of knowledge map!
- Creating a knowledge map without sufficient review. In this case the map stays incomplete and difficult to understand.
- Not sharing or transferring the knowledge. If a knowledge is modelled and never used then the whole process has little value.
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.
