<?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/2004/05/10/km_technology_process_people.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2004/05/10/km_technology_process_people.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2004://1.296-</id> 
  <updated>2007-12-03T12:05:27Z</updated>
  <title>Comments for KM technology, process, people</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,2004://1.296" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/10/km_technology_process_people.html"/>


    <id>tag:blog.jackvinson.com,2004://1.296.132</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/10/km_technology_process_people.html#comment-132" /> 
    <title>Comment from Lucas Rodríguez Cervera on 2004-10-18</title>
    <author>
        <name>Lucas Rodríguez Cervera</name> 
        <uri>http://www.nevant.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.nevant.com">     
      <![CDATA[ <p>I agree 100% with the opinion that:</p>

<p>"knowledge must be embedded into the workflow layer of an organization in order to ensure a level of success and "measurable results"</p>

<p>From my point of view that could be considered as the prime objective of KM. Managing knowledge does not mean buying a tool, and making knowledge explicit. Even sharing knowledge itself has no value. Value comes to light when people apply the things to their daily work.</p>

<p>Software tools, best practice documents and knowledge sharing are only tools to make knowledge "available for use" where it produces value (its application to the daily work). And that can be acomplished by designing processes and workflow that transmit smart ways of carrying out a job.</p>

<p>Lucas Rodríguez Cervera</p> ]]>
    </content>
    <published>2004-10-18T18:06:50Z</published>
    <updated>2004-10-18T18:06:50Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2004://1.296" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/10/km_technology_process_people.html"/>

    <id>tag:blog.jackvinson.com,2004://1.296.p3113</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/10/km_technology_process_people.html#p3113" /> 
    <title>Trackback in article Embedded knowledge from Knowledge Jolt with Jack</title>
    <author>
        <name>Knowledge Jolt with Jack</name> 
        <uri>http://blog.jackvinson.com/archives/2004/10/24/embedded_knowledge.html</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.jackvinson.com/archives/2004/10/24/embedded_knowledge.html"> 
        <p>
              Comments and recent discussion has me thinking about KM.  Knowledge is has to be built into how organizations AND people do business -- and at that point it is almost fruitless to talk about knowledge itself.  The important thing becomes questions arou... <a href="http://blog.jackvinson.com/archives/2004/10/24/embedded_knowledge.html">[Read More]</a>
        </p>
    </content>
    <published>2006-01-23T04:10:05Z</published>
    <updated>2006-01-23T04:10:05Z</updated>


  </entry> 

</feed>
