Top 10 ERP Implementation Myths Blog Series – Part 5

ERP Implementation Myth Number 5:  This is an IT project

ERP software is a technology product and IT will play an important role in supporting the chosen ERP product.  IT needs to be involved in the process to make sure that the underlying technology is sound and consistent with the overall business technology strategy.  As keeper of the company systems and data, IT often has a strong understanding of operations within each part of the organization and a broad understanding of how different parts of the overall organization work together.  This knowledge can make IT a critical part of the selection and implementation process.

But ERP software is a business tool that will be used by end users and business managers on a daily basis.  In order to insure acceptance and ownership of the new ERP system, business users need to take ownership of the selection process and accept a leading role in the implementation.  A high value ERP implementation should be about more than just processing transactions—it should be about how the ERP system and its implementation support higher level business goals.  For example, every ERP system can handle the procurement and receiving (transactions).  But which systems can automate inbound inspection processes to minimize inventory handling and provide insight into vendor performance to help drive down inventory costs and maximize purchasing discounts (business goals)?  IT is accountable for making sure the system accepts the transactions, but business leaders are held accountable for business performance.  Implementing your ERP system to achieve business goals will insure that you get the most value from your investment.

  1. You can’t spare your best people
    1. They know your business best
    2. Plan on back filling
    3. Create superstars
  2. Everyone should be involved
    1. Implementation teams are not a democracy
    2. Small, focused teams are more successful
  3. You can implement in a bubble
    1. Publicize progress
    2. Celebrate early success
    3. Help end users transition
    4. Don’t go it alone
  4. You will document and train later
    1. How well have you done this in the past?
    2. Training is the key to continued value
    3. Do it while you are thinking about it and reduce the effort
  5. You can ignore business reality
    1. Be pragmatic about the business drivers of the project
    2. Don’t over reach or over sell
    3. Plan for competing priorities
    4. Design a project that works

Be sure to subscribe to this blog’s RSS feed so that you don’t miss the rest of this blog series.

If you missed any of the previous Myths, you can check them out here:

ERP Implementation Myth Number 1:  One size fits all

ERP Implementation Myth Number 2:  Your current system defines your needs

ERP Implementation Myth Number 3: You will have a no modification policy

ERP Implementation Myth Number 4: All functionality is created equal

Richard Garraputa, VP Sales and Marketing,  brij Image and Information




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s