Our recent ERP benchmark study (soon-to-be-released) points out the obvious relationship between ERP selection success and ERP implementation success, that is: a failed selection project inevitably results in a failed implementation project. Now, ruminate on this statistic - a paltry 32% of ERP selection projects succeed. This means that 68% of ERP projects are destined to fail before implementation even starts.

ERP selection failure (and ERP failure in general) can almost always be traced to some avoidable root cause. An organization's task, therefore, is to identify and deal with potential root causes before they cause damage. This is what we call risk management.

Now, although each organization operates within its own unique set of circumstances, certain risk factors act as common threats to ERP selection projects. In this article, I highlight a few of these key threat areas, their potential consequences, and some tactics to manage them.

Risk Category 1: Business Risk
Risk Factor:
An ERP Project That Doesn't Product Positive Value
Risk Category 2: Project Management Risk
Risk Factor:
A Runaway ERP Selection Project
Risk Factor: Unduly Influenced or Biased Process
Risk Factor: Unresponsive Proposals
Risk Category 3: Evaluations Risk
Risk Factor:
Poor Decision-Making
Risk Category 4: Contractual and Legal Risk
Risk Factor:
Poor Implementation Performance
In summary, there will always be risks that threaten the success of an organization's ERP selection project. I've only highlighted a few of the most common. If your company is starting an ERP selection project or is in the middle of an ERP selection project, it should take a step back and see whether its risks are adequately mitigated.

If you're concerned that your organization might be exposing itself to too much ERP selection risk, give us a call. We would be happy to discuss whether your project might benefit from an ERP selection risk assessment and mitigation plan.


Originally posted on Pemeco's Blog

Quash ERP Selection Failure Risks Before They Torpedo Your Project

Categories

All

General

Accessibility

Business events

Business innovation

Cloud computing

Communications

Copyright

Data centers

Digital economy strategy

Economic development Canada

eCommerce

eHealth

eLearning

Enterprise Resource Planning (ERP)

Gadgets

Geo-blocking

Green technology

Investment

Mashups

Mobility

New technologies

Olympic technology

Outsourcing

Project management

Sales and marketing

Security

SMB

Social media

Social networking

Software as a Service (SaaS)

Speakers Corner

Start Up Innovation Campaign

Tech events

Technology law

Technology start-ups

Trends

Unified Communications

Usage based billing

Web 2.0

Wireless


Archives

May 2012

April 2012

March 2012

February 2012

January 2012

December 2011

November 2011

October 2011

September 2011

August 2011

July 2011

June 2011

May 2011

April 2011

March 2011

February 2011

January 2011

December 2010

November 2010

October 2010

September 2010

August 2010

July 2010

June 2010

May 2010

April 2010

March 2010

February 2010

January 2010

September 19, 2011 7:30 AM

Our recent ERP benchmark study (soon-to-be-released) points out the obvious relationship between ERP selection success and ERP implementation success, that is: a failed selection project inevitably results in a failed implementation project.

Now, ruminate on this statistic - a paltry 32% of ERP selection projects succeed. This means that 68% of ERP projects are destined to fail before implementation even starts.

ERP selection failure (and ERP failure in general) can almost always be traced to some avoidable root cause. An organization's task, therefore, is to identify and deal with potential root causes before they cause damage. This is what we call risk management.

Now, although each organization operates within its own unique set of circumstances, certain risk factors act as common threats to ERP selection projects. In this article, I highlight a few of these key threat areas, their potential consequences, and some tactics to manage them.

Risk Category 1: Business Risk
Risk Factor:
An ERP Project That Doesn't Product Positive Value

  • Cause: Pursuit of an ERP project that isn't tied to business goals.
  • Potential Consequences: An expensive, disruptive ERP investment that fails to generate a positive return.
  • Mitigation Tactics: Start the project with an analysis of the organization's strategic objectives, business goals and operational performance. Then, identify the areas in which ERP can help drive value. Only then will an organization be in a position to design a procurement process capable of delivering a value-producing ERP project.
Risk Category 2: Project Management Risk
Risk Factor:
A Runaway ERP Selection Project
  • Cause: Inadequately well-defined project structure and/or ineffective project management.
  • Potential Consequences: Cost overruns, delays, unresponsive proposals.
  • Mitigation Tactics: Clearly define the project plan, schedule, and vendor participation requirements. Use an experienced procurement or project manager. If one isn't available internally, look for external help.
Risk Factor: Unduly Influenced or Biased Process
  • Cause: A potential vendor has influence over the procurement process, the substance of the RFP and/or the list of potential vendor participants.
  • Potential Consequences: The biased process might direct the buyer away from a more well-suited vendor or solution.
  • Mitigation Tactics: Prevent any potential vendor from influencing the procurement process. If outside assistance is required, ensure that the advisor/consultant is fully agnostic and independent from all potential respondents.
Risk Factor: Unresponsive Proposals
  • Causes: An RFP that fails to define the requirements with sufficient particularity. A failure to deliver the RFP to an appropriate set of vendors.
  • Potential Consequences: Vendors may deliver vague, unresponsive, or incomparable proposals.
  • Mitigation Tactics: Buyers should use the RFP process to clearly define their needs. At a minimum, buyers should clarify the business objectives, project scope, specifical functional requirements, specific technical/technological requirements, and specific user requirements. The buyer should also perform a market analysis (including landscape of vendors and solutions used by competitors) to identify potentially well-suited respondents.
Risk Category 3: Evaluations Risk
Risk Factor:
Poor Decision-Making
  • Cause: A poorly defined decision-making process.
  • Potential Consequences: The buyer makes a selection decision based largely on subjective criteria or an alignment with a specific sales person instead of based on a reasoned analysis relative to true business needs. Another potential consequence is that the buyer is incapable of making a decision.
  • Mitigation Tactics: Before assessing alternatives, the buyer should define specific evaluations criteria. The buyer should also define a process for resolving conflicting views and breaking ties.
Risk Category 4: Contractual and Legal Risk
Risk Factor:
Poor Implementation Performance
  • Cause: A contractual relationship that fails to drive ERP implementation success.
  • Potential Consequences: Implementation delays, cost overruns, project failure.
  • Mitigation Tactics: The buyer should consider negotiating terms that incentivize the ERP services vendor to deliver a successful project. For example, it can link payment obligations to the successful completion of key project deliverables.
In summary, there will always be risks that threaten the success of an organization's ERP selection project. I've only highlighted a few of the most common. If your company is starting an ERP selection project or is in the middle of an ERP selection project, it should take a step back and see whether its risks are adequately mitigated.

If you're concerned that your organization might be exposing itself to too much ERP selection risk, give us a call. We would be happy to discuss whether your project might benefit from an ERP selection risk assessment and mitigation plan.


Originally posted on Pemeco's Blog

Blogger Profile: Jonathan Gross
Jonathan manages ERP selection projects drawing upon his experience as a commercial lawyer and his M.B.A. education to help clients select the right-fit ERP systems and negotiate the best deal. He is an industry analyst and advises boards of directors on issues relating to business, strategy and law.

Posted by Sue Ansell at September 19, 2011 7:30 AM

Categories: Enterprise Resource Planning (ERP)

Comments

Name
URL (remove the http://)
Email
Comments (field is limited to 2000 characters)
   

TrackBack Link

Bookmark and Share           Print Page          Email To A Friend
Start Me Up Innovation Campaign winner

WCIT C200 Investment Forum


Insightful business speaker Jim Harris talks innovation in 
Speaker's Corner 

Backbone magazine Speakers' Corner 

Backbone magazine latest digital issue

Backbone's Cloud Portal

Backbone's Digital Economy Acceleration Committee

Backbonemag on Twitter