Why do ERP, HRMS and CRMimplementations fail so often?

And tips to avoid them…

The usual suspects …

Bad product fit

Poor change management Incapable

implementation team

Vendor inflexibility

Under estimated budgets

Bad product quality

Poor senior management

support

But lets dig deeper…

Some deeper ‘insights’ into the natureof Enterprise Software Products

will uncover the root reasons why decision makers take wrong approaches

Insight #1 : It’s a transformation, not a software installation

Would you change any regular process without

a) Verification that it is the right changeb) Concurrence of the users who are impactedc) Evaluate its benefits

In an Enterprise suite implementation, it’s a Process change tsunami..

Action Point: Manage the whole transformation, not just the Software purchase and installation.

Staff up, and budget for this.

Insight #2 : Identify the generic processes

Generic processes the same for everyone in your industry,or even your country and possibly globally

Financial Accounting

Payroll

Human Resources

Sales Pipeline

Action: Evaluate the best product for your budget.Prepare your team to change their processes to the products

processes and don’t ask for changes unless critical

Insight #3 : Identify your unique operational processes

At the surface, unique operational processes may beseem the same as everyone in your industry,

but it may not be ..

Supply ChainWork Force

Mgmt.

Sales Compensat-

ion

Social Media Initiatives

Action: Insist on getting the software to match your process, if required with a change. Eliminate vendors

who are not able to

Insight #4 : Identify the fatal flaws

A fatal flaw is a gap in the product that cannot be fixed by the vendor because the change with have massive

negative impact on the product

Multi-Level data security

Multi-currency

N – Level Reporting

Retrospective Pay

Action: Make your checklist of must-have capability.If the vendor cannot provide it via a change or a

non – intrusive customization, eliminate them

Insight # 5 : Understand what is under the hood

Most enterprise products have millions of lines of spaghetti like lines of code, which are very difficult to change unless

architected for it

Action: When you need a change, ask the vendor if thechange will affect the ability to get upgrades of the product

later. If the answer is no, watch out

Insight # 6 : Prepare for life cycle usage

What happens after the implementation is done? How will the product be supported for ongoing changes?

Action: If you are plan to do it in-house, look for tools that can change business rules, add new fields, upload data, build new reports, set up more alerts, set up more mail triggers,

and obtain automatic upgrades to versions. Otherwiseset up a water tight support arrangement – your business

depends on it.

www.KallosSolutions.com

Brought to you after hundreds of person years of Enterprise product building and implementation experience by

www.KServeERP.com

www.KServeHRMS.com