<?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/01/29/why_change.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2007/01/29/why_change.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2007://1.8119-</id> 
  <updated>2007-12-03T11:42:40Z</updated>
  <title>Comments for Why change?</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.8119" type="text/html" href="http://blog.jackvinson.com/archives/2007/01/29/why_change.html"/>


    <id>tag:blog.jackvinson.com,2007://1.8119.17803</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/01/29/why_change.html#comment-17803" /> 
    <title>Comment from Shawn Callahan on 2007-01-30</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>[duplicate comment deleted]</p> ]]>
    </content>
    <published>2007-01-30T09:18:36Z</published>
    <updated>2007-01-30T09:18:36Z</updated>

  </entry> 

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


    <id>tag:blog.jackvinson.com,2007://1.8119.17804</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/01/29/why_change.html#comment-17804" /> 
    <title>Comment from Shawn Callahan on 2007-01-30</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>You make a good point Jack. I should have said that the strategic intent provides direction for the change. </p>

<p>I was wondering whether you have any ideas on how one helps a group of people articulate their intent? I will blog this idea later but I think you need to take an organisation through three journeys: 1) the development of the strategic intent by a leadership group (might be people throught an organisation not just the most senior people); 2) the involvement of the staff in developing the mud map based on experiences (stories); and 3) actually going on the change journey in the full knowledge that it wont look like they way it was planned. </p> ]]>
    </content>
    <published>2007-01-30T09:19:27Z</published>
    <updated>2007-01-30T09:19:27Z</updated>

  </entry> 

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


    <id>tag:blog.jackvinson.com,2007://1.8119.17805</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/01/29/why_change.html#comment-17805" /> 
    <title>Comment from jackvinson on 2007-01-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, Shawn.  </p>

<p>On first glance, I suspect the articulation of strategic intent is a chicken-and-egg thing.  The group needs to know what the higher-level strategy is (make money now and in the future; increase shareholder value; increase profits; increase production at the production facility; etc) to know how to make sense of their own strategies.  </p>

<p>In my work with clients, it is also quite helpful to see what is "good enough" to get people moving in the right direction.  Specifically, along with the strategic plans they need to uncover and consider the negative ramifications and obstacles of the approach.  This is where the stories and their built-in sense about how the organization works are very helpful.  It is hard to uncover the specifics issues without getting the longer descriptions and stories about why things have worked (or not) in the past.  Once you have those, then there is a clearer path to building a pathway.</p>

<p>I may be getting too deep into the tactics here, while you want to stay up at the strategic level.  <br />
</p> ]]>
    </content>
    <published>2007-01-30T16:25:00Z</published>
    <updated>2007-01-30T16:25:00Z</updated>

  </entry> 

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


    <id>tag:blog.jackvinson.com,2007://1.8119.17806</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2007/01/29/why_change.html#comment-17806" /> 
    <title>Comment from Shawn Callahan on 2007-01-30</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>Tactics are good Jack. I think one of the tactics is to help people describe what's outside the intent or out of scope. Defining an intent by what it is not is helpful. This helps you discern when you are heading in the wrong direction. Thanks again for helping me clarify my thoughts.</p> ]]>
    </content>
    <published>2007-01-30T21:11:22Z</published>
    <updated>2007-01-30T21:11:22Z</updated>

  </entry> 

</feed>
