<?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/29/hows_the_weather.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2004/05/29/hows_the_weather.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2004://1.281-</id> 
  <updated>2007-12-03T12:05:00Z</updated>
  <title>Comments for How&apos;s the weather?</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.281" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/29/hows_the_weather.html"/>


    <id>tag:blog.jackvinson.com,2004://1.281.118</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/29/hows_the_weather.html#comment-118" /> 
    <title>Comment from Lucas Rodríguez Cervera on 2004-10-21</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 believe that making the project team members aware of the "project weather" is benefitial for the following reasons:<br />
- People like to know all the details of the projects, and are very interested in those to which they don't have access normally.<br />
- The more information team members have, the more identified they feel with the project.<br />
- If cloudy weather is comunicated early, some good ideas might come to light.</p>

<p>Something that should be taken into account is the cost of not sharing this information. Hiding important information about the project environment makes people feel not important for the project.</p> ]]>
    </content>
    <published>2004-10-21T14:04:21Z</published>
    <updated>2004-10-21T14:04:21Z</updated>

  </entry> 

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

    <id>tag:blog.jackvinson.com,2004://1.281.p3112</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2004/05/29/hows_the_weather.html#p3112" /> 
    <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:04Z</published>
    <updated>2006-01-23T04:10:04Z</updated>


  </entry> 

</feed>

