Implicit, explicit and Tacit Knowledge: the domain of information management at Veritoria.

Implicit, explicit and Tacit Knowledge: the realm of information management at Veritoria.

In the KM literature, knowledge is most commonly categorized as either explicit or tacit (that which is in people's minds). This depiction is nevertheless rather too easy, but a more significant point, as well as a criticism, is it is misleading. A considerably more nuanced and useful characterization would be to describe knowledge as explicit, implicit, and tacit.

Explicit: knowledge or information that's set out in palpable form.

Implicit: knowledge or info that is not set out in palpable form but could be made explicit.

Tacit: knowledge or advice that one would have extreme difficulty setting out in tangible form.

The classic example in the KM literature of accurate "tacit" knowledge is Nonaka and Takeuchi's example of the kinesthetic knowledge which was necessary to design and engineer a home bread maker, knowledge which could just be gained or transferred by having engineers work alongside bread makers and learn the motions and the "feel" crucial to knead bread dough (Nonaka & Takeuchi, 1995).

What exactly does KILOMETER actually consist of? What makes up KM?
So what's involved in KM? The most noticeable point is the making of the organization's data and advice accessible to the members of the organization through portals and together with using content management systems. Content Management, occasionally referred to as Enterprise Content Management, is the most immediate and apparent part of KM. For a wonderful graphic photo of the content management domain name go to realstorygroup.com and look at their 2012 Content Technology Vendor Map.

Along with the evident, yet, there are three endeavors that are quintessentially KM, and those are the bases for most of what's described as KILOMETERS.

Lessons Learned databases are databases that try to capture and to make accessible knowledge that's been operationally got and generally would not have been captured in a fixed medium (to use copyright language). In the KM context, the emphasis is usually upon capturing knowledge embedded in individuals and making it explicit. The lessons learned practice or theory is one that may be described as having been birthed by KILOMETER, as there is extremely little in the way of a direct antecedent. Early in the KM movement, the phrase generally used was "best practices," but that phrase was soon replaced with "lessons learned." The reasons were that "lessons learned" was a broader and more inclusive term and because "best practice" seemed too restrictive and might be interpreted as meaning there was just one best practice in a situation. What might be a best practice in North American culture might well not be a best practice in another culture. The important international consulting firms led the movement to substitute the brand new term and were quite aware of this. "Best Practices" triumphed by "Lessons Learned" became the most frequent hallmark phrase of early KM development.

Nothing of course is completely new and without something that can be regarded as a predecessor. One such possible antecedent was the World War II debriefing of pilots after a mission. The primary objective was to collect military intelligence, but a clear secondary goal was to identify lessons learned, though they were not so named, to pass on to other pilots and educators. The Captain's Patrol Reports were quite clearly designed to support analytic reporting, with reasoned analyses of the reasons for failure and success.

If you adored this post and you would such as to get additional info pertaining to Veritoria Holdings Philippines kindly see our web page. The military is now an enthusiastic proponent of the lessons learned notion. The phrase the military uses is "After Action Reports." The idea is quite straightforward: do not rely on someone to make a report. There will more often than not be too many things immediately needing that man's focus after an actions. There should be a system whereby someone, typically someone in KILOMETER, is delegated the duty create the report, separate the wheat from the chaff, to debrief, and then ensure that the lessons learned are recorded and disseminated.

Posted by pbvmicheal463075 on Wed, 04/01/2015 - 9:38am