What Your ERP Implementation Reveals About Your Business
An ERP (enterprise resource planning) implementation can do more than introduce new technology—it can reveal how an organization actually operates, including inefficient processes, workarounds, poor documentation and unclear responsibilities. In his Forbes article, Marc Blythe, president of Blythe Global Advisors, explains that organizations can make the mistake of configuring a new ERP before fully understanding their existing processes, data and operational needs. When issues arise after go-live, companies may rely on manual controls or costly customization instead of addressing the underlying process. Blythe highlights the common mindset that “our business is different.” While some specialized requirements are legitimate, this thinking can also discourage organizations from questioning processes simply because they have always been done that way. Involving business teams and middle management early can help identify how work actually happens and where processes could be simplified before customization begins. Successful implementations, Blythe argues, require close collaboration between business and IT, testing with actual users, clear documentation and a willingness to ask difficult questions: Why do we do it this way? Is this truly a business requirement? Could the process be simpler? For CFOs and other leaders, an ERP implementation can be an opportunity to rethink how the organization operates—not simply recreate the old system in a new platform.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
