Show Buttons
Share On Facebook
Share On Twitter
Share On Google Plus
Share On Linkdin
Contact us
Hide Buttons
ERP Software Logo

Microsoft Dynamics vendors provide comparisons and opinions to professionals in the ERP/Accounting software selection process


Anya Ciecierski, CAL Business Solutions

Why is CFO Turnover So High? Are ERP Software Implementations To Blame?

Email | Print

I found a very interesting article in CFO Magazine called “Why is CFO Turnover So High?”  They report that 1 in 4  Fortune 1,000 companies changed their CFO in 2007.  Smaller companies had a lower turnover rate of 10%, but even that number is 25% higher than it was in 2005.   The reasons?  You can read my rather loose translation of 6 reasons why the CFO turnover is so high.   But my favorite is reason #6) Burn out due to large, complex (and expensive) ERP implementations gone bad!  The article says “implementations that should have taken two or three years in some cases took five, six, or more. That tends to burn a person out”.

My response to this last point is that they should have implemented a package like Microsoft Dynamics GP.  Implementations take days or weeks, not years.  And I have personally never seen a CFO “burn out” due to a Microsoft Dynamics GP implementation – even a complicated one! Hint: In anyone feels close to burn out, there is a lot of ERP software implementations tips on this blog!

What is your opinion? Do you see a higher turnover rate for CFOs today?  If so, why do you think this is changing? How is this affecting the staffing industry?

By CAL Business Solutions, Provider of Microsoft Dynamics GP + StaffLinx GP – Connect Bullhorn Front Office to Microsoft Dynamics GP Back Office.

2 Responses to “Why is CFO Turnover So High? Are ERP Software Implementations To Blame?”

  1. […] This post was mentioned on Twitter by RoseBusinessSolution. RoseBusinessSolution said: RT @tweetmeme Why is CFO Turnover So High? Are ERP Software Implementations To Blame? | ERP Software Blog […]

  2. We always suggest STAGED or PHASED implementations just for this reason! You want to see some “wins” for the employees before too much time goes by. Isn’t it better to first replace what you had with a small number of features, then plug more and more in so the employees see the advancements ~ without having to wait years?

Ask This Expert a Question / Leave a Comment


Live chat by BoldChat