Difference between revisions of "Explicit knowledge"
(→Related articles) |
|||
| Line 44: | Line 44: | ||
[[Tacit knowledge]] | [[Tacit knowledge]] | ||
| + | |||
| + | [[Documented knowledge lifecycle]] | ||
[[Category:Knowledge type]] | [[Category:Knowledge type]] | ||
Revision as of 10:43, 10 December 2015
Contents
Definition
Explicit knowledge is Knowledge that has been articulated or has already been codified in some form
Summary
Explicit knowledge can be documented in useful forms such as operating manuals, files, reports, drawings, etc. Explicit knowledge can also be non-codified, but articulated and codifiable. There is much discussion about the distinction between information and explicit knowledge, but for practical purposes, here they will be used interchangeably.
Description
Explicit knowledge can be readily transferred to others.
The most common forms of codified explicit knowledge are documents, drawings, calculations, icons, designs, multimedia, databases, taxonomies, knowledge maps documented procedures and manuals.
Non-codified explicit knowledge (i.e., knowledge that is conscious to the knowledge bearer) includes for example existing non-documented procedures in an organization.
There is much discussion about the distinction between information and explicit knowledge, but for practical purposes of managing these two (similarity of tools and methods), they will be used interchangeably here.
The object can be information or explicit knowledge, depending on the recipient. The next section illustrates this thin boundary.
Illustrative examples
- Expert (rule-based) systems contain information that allow an independent person to act upon it - hence it is considered explicit knowledge
- Without an expert, NPP documentation will not allow an independent person to build and run an NPP - hence it is information
- Power failure in an NPP is information for the general public (meaning: not able to operate), but knowledge for the operators (meaning:danger)
