At the beginning of a new year, many people create lists of resolutions or goals for the future. Just like you, companies make resolutions, too. Sometimes companies devise intricate ways to monitor and measure results against these goals. Yet, even with these seemingly adequate preparations in place, one continues to hear and read about project failures with nearly 50 percent of enterprise system implementation projects deemed failures. After a poor go-live, there is plenty of finger-pointing, usually at the external implementation and vendor team. But, from my perspective, there is also a significant amount of blame that should be shared by the user organization.
So as a CPA and consultant, I would like to offer some resolutions for companies to keep when implementing a new computer system or undertaking an upgrade effort. These resolutions are based on an aggregation of observations during my work troubleshooting and resolving problems after the fact, and are not unique to any one client experience but are common to many engagements.