<?xml version="1.0" encoding="UTF-8"?>
<GoodreadsResponse>
	<Request>
		<authentication>false</authentication>
		    <method><![CDATA[]]></method>
	</Request>
	
<book>
  <id>6468782</id>
  <title><![CDATA[Why New Systems Fail: Theory and Practice Collide]]></title>
  <isbn><![CDATA[1438944241]]></isbn>
  <isbn13><![CDATA[9781438944241]]></isbn13>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <description><![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]></description>
  <work>
  <best_book_id type="integer">6468782</best_book_id>
  <books_count type="integer">2</books_count>
  <desc_user_id type="integer" nil="true"></desc_user_id>
  <id type="integer">6659364</id>
  <media_type nil="true"></media_type>
  <original_language_id type="integer" nil="true"></original_language_id>
  <original_publication_day type="integer">4</original_publication_day>
  <original_publication_month type="integer">2</original_publication_month>
  <original_publication_year type="integer">2009</original_publication_year>
  <original_title>Why New Systems Fail: Theory and Practice Collide</original_title>
  <rating_dist>total:2|5:2|</rating_dist>
  <ratings_count type="integer">2</ratings_count>
  <ratings_sum type="integer">10</ratings_sum>
  <reviews_count type="integer">12</reviews_count>
  <text_reviews_count type="integer">0</text_reviews_count>
</work>

  <average_rating><![CDATA[5.00]]></average_rating>
  <ratings_count><![CDATA[2]]></ratings_count>
  <text_reviews_count><![CDATA[0]]></text_reviews_count>
  
  <url><![CDATA[http://www.goodreads.com/book/show/6468782-why-new-systems-fail]]></url>
  <link><![CDATA[http://www.goodreads.com/book/show/6468782-why-new-systems-fail]]></link>
  <authors>
    <author>
    <id>2930727</id>
        <name><![CDATA[Phil Simon]]></name>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-200x266.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-50x66.jpg]]></small_image_url>
    <link><![CDATA[http://www.goodreads.com/author/show/2930727.Phil_Simon]]></link>
    <average_rating>5.00</average_rating>
    <ratings_count>2</ratings_count>
    <text_reviews_count>0</text_reviews_count>
  </author>
  </authors>
    <reviews start="1" end="12" total="12">
      <review>
  <id>76808562</id>
    <user>
    <id>2911369</id>
    <name><![CDATA[Brian]]></name>
    <location><![CDATA[Severn, MD]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2911369-brian-gregory]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1257454721p3/2911369.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1257454721p2/2911369.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Nov 05 08:41:08 -0800 2009</date_added>
  <date_updated>Thu Nov 05 08:41:08 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/76808562]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/76808562]]></link>
</review>
      <review>
  <id>68803233</id>
    <user>
    <id>2530874</id>
    <name><![CDATA[John]]></name>
    <location><![CDATA[Tampa, FL]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2530874-john-glover]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Aug 25 05:32:38 -0700 2009</date_added>
  <date_updated>Tue Aug 25 05:32:38 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/68803233]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/68803233]]></link>
</review>
      <review>
  <id>67483547</id>
    <user>
    <id>1881793</id>
    <name><![CDATA[Anthony]]></name>
    <location><![CDATA[Mclean, VA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1881793-anthony]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1232851807p3/1881793.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1232851807p2/1881793.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="tech-books" />
        <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Aug 15 07:32:15 -0700 2009</date_added>
  <date_updated>Sat Aug 15 07:32:22 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/67483547]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/67483547]]></link>
</review>
      <review>
  <id>65744592</id>
    <user>
    <id>2530249</id>
    <name><![CDATA[Phil]]></name>
    <location><![CDATA[West Orange, NJ]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2530249-phil-simon]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1247774267p3/2530249.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1247774267p2/2530249.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Aug 01 03:57:33 -0700 2009</date_added>
  <date_updated>Sat Aug 01 03:57:33 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/65744592]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/65744592]]></link>
</review>
      <review>
  <id>64131199</id>
    <user>
    <id>732430</id>
    <name><![CDATA[Jim]]></name>
    <location><![CDATA[Houston, TX]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/732430-jim]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1199246748p3/732430.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1199246748p2/732430.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sun Jul 19 15:08:12 -0700 2009</date_added>
  <date_updated>Sun Jul 19 15:08:12 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/64131199]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/64131199]]></link>
</review>
      <review>
  <id>63794916</id>
    <user>
    <id>2174994</id>
    <name><![CDATA[Jeff]]></name>
    <location><![CDATA[Taipei, 03, Taiwan]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2174994-jeff]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1238591806p3/2174994.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1238591806p2/2174994.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="projects" />
        <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Jul 16 18:33:00 -0700 2009</date_added>
  <date_updated>Thu Jul 16 18:33:40 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63794916]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63794916]]></link>
</review>
      <review>
  <id>63698916</id>
    <user>
    <id>2259661</id>
    <name><![CDATA[Zcasper]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2259661-zcasper]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Jul 16 05:23:32 -0700 2009</date_added>
  <date_updated>Thu Jul 16 05:23:32 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63698916]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63698916]]></link>
</review>
      <review>
  <id>63698255</id>
    <user>
    <id>935410</id>
    <name><![CDATA[Rcharbon]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/935410-rcharbon]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1206702155p3/935410.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1206702155p2/935410.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Jul 16 05:11:41 -0700 2009</date_added>
  <date_updated>Thu Jul 16 05:11:41 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63698255]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63698255]]></link>
</review>
      <review>
  <id>63642202</id>
    <user>
    <id>864435</id>
    <name><![CDATA[Joel]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/864435-joel]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1201986662p3/864435.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1201986662p2/864435.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Jul 15 16:05:39 -0700 2009</date_added>
  <date_updated>Wed Jul 15 16:05:39 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63642202]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63642202]]></link>
</review>
      <review>
  <id>63632739</id>
    <user>
    <id>1268578</id>
    <name><![CDATA[Michael]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1268578-michael]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="computer" />
        <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Jul 15 14:37:49 -0700 2009</date_added>
  <date_updated>Wed Jul 15 14:37:49 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63632739]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63632739]]></link>
</review>
      <review>
  <id>63612288</id>
    <user>
    <id>2143689</id>
    <name><![CDATA[John]]></name>
    <location><![CDATA[Hesston, KS]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2143689-john]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1237504691p3/2143689.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1237504691p2/2143689.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6618465</id>
  <isbn nil="true"></isbn>
  <isbn13 nil="true"></isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail]]>
  </title>
  <image_url>http://www.goodreads.com/images/nocover-111x148.jpg</image_url>
  <small_image_url>http://www.goodreads.com/images/nocover-60x80.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6618465-why-new-systems-fail</link>
  <average_rating>0.0</average_rating>
  <ratings_count>0</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 manufacturing company implementing a multimillion dollar enterprise resource planning (ERP) system have in common with a 150 employee marketing firm that built a proprietary customer relationship management (CRM) system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.<br/><br/>These two organizations are hardly alone. On the contrary, research indicates that more than three in five new systems fail.1 Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.<br/><br/>While the statistics are grim, there is at least some good news:<br/><br/>These failures can be averted.<br/><br/>Organizations often lack the necessary framework to minimize the chance of system failure before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and insight from the perspective of a seasoned, independent consultant with more than a decade of related experience.<br/>The book examines in great detail the root causes of system failures. Detailed case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="business" />
        <shelf name="computing" />
        <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[http://books.slashdot.org/story/09/07/15/1255258/Why-New-Systems]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Jul 15 12:10:55 -0700 2009</date_added>
  <date_updated>Wed Jul 15 12:11:23 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63612288]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63612288]]></link>
</review>
      <review>
  <id>58099682</id>
    <user>
    <id>1855107</id>
    <name><![CDATA[Tim]]></name>
    <location><![CDATA[Eastleigh, Hampshire, The United Kingdom]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1855107-tim]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1242808582p3/1855107.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1242808582p2/1855107.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">6468782</id>
  <isbn>1438944241</isbn>
  <isbn13>9781438944241</isbn13>
  <text_reviews_count type="integer">0</text_reviews_count>
  <title>
    <![CDATA[Why New Systems Fail: Theory and Practice Collide]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1256081667m/6468782.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1256081667s/6468782.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/6468782-why-new-systems-fail</link>
  <average_rating>5.00</average_rating>
  <ratings_count>2</ratings_count>
  <description>
    <![CDATA[What does a Fortune 500 company implementing a multimillion dollar &quot;off the shelf&quot; system have in common with a 150 person firm building its own system? In each case, the organization failed to activate and utilize its system as initially conceived by senior management.     These two organizations are hardly alone. On the contrary, more than three in five new systems fail. Many miss their deadlines. Others exceed their initial budgets, often by ghastly amounts. Even systems activated on time and under budget often fail to produce their expected results and almost immediately experience major problems.     While the statistics are grim, there is at least some good news:    This doesn't have to be the case.    Organizations often lack the necessary framework to minimize the chance of system failure at three key points: before, during, and after system implementations. Why New Systems Fail provides such a framework with specific tools, tips, and questions from the perspective of a seasoned, independent consultant with more than a decade of related experience.    The book examines in great detail the root causes of system failures. Case studies, examples, and lessons from actual system implementations are presented in an informative, straightforward, and very readable manner. More than a theoretical or technical text, the book offers pragmatic advice for organizations both deploying new systems and maintaining existing ones.]]>
  </description>
  <published>2009</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Mon Jun 01 15:33:14 -0700 2009</date_added>
  <date_updated>Mon Jun 01 15:33:14 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/58099682]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/58099682]]></link>
</review>
    </reviews>
  <popular_shelves>
          <shelf name="to-read" />
          <shelf name="tech-books" />
          <shelf name="projects" />
          <shelf name="computer" />
          <shelf name="computing" />
          <shelf name="business" />
      </popular_shelves>
  <book_links>
    <book_link>
  <id>8</id>
  <name><![CDATA[WorldCat]]></name>
  <link>http://www.goodreads.com/book_link/follow/8?book_id=6468782</link>
</book_link>
  </book_links>
</book>
</GoodreadsResponse>