Managing top management support in complex information systems projects

Abstract

Purpose Top management support (TMS) is considered as a critical factor for the success of information systems (ISs) projects. The literature shows that TMS has a positive impact on achieving success in ISs’ projects in different aspects. However, the enabling factors for TMS in complex ISs’ projects have barely been tested, something which this study aims to rectify. Design/methodology/approach This study has designed a research model based on structural equation modelling (SEM) with the intention of analysing the perception of IS end users regarding the effect on TMS of the following factors: technological complexity and training and organizational communication. The application of the study has focused on an enterprise resource planning–open source software (ERP-OSS) environment. Findings The findings show how end users have a perception that organizational communication and training have a positive relation with TMS. Based on these findings, the authors have suggested several practical considerations. Research limitations/implications There are two limitations to this study. First, this study is based on the perception of complex IS/IT users. It would be interesting to add the perception of top managers to provide more solid findings. The second limitation is that this study has not suggested any additional potential factors which could affect TMS. Practical implications First, this article provides a study of the key role of TMS when an organization needs to implement a complex IS/IT. Second, organizations must develop mechanisms for increasing training and communication relating to the new complex IS/IT projects. Finally, the complexity of an IS/IT project does not constitute an enabling factor incentivizing TMS and should therefore not be a determining factor in increasing TMS within an organization selecting an IS/IT. Originality/value This study contributes to advancing theory in the field of TMS in information systems projects.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 13 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.