scholarly journals Using innovative approaches when analyzing information systems IS failure stories

Author(s):  
LYNETTE DREVIN
Author(s):  
Chung Kim ◽  
Dane Peterson ◽  
Jerry Chin ◽  
Tonya Barrier

Despite enormous progress in the methodologies and technologies used in the development and implementation of Information Systems (IS), IS failure continues to plague the efforts of many companies. According to a recent report, up to 90 percent of all IS projects fail to achieve their goals, 80 percent are late and over-budget, and 40 percent are abandoned (Clegg et al., 1997). Since information systems are becoming increasing critical for the strategic operations of organizations, the high rate of failure for IS projects is of great concern to both organizational management and IS professionals. Developing and implementing successful international IS have proven to be even more difficult due to such factors as the diversity and disagreement among the participants (Mantelaers & Van Den Berg, 2000). However, with an increasing number of firms expanding into international markets, the need to develop and implement IS which cross national boundaries and span diverse cultures is rapidly growing (Palvia, 1998). Adding to the importance of developing successful international IS is the realization that they constitute an essential tool for assisting organizations in coping with the increased competition associated with global markets. Thus, there is an urgent need to acquire knowledge about whether the factors found to be critical for developing successful IS in one country are also applicable to developing international IS involving countries with different cultural norms.


Author(s):  
Jeremy Fowler

Although the discipline of information systems (IS) development is well established, IS failure and abandonment remains widespread. As a result, a considerable amount of IS research literature has investigated, among other things, the factors associated with IS success and failure. However, little attention has been given to any possible relationships that exist among the uncovered factors. In an attempt to address this, we examine the development of a successful IS, and compare the factors associated with its success against the factors most reported in our review of the literature as being associated with IS failure. This may be an important area of study given, for example, project management practices may be affected by knowing whether success and failure are two sides of one coin, or different in nature. The results of our exploratory study showed that four of the six factors associated with the success of the investigated IS were related to the factors identified from our review of the literature as being associated with IS failure.


Author(s):  
Simon McGinnes

Success models often treat Information Systems (IS) as static. Yet most IS evolve continuously, and most development effort occurs during the so-called maintenance phase. For an IS to succeed, its evolutionary process must also remain successful. Unfortunately many IS projects fail, particularly when outsourced. This chapter argues that the practice of managing IS work in project form may itself be implicated in IS failure. The project model is critically examined, identifying mismatches with the reality of IS work as a component of business change. The results suggest that merely trying harder to make projects succeed may be ineffective. An alternative framework for “steady state” development is proposed, which characterises IS work as evolutionary and inseparable from its context of business change, providing a blueprint for IS development without the need for projects, and offering improved chances of success when “big bang” project management would otherwise be the only option.


2013 ◽  
pp. 279-298
Author(s):  
Simon McGinnes

Success models often treat Information Systems (IS) as static. Yet most IS evolve continuously, and most development effort occurs during the so-called maintenance phase. For an IS to succeed, its evolutionary process must also remain successful. Unfortunately many IS projects fail, particularly when outsourced. This chapter argues that the practice of managing IS work in project form may itself be implicated in IS failure. The project model is critically examined, identifying mismatches with the reality of IS work as a component of business change. The results suggest that merely trying harder to make projects succeed may be ineffective. An alternative framework for “steady state” development is proposed, which characterises IS work as evolutionary and inseparable from its context of business change, providing a blueprint for IS development without the need for projects, and offering improved chances of success when “big bang” project management would otherwise be the only option.


2017 ◽  
Vol 15 (2) ◽  
pp. 31-47 ◽  
Author(s):  
Pierluigi Zerbino ◽  
Davide Aloini ◽  
Riccardo Dulmin ◽  
Valeria Mininno

To the best of our knowledge, extant definitions of Enterprise Resource Planning (ERP) success are not comprehensive, and they do not address all of the most relevant dimensions of this complex issue. Consequently, current ERP success models may lead to deceptive evaluations. Through a rigorous logical shift starting from IS failure, and diverging from classical project management approaches, this paper attempts to define ERP success by means of four factors: Process, Correspondence, Interaction, and Expectation. Results formally integrates the literature gaps and enable the future definition of appropriate measurement items that could steer management practices towards a sounder approach to ERP success.


2018 ◽  
Vol 6 (1) ◽  
pp. 159-186
Author(s):  
Chris Powell

There may be a disconnect between technology as-created and as-used that could lie at the foundation of frequent failure in cost, schedule, and/or performance of Information Technology/Information Systems (IT/IS). This can perhaps be reconciled through a focus on the socially constructed and emergent nature of IT as it enters and is used by an organization. A structured and facilitated dialog technique, by focusing on properly perceiving human felt needs in addition to technological aims, may improve the process of technology realization. This paper starts with an analysis of IT/IS failure factors using case studies. Then, a theoretical framework is derived to attempt to address the systemic failure factors. This is then made practical by creating a conceptual decision framework for management to use in framing complex investment decisions including IT/IS. The framework elements achieve an organizational epistemology, or knowledge framework, that can potentially facilitate more accurate acquisition and development of the system-as-created, and perhaps lay the foundation for subsequent transition into a system-as-used that an organization can use in the manner needed and intended. In addition, this epistemology may underlie the process and products of successful IT/IS architecture.


2008 ◽  
pp. 195-210
Author(s):  
Jeremy J. Fowler ◽  
Pat Horan

Although the discipline of information systems (IS) development is well established, systems’ failure, abandonment, and dissatisfaction with functioning systems remain widespread. This has generated a considerable amount of literature investigating the factors seen to contribute to IS success and failure. However, little attention has been given to the possible relationships among the factors most influential in IS success and failure. Therefore, we examine the development of a successful system and compare the factors associated with the system’s success against the factors most reported in the literature as being associated with systems’ failure. Project management practices may be affected by knowing whether success and failure are two sides of one coin or different in nature. The results of our exploratory study showed that four of the six factors identified by the participants in our chosen system as being the most influential in the success of the system were directly related to the factors identified from the literature as being most associated with IS failure. Although more research needs to take place, these results would suggest a considerable relationship might exist between IS success and failure factors.


Author(s):  
Frank Stowell

In this chapter I raise questions about the nature of Information systems, the way that they are designed and developed and suggest areas that IS researchers may wish to investigate. A concern is raised about the way we think about the domain of information systems and a suggestion made that rather than think of it in terms of the mnemonic IS, with is association with IT, it should be thought of in terms of as systems of information. This suggestion is made as a means of highlighting considerations developers have to take into account which go beyond those of technology alone. As a means of instigating this proposition four questions are raised in the chapter which are intended to stimulate further information systems research. These questions are about the nature of IS, design Methods, the underpinning philosophy and finally, IS failure.


Author(s):  
Brian Dempsey ◽  
Joe McDonagh

This chapter examines the integration of process inquiry and the case method in the study of Information Systems (IS) failure. Having acknowledged the prevalence of IS failure and the need for continued inquiry in this domain, the two predominant methods of inquiry, factor and process studies, are described along with the utility of both methods. The chapter then examines the nature of process inquiry and notes its utility and prevalence in the study of IS phenomena, and its potential applicability for inquiry into IS failure. The case study method is then briefly described along with its potential contribution when combined with process inquiry. The chapter then describes how the case method can provide an overall framework for the conduct of a process inquiry and presents an iterative six-stage research process model based on the case method to assist with the planning, design, preparation, data collection, data analysis, and reporting of findings.


Sign in / Sign up

Export Citation Format

Share Document