Information technology failure is one in which stakeholders are left dissatisfied with how the system has served their interests (Chua, 2009; Sauer, 1993). The Standish Group (1994) defines ERP failure as one in which the project was canceled, over budget, missed time delivery, and/or did not meet stated business goals.
Wong, Scarbrough, Chau, and Davison (2005) describe how failure refers to ERP system downtime, fully functional, loss of sales, lost market share or lost competitive advantage. Wong, Scarbrough, Chau, and Davison (2005) further note that often ERP failure is identified in which the project approval phase objectives and goals have not realized sufficient or expected return on investment.
The key is keeping the definition and measurement of failure, or success, as objective as possible. The organization needs to spend the time and effort to formally document and agree on how failure, and success, will be defined. Without a formal process in which failure/success is formally documented and communicated, the idea of failure or success can become quite subjective and mean many things across the stakeholder groups and their members.
Moreover, the organization needs to allow some time to fully realize the benefits and value of ERP assimilation. Ghosh (2018) notes that stakeholders should allow time before considering ERP as a failure as it takes months to years to realize the return and benefits of ERP.