<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Time for new accounting software? Some things to think about…..</title>
	<atom:link href="http://www.missionaccountable.com/2009/06/15/time-for-new-accounting-software-some-things-to-think-about%e2%80%a6/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.missionaccountable.com/2009/06/15/time-for-new-accounting-software-some-things-to-think-about%e2%80%a6/</link>
	<description>a blog for tax-exempt organizaitons serving the needs of Ft Worth and surrounding communities</description>
	<lastBuildDate>Fri, 19 Aug 2011 02:18:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Sylvain</title>
		<link>http://www.missionaccountable.com/2009/06/15/time-for-new-accounting-software-some-things-to-think-about%e2%80%a6/comment-page-1/#comment-191</link>
		<dc:creator>Sylvain</dc:creator>
		<pubDate>Sun, 28 Jun 2009 17:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.missionaccountable.com/?p=1261#comment-191</guid>
		<description>I agree with Doug too. I also agree with Jaye when he says it all depends on the size of your organization. The more people you have to convert to a new system, the harder the work and the longer the learning curve. Some will dig the new software right away, some will complain but will finally get used to it and some will totally hate it because it&#039;s not like the old one, it doesn&#039;t do this and that like the old one, blah blah blah. Unfortunately, several large enterprises are stuck with their old, outdated systems because of stubbornness and fear of change. It&#039;s not always the enterprise itself, but rather some refractory employees who worked with that system for so many years and hence, nothing else can be better. This is less common in smaller businesses where productivity and success is worth more than good old habits.</description>
		<content:encoded><![CDATA[<p>I agree with Doug too. I also agree with Jaye when he says it all depends on the size of your organization. The more people you have to convert to a new system, the harder the work and the longer the learning curve. Some will dig the new software right away, some will complain but will finally get used to it and some will totally hate it because it&#8217;s not like the old one, it doesn&#8217;t do this and that like the old one, blah blah blah. Unfortunately, several large enterprises are stuck with their old, outdated systems because of stubbornness and fear of change. It&#8217;s not always the enterprise itself, but rather some refractory employees who worked with that system for so many years and hence, nothing else can be better. This is less common in smaller businesses where productivity and success is worth more than good old habits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaye Helm</title>
		<link>http://www.missionaccountable.com/2009/06/15/time-for-new-accounting-software-some-things-to-think-about%e2%80%a6/comment-page-1/#comment-189</link>
		<dc:creator>Jaye Helm</dc:creator>
		<pubDate>Wed, 24 Jun 2009 14:22:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.missionaccountable.com/?p=1261#comment-189</guid>
		<description>I 100% agree.  My last conversion we only did 3 months of running parallel systems, and I would suggest 3 as a bare minimum.  6 months is probably closer to ideal.  Often this can be worked out with the new software vendor so that there&#039;s not a huge financial consequence if you decide to stay with your old system. 
Hopefully, I can crank out my sequel blog post about implementation here pretty soon and we&#039;ll mention the parallel thing definitely.
Later Doug.  Keep up the piano playing and thanks for the response, we appreciate it !! -jh</description>
		<content:encoded><![CDATA[<p>I 100% agree.  My last conversion we only did 3 months of running parallel systems, and I would suggest 3 as a bare minimum.  6 months is probably closer to ideal.  Often this can be worked out with the new software vendor so that there&#8217;s not a huge financial consequence if you decide to stay with your old system.<br />
Hopefully, I can crank out my sequel blog post about implementation here pretty soon and we&#8217;ll mention the parallel thing definitely.<br />
Later Doug.  Keep up the piano playing and thanks for the response, we appreciate it !! -jh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Briley</title>
		<link>http://www.missionaccountable.com/2009/06/15/time-for-new-accounting-software-some-things-to-think-about%e2%80%a6/comment-page-1/#comment-187</link>
		<dc:creator>Doug Briley</dc:creator>
		<pubDate>Mon, 22 Jun 2009 16:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.missionaccountable.com/?p=1261#comment-187</guid>
		<description>Software can hold you hostage, Jay. It can keep you from moving forward, because you don&#039;t know what trouble you&#039;ll encounter with a major change, so many organizations keep doing what&#039;s known rather than tackling the unknown. May I suggest a parallel path (yes, double the work for a short time) using two systems simultaneously before making a head-first jump into the new software. The last half of your fiscal year is a good time to try something like this, which lets you abandon the new if it doesn&#039;t work out. If you like the new software, you may be up-to-speed with it by the time the new fiscal year starts, which is a great time to make a clean break.</description>
		<content:encoded><![CDATA[<p>Software can hold you hostage, Jay. It can keep you from moving forward, because you don&#8217;t know what trouble you&#8217;ll encounter with a major change, so many organizations keep doing what&#8217;s known rather than tackling the unknown. May I suggest a parallel path (yes, double the work for a short time) using two systems simultaneously before making a head-first jump into the new software. The last half of your fiscal year is a good time to try something like this, which lets you abandon the new if it doesn&#8217;t work out. If you like the new software, you may be up-to-speed with it by the time the new fiscal year starts, which is a great time to make a clean break.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

