title: Why New Systems Fail: An Insider's Guide to Successful IT Projects
author:  Phil Simon 
description: "Simon's book offers practical advice on why IT projects run late, over-budget, and do not achieve planned results. The framework is clear and the examples compelling, making this book a manifesto for success." -Michael Krigsman - CEO of Asuret, Inc., and ZDNet Blogger on IT Project Failures<br /><br />"Projects are multidimensional. They're technical, political, financial, personal, emotional, logistical, and more. Great project leaders anticipate these dimensions before the project begins. Read Phil's book to recognize the pitfalls and minimize their impact on your organization and your career. You can't work the plan until you've really planned the work" - Brian Sommer, founder of TechVentive and Vital Analysis<br /><br />"Simon's book honestly portrays the many small, but crucial, aspects of system failures that too many people in the industry don't want to admit." - Jim Harris, Founder of OCDQBlog, independent consultant, speaker, and writer.<br /><br />"A good read and as insightful as any I have read about enterprise software project management and the obstacles to success." - David F. Carr, independent journalist and former writer for Baseline Magazine
zlib_text: by 
  Joe Natoli
  
  Copyright © 2017 by UXPin Inc.
  All rights reserved. No part of this publication text may be uploaded or 
  posted online without the prior written permission of the publisher. 
  For permission requests, write to the publisher, addressed “Attention: 
  Permissions Request,” to hello@uxpin.com.
  
  Index
  Foreword 
  8
  Revisiting Enterprise Problem-Solving 
  10
  For Startups, Problem Solving Equals Survival 
  11
  Leveraging the UX Value Loop 
  13
  Change Your Thinking, Change the Enterprise 
  14
  Stop Jumping to Solutions 
  16
  UX is Everybody’s Business 
  20
  Get the Right People in the Room 
  23
  Involve stakeholders by calming their fears 
  24
  When the Answer is Still “NO” 
  27
  Draw Hard Lines Between New and Legacy Functionality 
  28
  The Difficult Tradeoff 
  29
  Existing vs. New Users 
  30
  
  User Research: Fast, Early, Often 
  33
  The 1-Page Summary  
  34
  Skip Traditional Personas and Get to Context Quickly 
  35
  Streamline User Interviews  
  38
  If You Can’t Access End Users... 
  40
  Validate User Research 