0
Why do ERP, HRMS and CRM
implementations fail so often?
And tips to avoid them…
The usual suspects …
Bad
product fit

Vendor
inflexibility

Poor change
management

Under
estimated
budgets

Poor senior
m...
But lets dig deeper…

Some deeper ‘insights’ into the nature
of Enterprise Software Products
will uncover the root reasons...
Insight #1 : It’s a transformation, not a
software installation
Would you change any regular process without
a) Verificati...
Insight #2 : Identify the generic
processes
Generic processes the same for everyone in your industry,
or even your country...
Insight #3 : Identify your unique
operational processes
At the surface, unique operational processes may be
seem the same ...
Insight #4 : Identify the fatal flaws
A fatal flaw is a gap in the product that cannot be fixed
by the vendor because the ...
Insight # 5 : Understand what is under
the hood
Most enterprise products have millions of lines of spaghetti
like lines of...
Insight # 6 : Prepare for life cycle usage

What happens after the implementation is done?
How will the product be support...
Brought to you after hundreds of person years of
Enterprise product building and
implementation experience by

www.KallosS...
Upcoming SlideShare
Loading in...5
×

Why do ERP, HRMS and CRM implementations fail so often?

340

Published on

Root cause reasons based on real experience. A must read for anyone implementing an enterprise product suite

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
340
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Why do ERP, HRMS and CRM implementations fail so often?"

  1. 1. Why do ERP, HRMS and CRM implementations fail so often? And tips to avoid them…
  2. 2. The usual suspects … Bad product fit Vendor inflexibility Poor change management Under estimated budgets Poor senior management support Incapable implementati on team Bad product quality
  3. 3. But lets dig deeper… Some deeper ‘insights’ into the nature of Enterprise Software Products will uncover the root reasons why decision makers take wrong approaches
  4. 4. Insight #1 : It’s a transformation, not a software installation Would you change any regular process without a) Verification that it is the right change b) Concurrence of the users who are impacted c) 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.
  5. 5. 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 Sales Pipeline Human Resources 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
  6. 6. Insight #3 : Identify your unique operational processes At the surface, unique operational processes may be seem the same as everyone in your industry, but it may not be .. Supply Chain Work Force Mgmt. Social Media Initiatives Sales Compensation Action: Insist on getting the software to match your process, if required with a change. Eliminate vendors who are not able to
  7. 7. 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 Retrospective Pay N – Level Reporting Action: Make your checklist of must-have capability. If the vendor cannot provide it via a change or a non – intrusive customization, eliminate them
  8. 8. 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 the change will affect the ability to get upgrades of the product later. If the answer is no, watch out
  9. 9. 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. Otherwise set up a water tight support arrangement – your business depends on it.
  10. 10. Brought to you after hundreds of person years of Enterprise product building and implementation experience by www.KallosSolutions.com www.KServeERP.com www.KServeHRMS.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×