<?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/28/us_government_defines_knowledge_management.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2006://1.7964-</id> 
  <updated>2007-12-03T11:46:20Z</updated>
  <title>Comments for US Government defines &quot;knowledge management&quot;</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.7964" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html"/>


    <id>tag:blog.jackvinson.com,2006://1.7964.8453</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html#comment-8453" /> 
    <title>Comment from Yigal Chamish on 2006-08-28</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>It is Technology-Focused indeed. However, it is important to mention the cultural aspects of Knowledge Management as well.</p> ]]>
    </content>
    <published>2006-08-28T16:26:28Z</published>
    <updated>2006-08-28T16:26:28Z</updated>

  </entry> 

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


    <id>tag:blog.jackvinson.com,2006://1.7964.8578</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html#comment-8578" /> 
    <title>Comment from James on 2006-08-29</title>
    <author>
        <name>James</name> 
        <uri>http://duckdown.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://duckdown.blogspot.com">     
      <![CDATA[ <p>OK, they have defined it, now will they screw it up on execution?</p> ]]>
    </content>
    <published>2006-08-29T11:01:44Z</published>
    <updated>2006-08-29T11:01:44Z</updated>

  </entry> 

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


    <id>tag:blog.jackvinson.com,2006://1.7964.8665</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html#comment-8665" /> 
    <title>Comment from Shawn Callahan on 2006-08-29</title>
    <author>
        <name>Shawn Callahan</name> 
        <uri>http://www.anecdote.com.au</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.anecdote.com.au">     
      <![CDATA[ <p>This seems to be such a limited view of knowledge management and totally avoids the issue of 'knowledge,' that is, the stuff in our heads. Only focussing on information will defintely lead to more databases and document repositories and little been done with attracting and maintaining talent, peer assists, expertise location, communities of practice and a myriad of other KM practices with about connecting people. As you can see this gets me a little hot under the collar because it perpetuates an unhelpful, in my opinion, view of knowledge management.</p> ]]>
    </content>
    <published>2006-08-30T00:05:00Z</published>
    <updated>2006-08-30T00:05:00Z</updated>

  </entry> 

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

    <id>tag:blog.jackvinson.com,2006://1.7964.p54916</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html#p54916" /> 
    <title>Trackback in article KM definitions from my perspective from Knowledge Jolt with Jack</title>
    <author>
        <name>Knowledge Jolt with Jack</name> 
        <uri>http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html"> 
        <p>
              I linked to the techno-centric description from the US government a few days ago, and both Yigal Chamish and Shawn Callahan rightly complained in the comments that it missed whole aspects of KM that are important to the field.  Here is some thought on ... <a href="http://blog.jackvinson.com/archives/2006/08/29/km_definitions_from_my_perspective.html">[Read More]</a>
        </p>
    </content>
    <published>2006-08-30T04:59:42Z</published>
    <updated>2006-08-30T04:59:42Z</updated>


  </entry> 

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


    <id>tag:blog.jackvinson.com,2006://1.7964.9338</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html#comment-9338" /> 
    <title>Comment from Don Mezei on 2006-09-03</title>
    <author>
        <name>Don Mezei</name> 
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">     
      <![CDATA[ <p>Hi Jack,<br />
KM is any process which incoporates the desire to expand our range of inquiry with the need to simplify our options or decisions.</p>

<p>Don Mezei</p> ]]>
    </content>
    <published>2006-09-03T21:02:35Z</published>
    <updated>2006-09-03T21:02:35Z</updated>

  </entry> 

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


    <id>tag:blog.jackvinson.com,2006://1.7964.10602</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/08/28/us_government_defines_knowledge_management.html#comment-10602" /> 
    <title>Comment from James Taylor on 2006-09-14</title>
    <author>
        <name>James Taylor</name> 
        <uri>http://www.edmblog.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.edmblog.com">     
      <![CDATA[ <p>This is an OK definition but it seems to me that it misses a key point - "doing". Would a definition more like "Defines the set of capabilities that support the identification, gathering and transformation of documents, reports and other sources into meaningful <strong>action</strong>." be more useful? What good is knowledge if we don't plan to act on it. This distinction - knowledge management and operational decision-making is one that comes up all over, not just in government (see this post on <a href="http://www.edmblog.com/weblog/2006/04/segmentation_in.html">insurance segmentation</a> as an example.<br />
I suppose "Knowledge Distribution and Delivery" somewhat addresses this but not really.</p> ]]>
    </content>
    <published>2006-09-14T18:09:28Z</published>
    <updated>2006-09-14T18:09:28Z</updated>

  </entry> 

</feed>
