ERP project risks
ERP project risks are uncertain events or conditions that, if they occur, can affect project objectives (scope, schedule, budget, quality). Effective risk management – identification, analysis, and mitigation – is essential for success. This article covers common risks, risk assessment frameworks, and links to project governance, change management, and hidden costs.
1. Why risk management matters
ERP projects have a high failure rate. Studies show:
- 50-60% of ERP projects exceed budget.
- 60-70% experience significant delays.
- Many fail to deliver expected benefits.
Proactive risk management helps avoid surprises, enables informed decisions, and increases chances of success.
2. Common ERP project risks
| Risk category | Specific risks |
|---|---|
| Scope & requirements | Scope creep, unclear requirements, gold‑plating, changing business needs |
| Data | Poor data quality, data migration failures, data loss, mapping errors |
| People & change | Resistance to change, inadequate training, loss of key staff, low adoption |
| Vendor & technology | Vendor viability, software bugs, integration complexity, customisation risks |
| Project management | Unrealistic timelines, poor governance, resource shortages, communication gaps |
| Financial | Budget overruns, hidden costs, currency fluctuations, ROI shortfall |
3. Risk assessment matrix
Risks are assessed by probability and impact. The matrix helps prioritize:
Red cells require immediate mitigation; yellow need plans; green can be monitored.
4. Risk register
A risk register is the central tool. Typical fields:
| ID | Risk description | Probability | Impact | Score | Owner | Mitigation | Status |
|---|---|---|---|---|---|---|---|
| R001 | Key data migration expert leaves | Med | High | High | PM | Cross-train backup | Active |
| R002 | Scope creep in finance module | High | Med | High | Sponsor | Strict change control | Mitigated |
Review the register monthly at steering committee.
5. Mitigation strategies
- Avoid: Change scope to eliminate risk.
- Transfer: Move risk to vendor (fixed-price, insurance).
- Mitigate: Reduce probability/impact (e.g., extra testing).
- Accept: Acknowledge and have contingency.
6. Risk governance
Risk management is integrated with project governance:
- Steering committee: Reviews top risks, approves mitigation budgets.
- Project manager: Owns risk process, updates register.
- Risk owners: Assigned to each risk.
- Escalation: Clear path for emerging risks.
7. Real-world examples
8. Common pitfalls
- No formal risk process: Risks are managed reactively.
- Risk register not updated: Becomes a shelf‑ware document.
- Ignoring people risks: Focus only on technical risks.
- No contingency budget: When risks materialize, no funds.
- Risk owners not assigned: No accountability.
Key Takeaways
- Common risks: scope creep, data migration, resistance, vendor issues.
- Use a risk matrix (probability vs impact) to prioritize.
- Maintain a living risk register with owners and mitigation plans.
- Integrate risk management with project governance.
- Include contingency budget (15-25%) for materialized risks.
When should risk management start? At project initiation – during planning and vendor selection.
Who should be involved in risk identification? Whole team: project team, stakeholders, vendors, and sometimes external experts.
What is a residual risk? Risk that remains after mitigation. Some residual risk is acceptable.
Continue Reading in ERPEDIA
For structured, vendor‑neutral ERP advisory → Speak with an independent ERP advisor.