tag:blogger.com,1999:blog-4078765814361815863.post3986004770828981600..comments2011-08-31T06:03:59.342-07:00Ed Russellhttp://www.blogger.com/profile/03296647216026995687noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4078765814361815863.post-7908553628076452382008-11-26T05:06:00.000-08:002008-11-26T05:06:00.000-08:00I think most of the time people are swayed mainly by the salesperson and the fact that it is a new system so it must be better. <BR/><BR/>I agree with you - most of the time it is the process that needs looking at, not necessarily the system. Maybe once the processes are sorted then you need a new system or some development to help but people get distracted by the new rather than considering the actual business case for this stuff or even if they have they don't make the connection that their current system might be altered for a fraction of the cost of a new system to provide the functionality they need...Ed Russellhttp://www.blogger.com/profile/03296647216026995687noreply@blogger.comtag:blogger.com,1999:blog-4078765814361815863.post-33580863781652091052008-11-25T12:29:00.000-08:002008-11-25T12:29:00.000-08:00have you considered reviewing the business processes that are followed when using either the old or new shiney system to see if there are methods to update the application and streamline the business - thereby increasing the performance, reducing TCO and improving ROI of any development costs...Davehttp://www.blogger.com/profile/10473640681482698542noreply@blogger.com