Lexicon Systems, LLC Blog

lex'•i•con: the vocabulary of a branch of knowledge. Thoughts on environment, health & safety (EHS), sustainability and information technology to support them.


Leave a comment

Debunking common software implementation myths

I read an article this morning about three ERP (enterprise resource planning) implementation myths. I come across the same ones in EHS (environment, health & safety) software implementations. Let the debunking begin…

Myth 1. You cannot use your software selection consultant to implement the software.

no entryI have seen resistance to using a software selection consultant to implement the software. The hiring organization perceived that the consulting firm could not do both; there should be a separation between selection and implementation.

If your consultant has proven project management, communications, subject matter and technical skills to successfully implement the software, then use them. Once your consultant helps you to document and prioritize needs and select software, then they know your needs and business better than anyone else at this point! Take advantage of this knowledge.

Bringing in another group to implement the software will cost you lost productivity, duplication of efforts, extended timelines, and other avoidable costs.

Myth 2. You must have a software vendor or reseller implement your software.

sign-160675_1280While the software vendor/reseller should be conversant in the software, they may lack subject matter expertise or a broader perspective of implementation best practices.

Instead, I recommend a team approach to implementation:

  1. an integrator/implementer that is comfortable with the software and its configuration,
  2. vendor representatives–implementation and product specialists, and
  3. software customer key stakeholders.

Myth 3. The most important aspect of implementation is technical proficiency.

signs-38588_1280I have seen talented technical staff lead software implementations that become “challenged” when the teams focused solely on technical issues.  Warning!

Instead, I recommend a team skilled in several disciplines. Beyond technical (IT) proficiency, subject matter expertise, and industry experience, remember to round out the team with skill sets such as:

  • project management
  • risk management
  • business process management
  • organizational change management
  • training
  • analytics
  • etc.

With these implementation myths are debunked, you can make more informed decisions on your path forward for software implementation. This is my “quick take.” You can read the Panorama Consulting perspective here.

Advertisements