Cloud ERP implementations can be disastrous. Some implementation problems are so common that they are easy to anticipate and avoid.
Identifying and addressing these issues early on and closely monitoring the entire process can help ensure smooth cloud ERP implementations and avoid future problems.
These are common ERP implementation problems and the ways you can address them.
1. Identifying risks promptly
Early detection of risks is key to ensuring that they are tracked down and addressed. However, many implementation teams fail to do this. This can help reduce future problems. While some teams keep track of the risks but don't review it regularly to make sure they are resolved or on the right path to resolution, others fail to adequately address the risks.
These known risks can cause the ERP launch to be delayed and could demoralize the team that worked so hard to make the project a success.
2. Gathering the requirements in the correct way
Document requirements and have stakeholders review them. The following are common issues that could impact requirements:
These requirements are too complex and it is hard to hold the vendor or partner responsible if they are not met.
The requirements are incomplete because key stakeholders were not included in the requirements-gathering process. Subject matter experts might be too focused on the needs of their department or team. A finance employee might not have enough knowledge about accounts payable (AP), for example, to properly document AP's requirements. Think about the voices that are represented in this group.
Information about the vendor and implementation partner is outdated and does not reflect the future functionality of the ERP system.
These requirements should be met the first time. It is possible to make changes later, which could lead to significant financial losses. Make sure you have enough time to review the requirements once the team has completed their templates.
3. Understanding the policies regarding change requests
It is hard to avoid change requests entirely, but documenting and reviewing the requirements will help lower future unplanned costs. Before signing any contract, make sure you have a clear process for change requests. They can cause major delays and strain on the budget.
Partner fees may include the costs of the request, as well as the investigation and building of the change request. You will likely find details about changes in your contract. These details may also be found in the vendor's or implementation partner's supplemental documentation.
4. Project schedule issues to be anticipated
Before committing to a schedule, review the schedule with key stakeholders. It can be difficult and costly to move from the go-live date. The implementation partner will need to continue resources for the project beyond the scheduled go-live.
Avoid scheduling a go-live or other critical milestones around holidays observed by countries, such as the end of December or national independence days. There are many important holidays. People also enjoy extended vacations in the summer. Project leaders and their teams should plan around different vacation and holiday practices.
5. Being proactive in securing backup resources
A member of the key project team might need to be absent for extended periods due to illness, personal reasons, or unforeseeable circumstances. Make sure you budget for a backup resource. Make sure your implementation partner has backup plans for important resources.
6. Creating true change management strategies
Some employees may be excited to use a new ERP system. Some workers, or vendors, may not like the idea of change and prefers to keep using the current system. Although most people will use the new ERP software after go-live, they will also be more likely to trust it.