Abstract

The success rate of enterprise resource planning (ERP) implementation is less than 49% around the world owing to its complex nature. The key focus of information system (IS) researchers has been to explore the ways to reduce threats to ERP implementation posed especially by user resistance. Although the reasons for user resistance have already been dealt with in previous studies, our understanding of how users assess a new ERP system in the pre-implementation phase and what prompts their decision to resist it is far from complete. In particular, an explanation for user resistance or end-user grumbling from the perspectives of status quo bias and technostress was found to be missing. In order to fill this gap in research, the model proposed in the present study integrates status quo and technostress, thus throwing light on the end-user grumbling behaviour that precedes the implementation of a new ERP system. Data was collected via a survey questionnaire distributed to 221 respondents from five different manufacturing industries in Bangladesh which are currently in the process of installing the popular SAP ERP system. Results of this tested model indicate a significant impact of the constructs of status quo bias and technostress on end-user grumbling. Additionally, end user grumbling has positive significant impact on symbolic adoption. Moreover, the paper discusses common method bias and the limitations of the study, while providing an outlook for future research.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.