<?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/02/09/change_and_toc.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2006/02/09/change_and_toc.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2006://1.7792-</id> 
  <updated>2007-12-03T11:49:43Z</updated>
  <title>Comments for Change and TOC</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.7792" type="text/html" href="http://blog.jackvinson.com/archives/2006/02/09/change_and_toc.html"/>


    <id>tag:blog.jackvinson.com,2006://1.7792.3286</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/02/09/change_and_toc.html#comment-3286" /> 
    <title>Comment from Bill Brantley on 2006-02-10</title>
    <author>
        <name>Bill Brantley</name> 
        <uri>http://eclecticbill.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://eclecticbill.blogspot.com">     
      <![CDATA[ <p>Wouldn't you agree that TOC provides a better way to analyze the need for change and clearer criteria for determining what needs to be changed.</p>

<p>With Ryder's "choose your pain", I feel that organizations would choose the most immediate and easiest thing to change rather than tackling the underlying constraint.  The identification of the "right problem to solve" means finding the problem that produces the most value if it is solved.  This seems like it would force organizations to solve local optima problems rather than looking for the global optimal solution as Goldratt suggests.</p> ]]>
    </content>
    <published>2006-02-10T14:27:39Z</published>
    <updated>2006-02-10T14:27:39Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2006://1.7792" type="text/html" href="http://blog.jackvinson.com/archives/2006/02/09/change_and_toc.html"/>


    <id>tag:blog.jackvinson.com,2006://1.7792.3287</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2006/02/09/change_and_toc.html#comment-3287" /> 
    <title>Comment from jackvinson on 2006-02-10</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 Bill.  It's certainly not a perfect parallel, but once you've chosen the right problem, the pain should be a lot more obvious...  This is the process of understanding the current situation and all the problems (undesirable effects), and working through them to discover the (likely) one underlying cause of all of the undesirable effects. </p> ]]>
    </content>
    <published>2006-02-10T17:11:06Z</published>
    <updated>2006-02-10T17:11:06Z</updated>

  </entry> 

</feed>

