<?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/2007/10/29/boeing_on_knowledge_management.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2007://1.8456-</id> 
  <updated>2007-12-03T11:17:25Z</updated>
  <title>Comments for Boeing on knowledge management</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,2007://1.8456" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html"/>


    <id>tag:blog.jackvinson.com,2007://1.8456.18261</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html#comment-18261" /> 
    <title>Comment from reasonable robinson on 2007-10-30</title>
    <author>
        <name>reasonable robinson</name> 
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">     
      <![CDATA[ <p>Looks like Boeing are implementing a typical Neo Modernist knowledge management approach that is founded upon a managerialist version of the organisational learning philosophy. In other words 'we need to control, measure, and create a knowledge management environment' Additionally the seem to 'see' this KM as a technically driven process. All of these notions should be contested. Knowledge, Know What and Know How and the process of Knowing are as much the asset of the employed as the employee and as such should be discussed in a negotiated context and not simply 'captured' to secure competitive advantage. Additionaly merely identifying, storing and distrubuting 'knowledge' cannot of itself ever ensure competitive advanatge. This is simply a fadland management mantra that is delusional in its expectations.</p> ]]>
    </content>
    <published>2007-10-30T08:13:56Z</published>
    <updated>2007-10-30T08:13:56Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2007://1.8456" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html"/>


    <id>tag:blog.jackvinson.com,2007://1.8456.18262</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html#comment-18262" /> 
    <title>Comment from jackvinson on 2007-10-30</title>
    <author>
        <name>jackvinson</name> 
        <uri>http://blog.jackvinson.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.jackvinson.com">     
      <![CDATA[ <p>Thanks for your comment, RR.   </p>

<p>The issues you've identified are right up there in my mind with the fallacies of "enterprise knowledge management" as promoted in the 1990's.  While some of that is happening in the Boeing example, I could also see a lot of opportunity for them to move beyond this view of KM and into a view where people (the employees) are encouraged to have more control over the process.</p> ]]>
    </content>
    <published>2007-10-30T13:45:06Z</published>
    <updated>2007-10-30T13:45:06Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2007://1.8456" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html"/>


    <id>tag:blog.jackvinson.com,2007://1.8456.18264</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html#comment-18264" /> 
    <title>Comment from Jerry Ash on 2007-10-30</title>
    <author>
        <name>Jerry Ash</name> 
        <uri>http://www.kwork.org</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.kwork.org">     
      <![CDATA[ <p>Hi Jack.</p>

<p>Great find on Boeing. I'm currently working with Pauline DeGard, knowledge strategist at Boeing, on a case report for the December/January issue of Inside Knowledge magazine. By the way, I've given it the working title of "Chasing the Vapor Trail". </p>

<p>What's happened at Boeing, like many companies, is that the advent of personal computing has fractured the organizational database and the company's critical knowledge is now scattered among personal computers and in a plethora of formats. Today's social network approach to decision-making takes place to a great extent in email with documents stored as attachments.</p>

<p>Compounding the problem is what Paulette DeGard describes in Star Wars language as the changing of the guard from "Masters" to "Padiwans" as the graybeard retire and young apprentices take their places.</p>

<p>Paulette and her team have done an amazing job of pulling existing knowledge and information together and that's what my story is all about. It will be in the December/January issue (my first as the new managing editor). </p>

<p>Congratulations on being on top of things!</p>

<p>Jerry Ash<br />
Managing Editor, Inside Knowledge magazine<br />
Founder/manager, Association of Knowledgework</p>

<p>jash@kwork.org<br />
<a href="http://www.ikmagazine.com">http://www.ikmagazine.com</a><br />
<a href="http://www.kwork.com">http://www.kwork.com</a></p> ]]>
    </content>
    <published>2007-10-31T01:37:12Z</published>
    <updated>2007-10-31T01:37:12Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2007://1.8456" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html"/>


    <id>tag:blog.jackvinson.com,2007://1.8456.18281</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html#comment-18281" /> 
    <title>Comment from Jim Coogan on 2007-11-06</title>
    <author>
        <name>Jim Coogan</name> 
        <uri>http://www.boeing.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.boeing.com">     
      <![CDATA[ <p>The problem with such a short article is that people can get the wrong ideas based on very small amounts of information.  KM at Boeing is far from technology centric.  There was only one slight error in the article.  We do not define KM loosely.  It is defined as a disciplined holistic approach to effectively utilize expertise for competitive advantage.  And what we mean by this is that it starts and ends with people.  What we practice, and have done so for over 14 years, is a very people centric form of KM.  </p> ]]>
    </content>
    <published>2007-11-06T06:58:20Z</published>
    <updated>2007-11-06T06:58:20Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2007://1.8456" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html"/>


    <id>tag:blog.jackvinson.com,2007://1.8456.18282</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/10/29/boeing_on_knowledge_management.html#comment-18282" /> 
    <title>Comment from Jack Vinson on 2007-11-06</title>
    <author>
        <name>Jack Vinson</name> 
        <uri>http://blog.jackvinson.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.jackvinson.com">     
      <![CDATA[ <p>Thanks for jumping into the conversation to correct that misinterpretation.  Given the brevity of the article and all the efforts mentioned, I am not surprised that people could get the wrong impression.  <br />
</p> ]]>
    </content>
    <published>2007-11-06T16:56:46Z</published>
    <updated>2007-11-06T16:56:46Z</updated>

  </entry> 

</feed>
