<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
         xmlns:thr="http://purl.org/syndication/thread/1.0" 
         xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2006://1.7967-</id> 
  <updated>2007-12-03T11:46:12Z</updated>
  <title>Comments for KM definitions from my perspective</title> 
  <subtitle>Jack Vinson writes about knowledge management, personal effectiveness, theory of constraints and more.  As of December 2007 Jack will likely start writing about product management too.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.01</generator>

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2006://1.7967" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html"/>


    <id>tag:blog.jackvinson.com,2006://1.7967.8714</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html#comment-8714" /> 
    <title>Comment from Yigal Chamish on 2006-08-30</title>
    <author>
        <name>Yigal Chamish</name> 
        <uri>http://yigalc.wordpress.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://yigalc.wordpress.com">     
      <![CDATA[ <p>Hello jack, Thank you for mentioning my comment to your post. Indeed, defining KM is a tough issue. Yet, I am trying to figure it out as described here: <a href="http://yigalc.wordpress.com/2006/07/15/what-is-km-knowledge-management/.">http://yigalc.wordpress.com/2006/07/15/what-is-km-knowledge-management/.</a></p>

<p>I will be happy to discuss it,</p>

<p>Yigal</p> ]]>
    </content>
    <published>2006-08-30T07:54:57Z</published>
    <updated>2006-08-30T07:54:57Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2006://1.7967" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html"/>


    <id>tag:blog.jackvinson.com,2006://1.7967.13126</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html#comment-13126" /> 
    <title>Comment from Duane McCollum on 2006-10-02</title>
    <author>
        <name>Duane McCollum</name> 
        <uri>http://www.theinformationauditor.com/blog/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.theinformationauditor.com/blog/">     
      <![CDATA[ <p>I have experienced that settling on a satisfactory definition "Knowledge Management" is quite a challenge. Why bother? I guess I feel i have to, that i have a professional responsibility to try to help my employer (and the government agencies we do work for) make sense out of such ideas as Knowledge Management.</p>

<p>Most people I work with put KM directly into an IT context. Others try to focus on <i>people</i> or <i>knowledge</i> but that IT thing still lingers in the background (like a bad habit). So, i have seen at least two distinct approaches, one that is mostly technologically driven, the other less so, to a degree, but still very much in an IT context. </p>

<p>Irrespective of what approach we might take, we often seem to make KM a part of a kind of an "Information Management Holy Trinity" for the information-age organization: there's Data (the father, or Source), then Information (the son, or that which is <i>consubstantial</i> to the Source and, simultaneously, a derivative of it), and finally there's Knowledge (the Spirit of Wisdom and its preservation and transmission,  guiding all human-information endeavors) which somehow transcends data and information --and yet we insist it can be managed. </p>

<p>In my organization, if the topic of KM comes up, someone eventually draws a pyramid with data-managment on the bottom, information management in the middle, and Knowledge Management up on the top. Intuitively, I guess all this makes sense --certainly makes a neat picture for management. But I've rejected this vision and am left with both trying to explain why it's inadequate and create an alternative definition. So, I've been searching for a different way of looking at KM, one that is independent of any discussion of information technology and instead on how does this thing we like to call "knowledge" get created, used, moved around, preserved, discarded, and so on in an organization (or our society itself). </p>

<p>In order to do this, i've been experimenting with creating a new language to talk about it. So far, the best i've done is come up with a very rough-hewn idea i am calling "Meaning Management". My idea here is that what we really seem to be doing with all this data-information-knowledge is <i>create meaning</i>. This is what we really use to guide our decisions. If an information resource (here i mean data, information, knowledge, whatever; its format is anything from a note on a "post-it", or the WikiPedia, or a conversation with a co-worker) is to be useful in some way it has meaning, and that meaning is created by human relationships (perhaps influenced in some way by information technology).  My thinking is that if information is ever made useful, then it is so because of the relationships made in context between people who created that information. <i>Meaning</i> is the key thing we should be thinking about managing --not just data, information, or knowledge. Such Meaning is not possible with relationships and such relationships are not possible without organizational structures of some sort (families, businesses, academic fields, etc). </p>

<p>My idea is really half-baked. But it makes a certain kind of sense to me: i want to get far enough on the outside of this data-information-knowledge business to create a way of describing what's really going on. I think by taking this look at it we might be able to see that things like culture, of one form or antoher, plays a far more significant role in our "knowledge management" and "learning organizations" than we give credit. </p> ]]>
    </content>
    <published>2006-10-03T04:44:19Z</published>
    <updated>2006-10-03T04:44:19Z</updated>

  </entry> 

</feed>

