Damage Control in ERP Implementations
More than 60% of ERP implementations exceed budget and over 70% miss their initial go-live date. When a project stalls, independent damage control can get it back on track.
Most stalled ERP projects can be saved, provided there is willingness to reassess scope and conduct an independent assessment. Early intervention significantly limits the damage.
Frequently Asked Questions
When does an ERP project need damage control?
When it significantly lags behind schedule, threatens to exceed budget, key users lose confidence, or vendor and client are no longer aligned.
What are the first steps?
Stop, analyze, restart. Independent assessment of the situation. Then redefine scope, recalibrate expectations and create a realistic plan.
Can a stalled project be saved?
In most cases yes, if there is willingness to honestly examine root causes. This sometimes means: reducing scope, adjusting the team or addressing the vendor.