critical success factors revisited: success and failure cases of information systems for senior...

26
Ž . Decision Support Systems 30 2001 393–418 www.elsevier.comrlocaterdsw Critical success factors revisited: success and failure cases of information systems for senior executives PoPo Poon ) , Christian Wagner 1 Department of Information Systems, City UniÕersity of Hong Kong, 83 Tat Chee AÕenue, Hong Kong, People’s Republic of China Accepted 1 April 2000 Abstract Ž . The literature suggests the existence of critical success factors CSFs for the development of information systems that support senior executives. Our study of six organizations gives evidence for this notion of CSFs. The study further shows an interesting pattern, namely that companies either Aget it rightB, and essentially succeed on all CSFs, or Aget it completely wrongB, that is, fall short on each of the CSFs. Among the six cases for which data were collected through in-depth interviews with company executives, three organizations seemed to manage all the CSFs properly, while two others managed all CSFs poorly. Only one organization showed a mixed scorecard, managing some factors well and some not so well. At the completion of the study, this organization could neither be judged as a success, nor as a failure. This dichotomy between success and failure cases suggests the existence of an even smaller set of Ameta-successB factors. Based on our findings, we speculate that these Ameta-successB factors are AchampionshipB, Aavailability of resourcesB, and Alink to organization objectivesB. q 2001 Elsevier Science B.V. All rights reserved. Keywords: Executive information systems; Critical success factors; Critical failure factors; Information systems success; Case study 1. Background The successful development of information sys- tems for senior executives is not easy for any organi- zation. Information systems to support senior execu- tives have been available for well over a decade, Ž . initially as Aexecutive information systemsB EIS , and today more frequently as EIS components of Ž enterprise resource planning software such as . Ž . SAPrR3 , on-line analytic processing OLAP soft- ) Corresponding author. Tel.: q 852-2788-9959. Ž . E-mail addresses: [email protected] P. Poon , Ž . [email protected] C. Wagner . 1 Tel.: q 852-2788-7546. ware, or data warehouse access software. EIS and their derivatives have always been high-risk systems, offering usually only one chance to successfully implement them in the organization. Consequently, w x many failures have occurred 5,14 , with estimates being as high as 70%. Technological, organizational, psychological and educational issues all contribute to making the implementation of such systems difficult w x 20,21 . In addition, although EIS and their successors are supposedly specifically tailored to top executives’ information needs, few executives made significant wx direct use of them. Fitzgerald and Murphy 9 found that only 32% of users were at executive level. Furthermore, the majority of executives did not rate Ž . EIS benefits very highly. The majority 68% of 0167-9236r01r$ - see front matter q 2001 Elsevier Science B.V. All rights reserved. Ž . PII: S0167-9236 00 00069-5

Upload: popo-poon

Post on 15-Sep-2016

217 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: Critical success factors revisited: success and failure cases of information systems for senior executives

Ž .Decision Support Systems 30 2001 393–418www.elsevier.comrlocaterdsw

Critical success factors revisited: success and failure cases ofinformation systems for senior executives

PoPo Poon), Christian Wagner 1

Department of Information Systems, City UniÕersity of Hong Kong, 83 Tat Chee AÕenue, Hong Kong, People’s Republic of China

Accepted 1 April 2000

Abstract

Ž .The literature suggests the existence of critical success factors CSFs for the development of information systems thatsupport senior executives. Our study of six organizations gives evidence for this notion of CSFs. The study further shows aninteresting pattern, namely that companies either Aget it rightB, and essentially succeed on all CSFs, or Aget it completelywrongB, that is, fall short on each of the CSFs. Among the six cases for which data were collected through in-depthinterviews with company executives, three organizations seemed to manage all the CSFs properly, while two others managedall CSFs poorly. Only one organization showed a mixed scorecard, managing some factors well and some not so well. At thecompletion of the study, this organization could neither be judged as a success, nor as a failure. This dichotomy betweensuccess and failure cases suggests the existence of an even smaller set of Ameta-successB factors. Based on our findings, wespeculate that these Ameta-successB factors are AchampionshipB, Aavailability of resourcesB, and Alink to organizationobjectivesB. q 2001 Elsevier Science B.V. All rights reserved.

Keywords: Executive information systems; Critical success factors; Critical failure factors; Information systems success; Case study

1. Background

The successful development of information sys-tems for senior executives is not easy for any organi-zation. Information systems to support senior execu-tives have been available for well over a decade,

Ž .initially as Aexecutive information systemsB EIS ,and today more frequently as EIS components of

Ženterprise resource planning software such as. Ž .SAPrR3 , on-line analytic processing OLAP soft-

) Corresponding author. Tel.: q852-2788-9959.Ž .E-mail addresses: [email protected] P. Poon ,

Ž [email protected] C. Wagner .1 Tel.: q852-2788-7546.

ware, or data warehouse access software. EIS andtheir derivatives have always been high-risk systems,offering usually only one chance to successfullyimplement them in the organization. Consequently,

w xmany failures have occurred 5,14 , with estimatesbeing as high as 70%. Technological, organizational,psychological and educational issues all contribute tomaking the implementation of such systems difficultw x20,21 .

In addition, although EIS and their successors aresupposedly specifically tailored to top executives’information needs, few executives made significant

w xdirect use of them. Fitzgerald and Murphy 9 foundthat only 32% of users were at executive level.Furthermore, the majority of executives did not rate

Ž .EIS benefits very highly. The majority 68% of

0167-9236r01r$ - see front matter q 2001 Elsevier Science B.V. All rights reserved.Ž .PII: S0167-9236 00 00069-5

Page 2: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418394

users was at middle management level. These middlemanagers were not using the systems on behalf ofexecutives but for their own information needs. Nord

w xand Nord 18 confirmed that vice-presidents andmiddle managers exhibited higher system usage thantop executives.

Taken together, these facts illustrate that imple-mentation success cannot be taken for granted, andthat even successful implementations might not beused as intended. Furthermore, critical success orfailure factors applicable to other types of informa-tion systems may not necessarily apply to informa-

Žtion systems for executives compare for instancew x.critical failure factors in Flowers 10 . Hence, as

EIS and their derivatives are offered by an increasingnumber of vendors and supposedly used by more andmore organizations, understanding the determinantsfor their successful implementation and use becomesincreasingly important. Interestingly enough, littleresearch has been carried out concerning this subject

w xmatter. Although Rockart and DeLong 22 proposedŽ .a model of critical success factors CSFs for EIS

over 10 years ago, little additional research of thecore concepts and theoretical foundations was con-

w xducted in subsequent years 27 . The few studies thatŽ w x.followed e.g., Turban 25 , largely confirmed

Rockart and DeLong’s factors through one or morecases.

Hence, to date, it has yet not been determined ifthe CSFs are universal in their application to differ-ent organizations, business environments and culture,or if they are an artifact of prevailing company andcountry cultures. A recent article by Bensaou and

w xEarl 3 for instance hints at interesting differencesbetween Western and Japanese IT management, withrespect to the ways in which requirements should bedetermined or success should be measured. To shedmore light on the critical link between CSFs andsystem success, six cases of information systems forsenior executives from organizations in Hong Kongwere analyzed over a time frame of 18 months.

Ž .Some of the systems were new 2 years or less ,whereas others had been in use for up to 6 years. Theorganizations chosen represent a number of differentindustries ranging from education, hospital, shipping,electric supplies, to railways and airways. Withineach organization, several members were inter-viewed, to assess success from several perspectives.

The article is organized as follows. We will nextbriefly describe the meaning of system success andsuccess characteristics. This will be followed by areview of CSFs and the selection of CSFs to befurther considered within this study. We will thendiscuss research methodology, followed by results,and discussion. The manuscript ends with conclu-sions and suggestions for future research.

2. System success

ŽIt has been known for a long time that EIS and.their derivatives are usually developed with high

w xexpectations, yet often end in failure 21,30 . So howcan we define system success? Unfortunately, sys-tems that support decision making are difficult orimpossible to justify using standard economic evalu-

w xation methods. Keen 12 showed that defining andquantifying the benefits of a decision support systemis very difficult. While the cost of an EIS can beestimated, putting a dollar value on the benefits isdifficult since the benefits of EIS can be intangible

w xand transient 22 . Nevertheless, Rockart and De-Long suggested that there is a hierarchy of fourissues to consider when evaluating an EIS. In addi-tion, other researchers, such as Cottrell and Rapleyw x w x6 or Rainer and Watson 21 have put forwardadditional criteria that can be used to determine EISsuccess. Based on their combined suggestions, wechose five evaluation criteria, which are introducedbelow together with the explanation for their choice.

2.1. Access: the EIS is made aÕailable and users aregiÕen access to the system

It is obvious that if the development team cannotmake the system available to users, the users cannotaccess the system and the system, in this case, thesystem is unsuccessful. Even a seemingly availablesystem can be difficult to access, if it requires com-plicated log-in procedures, or access from only a fewdedicated terminals.

2.2. Use: the EIS is used by the intended users

It is logical that if the system ceases to be used, itcannot provide any benefit to users and then cannot

Page 3: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 395

be seen as successful. Therefore, there is a need toensure that the EIS is actually used by its potential

w xusers. As Rockart and DeLong 22 mentioned, howmuch time executives spend using the system canindicate the success of the EIS. Moreover, Leidner

w xand Elam 13 realized that the frequency with whichsystem is used is also one of the factors that reflectthe success of EIS.

2.3. Satisfaction: users are satisfied with the EIS

User satisfaction is one of the most widely usedindicators of success in information system researchw x15 . The level of users’ satisfaction will also havedirect impact on whether or not the system is usedw x2 . So, if the EIS cannot satisfy its users, the userswill not use the system anymore. As a result, thesystem will not be successful.

2.4. PositiÕe impact: the EIS has positiÕe impact onthe executiÕes and the organization

An EIS is successful if it has a beneficial impacton the executives and organization. As indicated by

w xRockart and DeLong 22 , a successful EIS canimprove the manager’s mental model of the com-

w xpany and Mintzberg 16 proposed that better deci-sions result from better mental models. Once theexecutives can make better decisions, a positive im-pact on the organization is obtained.

2.5. Diffusion: the EIS tends to spread

Another feature to indicate successful EIS is thatthe number of people using the system increasesafter the initial users have tried to use the systemw x22,29 . Once the non-users perceive the system canprovide benefits to them, they may request access tothe system. In addition, once EIS users found thattheir colleagues gain positive impact from the sys-tem, they may promote the system to other col-leagues. As a result, the number of EIS users will

w xsteadily rise. Santosus 23 describes this phe-nomenon for a successful EIS implementation atMotorola, where success meant an increase in thenumber of users, applications, and platforms through

Ž .which the EIS was delivered spread and growth .

Absent from our success criteria list are factorsthat refer to implementation issues. Of course, themost basic level of success for any EIS is whether itis completed in the first place vs. its remaining inanalysis design or prototyping stages. In fact, severalfailure cases in our study failed early, never gettingbeyond the prototyping stage.

3. CSFs reviewed

In the previous section, we introduced successŽcriteria, the measures of success for systems and

.operationalizations of our dependent variable . Ourfocus will now move to what is frequently calledAcritical success factorsB, namely the conditions thatneed to be met to assure success of the system. Inother words, they are operationalizations of our inde-pendent variable.

The most comprehensive investigation of successfactors for EIS implementation is still the work by

w xRockart and DeLong in 1988 22 . Prior to it, therewas no clear agreement on the factors that are mostsignificant in making the implementation processsuccessful or to identify the best development pro-

w xcess to follow. Rockart and DeLong 22 observed 30cases, where attempts were made to implement EIS.From these, they extracted eight areas that appearedto be the most important to EIS success. Both execu-tive users and developers also deemed all eightfactors most important.

Ž w xSeveral other researchers Paller and Laska 19 ,w x w x w xBird 4 , Watson et al. 30 , Whymark 31 , Rainer

w x w x w x.and Watson 21 , Turban 25 , McBride 14 havesubsequently reconfirmed the factors observed byRockart and DeLong. Follow-up research has shownconsiderable agreement on two additional factors.Each of the factors is described below in some detail.

3.1. Committed and informed executiÕe sponsor

Most studies recognize the importance of an exec-utive sponsor who is both sufficiently committed tothe system to invest time and effort in guiding itsdevelopment, and has a realistic understanding of thecapabilities and limitations of the system. A detaileddiscussion of the importance of commitment and

Page 4: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418396

factors influencing commitment for IS projects canw xbe found in Newman and Sabherwal 17 .

3.2. Operating sponsor

To leverage the time of the executive sponsor, itis necessary to have an operating sponsor designatedto manage the details of implementation from theuser’s side. This sponsor should be well acquaintedwith the executive sponsor’s way of working.

3.3. Appropriate IS staff

The quality of the staff that support an IS forsenior executives is important. The project managershould have technical as well as business knowledge,and the ability to communicate with senior manage-ment. Support staff must be sophisticated enough tointeract with top management and be able to masterthe technologies required for the system.

3.4. Appropriate technology

The choice of hardware and software has a majorbearing on the acceptance of a system. In the past, abarrier to executive support was the lack of hardwareand software that fit with the demands of highlyvariable work styles and environments of executives.As more specifically designed products have becomeavailable, this problem has diminished. Developmentis now often replaced by selecting the most appropri-ate system on the market.

3.5. Management of data

The ability to provide access to reliable data fromboth internal and external sources, is a major issue inthe system development. Aggregating, accessing andextracting data from a number of subsidiary databasescan be a stumbling block to the implementation of anIS suitable for executives.

3.6. Clear link to business objectiÕes

The system must solve a defined business prob-lem or meet a need that can be addressed effectivelywith IS technology. There should be a clear link to

business objectives and clear benefits in using thetechnology. The system must provide something thatwould not otherwise be available and add value tothe data.

3.7. Management of organizational resistance

Political resistance is a common cause of imple-mentation failure. Because an IS for executives canalter the information flow in an organization andshift the power relationships within a company, theremay be resistance to its introduction and operation.Handling of this potential conflict source will remainan issue throughout the life of the system. Dragoonw x8 , for instance reports on the case of Eli Lilly,where a AstandardizedB EIS needed to be imple-mented against the resistance of individual groupswho insisted on keeping their own data collectiontechniques.

3.8. Management of system eÕolution and spread

An installation that is successful and used regu-larly by the executive sponsor will almost inevitablyproduce demand by peers or subordinates for accessto a similar system. Managing this process ofAspreadB means identifying the specific job function,technical orientation, work style, and specific infor-mation support needs of each potential user, andtaking that into account when expanding the system.

3.9. EÕolutionary deÕelopment methodology

An evolutionary development methodology iswidely acknowledged as a key factor for system

w xsuccess 11,22 . The most common way of findinghow the technology can provide value for the execu-

w xtive is through prototyping 22 . This also keeps theexecutives aware and hopefully enthusiastic concern-

w xing the project 1 .

3.10. Carefully defined information and system re-quirements

A key design issue is identifying the executivew xuser’s information requirements 28 . A successful

system can only be delivered when the executives’

Page 5: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 397

needs are understood. Getting executives to specifywhat they want is not an easy task. Paller and Laskaw x w x19 and Bird 4 also pointed out that identifyingexecutives’ information requirements was the biggestchallenge faced by the development team. Vanden-

w xbosch and Huff 26 identified differences in execu-tive information needs based on different informa-

w xtion search behavior. And Davenport 7 points outthat even experienced IS consulting firms may find itdifficult to identify executive information needs.

In order to investigate the CSFs involved in im-plementing an EIS in Hong Kong, all 10 factors wereused to predict the success of EIS development inthis research.

4. Methodology

4.1. Research model

Using the above defined concepts of EIS successand CSFs, the study considered a basic EIS successmodel, as illustrated in Fig. 1. The model postulatesthat the presence of the 10 CSFs would result in the

Žsuccess of the information system as measured by.the five success factors , while the absence of the

CSFs would lead to failure of the project. This is astrong interpretation of the CSF concept, treating theCSFs as both necessary and sufficient conditions forsystem success.

Thus, we expected that organizations that did notmanage all CSFs right would incur project failure, orat least a project outcome below company expecta-

Ž .tion Anon-successB .

4.2. Research sites

To assess the importance of the 10 previouslyidentified CSFs, we studied six Hong Kong organiza-

Fig. 1. Research model.

tions that had implemented information systems forsenior executives. The organizations included bothprivate and public companies and government insti-tutions. The six organizations are labeled here by analias, describing their principal business:

1. Major Railway Corporation,2. International Airline,3. Health Care Provider,4. Large University,5. Utility,6. Shipping Company.

4.3. Data collection

The research was conducted through a series ofpersonal interviews with several key personnel ineach organization. While many questions wereopen-ended, questionnaires were sent before the in-terview, thus ensuring that all interviews followedthe same general format and that interviewees couldprovide more informative data.

Interviewees were asked to complete the question-naires before interviews were held. There were twosets of questionnaires, one for companies still usingthe system, another one for those who had stoppedusing the system. The questionnaires are shown inAppendices A and B, respectively. Interviews wereconducted with internal developers who developedthe systems in-house, external consultants who helpedguide the development process, software vendorsEIS, and users. The face-to-face interview protocolfollowed the questionnaire questions in order to fo-cus on the aspects that were the most relevant tosystem success and failure. Both developers andusers were interviewed. Developers included boththe internal IS department in each organization andexternal consultants. System users were executivemanagers and middle managers. Observational visitsof the organizations were also conducted to watchthe systems in use.

The study did not produce quantitative data, norwas any attempt made to quantify essentially qualita-tive data. In many cases, we were simply looking for

Žthe absence or presence of a particular factor e.g.,.was there an operating sponsor? , while at the same

Page 6: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418398

time checking whether that characteristic was ful-filled only superficially, or in a meaningful way.

5. Results

5.1. EIS success

After questionnaire and interview results for allsix organizations were analyzed, three success casesemerged, two failure cases, and one unresolved case.The two failure cases were identified both by a lackof benefits derived by the firm, and by the decisionto discontinue the use of the EIS in both cases. Inother words, they were true failures. The unresolvedcase was identified by a situation where the systemwas actually used, but only at a small fraction of itsfunctionality, benefits had not yet been clearly real-ized, and that no future expansions were planned atthe time of the study. While this was not an aban-

Ždoned system, it had not met expectations and thusmet our definition of a Anon-successB, given in the

.previous section . Table 1 shows in more detail howthe six cases measured up against the previouslyintroduced list of success measures. Each case re-ceived a qualitative summary rating for every suc-cess measure. A measure rated as AGoodB meansthat most of the users agreed the measure was wellachieved. An AAcceptableB rating indicates marginal

performance of the relative success measure, withsome signs of success. For example, system use wasmarginal at Large University. Some users consid-ered the system to be successfully employed whileothers did not. The underlying issue was that systemuse was optional, and that executives were able toobtain the data through other means as well. Hence,the system did not play a strategic, but merely asupport role. A case rated APoorB reflect high agree-ment among users that the success measure was notwell achieved.

5.2. CSFs obserÕed

To demonstrate how EIS successes and failuresstacked up against the management of CSFs withinthe six organizations, we compiled summaries ofrelevant CSF performance data in Table 2. For eachorganization, management of each CSF is ratedthrough a summary rating of U for ACSF welladdressedB, or > for ACSF ignoredB. In addition, thesummary ratings are supported through factual datafrom each case.

The results emphasize the importance of CSFs.When all factors were present, the system succeeded;when they were absent, the system failed. In oneunresolved case, some factors were present and oth-ers not, with the result being undecided.

Table 1Success criteria for the six case studies

Page 7: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 399

Tab

le2

Cri

tica

lsu

cces

sfa

ctor

eval

uati

on

ŽŽ

ŽŽ

ŽŽ

.C

riti

cal

succ

ess

Maj

orra

ilw

aysu

cces

sful

Inte

rnat

iona

lai

rlin

esu

c-H

ealt

hca

repr

ovid

ersu

c-L

arge

univ

ersi

tyun

re-

Shi

ppin

gco

mpa

nyfa

ilur

eU

tili

tyfa

ilur

eca

se

..

..

.fa

ctor

sca

sece

ssfu

lca

sece

ssfu

lca

seso

lved

case

case

1.A

com

mit

ted

UU

UU

>>

and

info

rmed

Ex-

ecut

ive

Spo

nsor

))

))

))

)

The

Cha

irm

anan

dC

hief

The

Out

port

Sal

esM

an-

Mor

eth

an15

seni

orex

-T

heU

nive

rsit

yP

resi

dent

The

Dir

ecto

rof

the

orga

-T

heM

anag

ingD

irec

tor.

The

))

)

Exe

cuti

ve.

He

keep

sth

eag

ers

atH

ong

Kon

g,S

in-

ecut

ives

.T

hey

mak

eth

ean

dth

eD

irec

tor

ofP

lan-

niza

tion

.H

ene

ver

sets

EIS

proj

ect

isde

fine

dw

ith

clea

r)

))

EIS

proj

ect

high

lyvi

sibl

ega

pore

and

Lon

don.

The

yin

itia

lre

ques

tfo

rth

eE

IS.

nin

g.

Th

eU

niv

ersi

tyan

yde

adli

nefo

rth

eE

ISob

ject

ives

init

iall

y.T

he

EIS

))

)

inth

eor

gani

zati

on.

He

mak

eth

ein

itia

lre

ques

tfo

rT

hey

init

iate

the

syst

emP

resi

dent

has

are

lati

vely

proj

ect.

Los

sof

spon

sor-

proj

ect

has

acl

ear

vis

ibil

ity

)

ensu

res

the

reso

urce

san

dth

eE

IS.

The

yst

ayon

top

and

mak

eha

nds-

onus

eof

han

ds-

off

app

roac

hto

ship

afte

rth

edi

rect

orlo

stsi

nce

all

exec

utiv

esar

eto

ld)

)

poli

tica

lsu

ppor

tne

eded

for

ofth

eE

ISde

velo

pmen

t,th

esy

stem

.T

hey

keep

man

agin

gth

eE

ISpr

ojec

t;in

tere

ston

the

EIS

.N

ow

hat

the

obje

ctiv

esof

the

sys-

))

the

EIS

tosu

rviv

e.H

epr

ovid

ing

dire

ctio

nan

dco

nsta

ntpr

essu

reon

the

how

ever

,he

ensu

res

the

spo

nso

rsh

ipm

ean

sn

ote

mar

e.T

heM

anag

ing

Dir

ec-

)

enco

urag

esot

her

boar

dfe

edba

ck.

The

yco

mm

u-E

ISpr

ojec

tte

am.

reso

urce

ssu

ppor

tne

eded

com

mit

men

tto

the

allo

ca-

tor

deci

des

hedo

esno

tha

ve)

mem

bers

tofo

llow

suit

.ni

cate

stro

ngan

dco

ntin

u-fo

rth

eE

IS.

The

Dir

ecto

rti

onof

reso

urce

s.su

ffic

ient

tim

eto

over

see

the

)

ing

inte

rest

toth

eE

ISde

-of

Pla

nnin

gin

itia

tes

the

EIS

proj

ect.

He

dele

gate

sit

to

ve

lop

ers

an

dd

ata

EIS

.th

eC

orpo

rate

Bus

ines

sP

lan

)

prov

ider

s.M

anag

er.

Los

sof

spon

sors

hip

sinc

eth

eE

ISpr

ojec

tlo

stdi

rec-

tion

from

the

Man

agin

gD

irec

-

tor.

()

cont

inue

don

next

page

Page 8: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418400

Ž.

Tab

le2

cont

inue

d

ŽŽ

ŽŽ

ŽŽ

.C

riti

cal

succ

ess

Maj

orra

ilw

aysu

cces

sful

Inte

rnat

iona

lai

rlin

esu

c-H

ealt

hca

repr

ovid

ersu

c-L

arge

univ

ersi

tyun

re-

Shi

ppin

gco

mpa

nyfa

ilur

eU

tili

tyfa

ilur

eca

se

..

..

.fa

ctor

sca

sece

ssfu

lca

sece

ssfu

lca

seso

lved

case

case

2.A

nO

pera

ting

UU

UU

>>

Spo

nsor

))

))

))

)

17

Div

isio

nH

ead

s.T

heth

ree

staf

ffr

omth

eT

heIT

DM

anag

er.

She

The

Adm

inis

trat

ive

Off

i-N

ocl

ear

sing

leop

erat

ing

The

Cor

pora

teB

usin

ess

Pla

n)

)

The

yco

mm

itre

sour

ces

Sal

esD

epar

tmen

tat

the

help

sth

eex

ecut

ives

and

cer

ofth

eD

irec

tor

ofP

lan-

spon

sor

role

isas

sign

edal

-M

anag

er.

He

acts

inth

eM

an-

))

)

and

tim

e.T

hey

part

ici-

Hea

dqua

rter

s.T

hey

com

-de

sign

ers

buil

dco

nstr

uc-

ning

.S

here

pres

ents

the

thou

ghth

eex

ecut

ive

spon

-ag

ing

Dir

ecto

r’s

stea

dto

man

-)

pate

inth

eE

ISde

velo

p-m

itti

me

and

ener

gyto

the

tive

inte

ract

ions

and

com

-bu

sine

sssi

dean

dw

orks

sor

cann

otm

ake

suff

icie

ntag

eth

eE

ISpr

ojec

t.H

eis

not

))

)

men

t.T

hey

prom

ote

use

proj

ect.

The

yen

cour

age

mun

icat

ion.

She

isa

sys-

wit

hth

eve

ndor

hand

ling

tim

efo

rth

eE

ISpr

ojec

t.ac

quai

nted

wit

hth

eex

ecut

ive

))

ofth

eE

IS.

The

iren

-ot

her

outp

ort

man

ager

sto

tem

cham

pion

ona

day-

to-

day-

to-d

ayis

sues

ofde

vel-

spon

sor’

sw

ayof

thin

king

.H

e)

)

dors

emen

tof

the

EIS

com

-us

eth

eE

IS.

The

yco

m-

day

basi

san

dta

kes

onth

eop

men

t.S

heco

mm

uni-

does

not

unde

rsta

ndth

eM

anag

-

man

dsre

spec

tan

din

tere

stm

unic

ate

easi

lyw

ith

both

resp

onsi

bili

tyfo

rco

llec

t-ca

tes

wit

hth

eE

ISus

ers

ing

Dir

ecto

r’s

oper

atin

gfo

cus.

))

amon

got

hers

.th

eE

ISus

ers

and

the

EIS

ing

data

.S

hehe

lps

exec

-an

dda

tapr

ovid

ers.

She

)

team

.T

hey

serv

eas

aut

ive

user

sto

unde

rsta

ndtr

ansl

ates

user

s’ne

eds

to)

go

-bet

wee

nh

elp

ing

toth

eE

ISca

pabi

liti

esan

dth

ede

sign

team

.S

heis

)

mat

chbu

sine

ssne

eds

wit

hli

mit

atio

ns.

She

prot

ects

resp

onsi

ble

tom

atch

busi

-

tech

nolo

gica

lca

pabi

liti

es.

the

desi

gnte

amfr

omto

pne

ssne

eds

wit

hte

chni

cal

man

agem

ent

pres

sure

.ca

pabi

liti

es.

Page 9: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 401

3.A

ppro

pria

teIS

UU

U>

>>

staf

f)

))

))

)

Ate

amap

pro

ach

isA

team

appr

oach

isad

op-

Ext

erna

lco

nsul

tant

she

lpE

xter

nal

cons

ulta

nts

wit

hT

heE

ISis

deve

lope

dby

The

EIS

isfu

lly

deve

lope

dby

)

adop

ted,

whi

chin

clud

esIS

ted,

whi

chco

nsis

tsof

IMD

sele

ctha

rdw

are

and

soft

-th

ehe

lpof

the

oper

atin

gth

ein

tern

alIS

staf

fw

hoex

tern

alco

nsul

tant

s.T

hey

staf

fin

part

ners

hip

wit

hst

aff

and

the

repr

esen

tati

vew

are

that

prov

ide

afl

exi-

spon

sora

ndth

eus

ers

de-

are

led

bya

new

lyre

-he

lpde

fine

the

info

rmat

ion

and

exte

rnal

cons

ulta

nts,

spon

-fr

omth

eM

arke

ting

and

ble,

user

-fri

endl

yfr

ont-

end

velo

pth

ein

itia

lve

rsio

ncr

uite

dE

ISpr

ojec

tm

an-

capa

bili

ties

ofth

esy

stem

.)

))

)

sors

and

data

prov

ider

s.S

ales

Dep

artm

ent.

The

tool

,an

dcr

eate

ada

taba

seE

IS.

Con

sult

ants

help

se-

ager

.N

oon

eis

assi

gned

The

ycl

arif

yco

rpor

ate

re-

)

ISst

aff

com

efr

om

IMD

staf

fin

clud

esy

stem

that

prov

ides

nece

ssar

yle

ctE

ISha

rdw

are

and

soft

-to

hand

leth

eE

ISpr

ojec

tsp

on

sib

ilit

ies,

com

mit

men

ts,

))

dat

abas

ead

min

istr

atio

n,

anal

ysts

,sy

stem

desi

gner

sda

tafo

rth

eE

ISin

itia

lly.

war

e.T

hey

trai

nin

tern

alaf

ter

the

depa

rtur

eof

the

and

reso

urce

s.T

hey

help

se-

))

)

tech

nica

lsu

ppor

t,en

dus

eran

dpr

ogra

mm

ers.

The

yT

heE

ISte

amin

volv

esst

aff

tom

aint

ain

the

EIS

.E

ISpr

ojec

tm

anag

er.

In-

lect

EIS

hard

war

ean

dso

ft-

))

)

com

puti

ng.

Ext

erna

lco

n-fo

rman

ind

epen

den

tth

eIT

DM

anag

er,

inte

rnal

The

yof

fer

cons

ulti

ngte

rnal

ISst

aff

lack

expe

ri-

war

e.In

tern

alIS

staf

fon

ly

sult

ants

wor

kw

ith

exec

u-qu

ick-

resp

onse

team

that

tech

nica

lsu

ppor

ters

,bu

si-

serv

ices

afte

rth

ein

itia

lE

ISen

cew

ith

EIS

deve

lop-

help

solv

ete

chni

cal

prob

lem

s.)

))

tive

san

dIS

man

ager

sto

expe

rim

ents

wit

hqu

ickl

yne

ssin

form

atio

nan

alys

tsis

deve

lope

d.In

tern

alm

ent.

The

reis

lack

ofE

xter

nal

cons

ulta

nts

lack

un-

)

desc

ribe

wha

tis

ulti

mat

ely

con

stru

cted

pro

toty

pes

.an

dda

tapr

ovid

ers.

The

staf

fco

nfro

nted

wit

hpr

ob-

hum

anre

sour

ces

toco

m-

ders

tand

ing

ofth

eex

ecut

ive

en-

))

expe

cted

from

the

EIS

.T

heot

her

repr

esen

tati

ves

inte

rnal

ISst

aff

eval

uate

lem

saf

ter

the

exte

rnal

con-

plet

eth

epr

ojec

t.O

ther

viro

nmen

t.)

)

The

yhe

lpde

fine

the

in-

have

soph

isti

cate

dbu

sine

ssha

rdw

are

and

soft

war

e,in

-su

ltan

tsle

ft.

Inte

rnal

staf

fIS

proj

ects

com

pete

for

form

atio

nan

dca

pabi

liti

eskn

owle

dge

toid

enti

fyex

-st

all

LA

Nan

dw

rite

rou-

are

unab

leto

cont

inua

lly

scar

ceIS

reso

urce

sat

the

))

for

the

init

ial

EIS

.T

hey

ecut

ive

need

san

din

form

a-ti

nes

that

dow

nloa

dto

the

enha

nce

the

EIS

tom

eet

sam

eti

me.

The

ISst

aff

))

help

sele

ctE

ISha

rdw

are

tion

sour

ces.

The

yha

veE

IS.

The

busi

ness

info

r-us

ers’

new

requ

irem

ents

.us

eth

etr

adit

iona

lde

velo

p-

and

soft

war

ean

dth

enbu

ild

skil

lsof

busi

ness

orie

nta-

mat

ion

anal

ysts

help

exec

-m

ent

met

hod

tode

velo

p)

)

the

EIS

.T

hey

prov

ide

tion

and

sale

sman

ship

tout

ives

deci

dew

hich

info

r-th

eE

IS.

The

yar

eun

fa-

foll

ow-u

pob

serv

atio

nsan

dpr

omot

eth

eE

IS.

mat

ion

the

EIS

shou

ldco

n-m

ilia

rw

ith

such

unst

ruc-

)

com

mit

men

taf

ter

the

EIS

tain

.T

heIT

DM

anag

eris

ture

dsy

stem

deve

lopm

ent.

)

isbu

ilt.

The

team

has

assi

gned

asth

eE

ISco

ordi

-

both

tech

nica

lex

cell

ence

nato

rw

hois

inch

arge

wit

h

and

bu

sin

ess

exp

erti

seun

ders

tand

ing

the

exec

u-

abo

ut

the

info

rmat

ion

-ti

ves’

busi

ness

,re

port

ing

sour

ces

and

exec

utiv

es’

syst

ems,

crit

ical

data

,an

d

need

s.de

sire

dpr

esen

tati

onfo

r-)

mat

s.S

hehe

lps

man

age

the

evol

utio

nan

dsp

read

of

EIS

.

()

cont

inue

don

next

page

Page 10: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418402

Ž.

Tab

le2

cont

inue

d

ŽŽ

ŽŽ

ŽŽ

.C

riti

cal

succ

ess

Maj

orra

ilw

aysu

cces

sful

Inte

rnat

iona

lai

rlin

esu

c-H

ealt

hca

repr

ovid

ersu

c-L

arge

univ

ersi

tyun

re-

Shi

ppin

gco

mpa

nyfa

ilur

eU

tili

tyfa

ilur

eca

se

..

..

.fa

ctor

sca

sece

ssfu

lca

sece

ssfu

lca

seso

lved

case

case

4.A

ppro

pria

teU

UU

>>

>

tech

nolo

gy)

))

))

)

Com

pati

bili

ty,

capa

city

Com

pati

bili

ty,

capa

city

The

ypu

rcha

sene

wth

atU

sers

have

prob

lem

sac

-T

hecu

stom

-bui

ltap

p-S

low

resp

onse

tim

eis

re-

))

and

resp

onse

tim

ear

eac

-an

dre

spon

seti

me

are

ac-

enha

nce

the

perf

orm

ance

cess

ing

the

syst

em.

Slo

wro

ach

isus

ed,

they

wri

tepo

rted

byth

eus

ers.

A)

))

)

cept

edby

the

user

s.A

cept

edby

the

user

s.A

ofth

eE

IS.

Cap

acit

yan

dre

spon

seti

me

isre

port

edth

eir

own

soft

war

e.T

heve

ndor

-sup

plie

dE

ISso

ftw

are

))

vend

or-s

uppl

ied

EIS

soft

-fu

ll-c

apab

ilit

yE

ISso

ft-

resp

onse

tim

ear

eac

cept

edby

the

user

s.A

vend

or-

EIS

deve

lope

rsfi

nddi

ffi-

isus

ed.

Use

rsfe

elth

atth

e)

)

war

eis

used

.T

hesy

stem

war

eis

use

dan

da

byth

eus

ers.

Cus

tom

-su

ppli

edE

ISso

ftw

are

iscu

ltie

sto

wri

tesu

chsy

s-sy

stem

isno

tus

er-f

rien

dly.

))

supp

orts

for

rapi

dsc

reen

cust

om-b

uilt

syst

emis

de-

buil

tap

proa

chis

used

wit

hus

ed.

Use

rsfe

elth

atth

ete

m;

they

take

alo

ngti

me

Use

rsca

nnot

capt

ure

info

rma-

))

desi

gnan

dm

aint

enan

ce.

velo

ped.

The

syst

emsu

p-in

volv

emen

tof

EIS

tool

sE

ISis

diff

icul

tto

use

and

tobu

ild

the

syst

em.

The

tion

inth

eir

desi

red

form

at.

))

Use

rsre

port

that

the

sys-

port

sea

seof

use.

The

that

supp

ort

part

ial

EIS

de-

com

plic

ated

.E

ISso

ftw

are

cann

otpr

o-)

tem

has

‘‘us

erfr

iend

ly’’

syst

emsu

ppor

tsfo

rfa

stve

lopm

ent.

The

fron

t-en

dvi

dean

ypr

otot

ype

for

the

)

hu

man

rE

ISin

tera

ctio

n.

and

flex

ible

desi

gn.

The

too

lis

use

r-fr

ien

dly

.us

ers

totr

you

tth

esy

stem

.)

)

The

syst

emsu

ppor

tsa

syst

emsu

ppor

tsa

grap

hi-

Use

rsfi

ndth

atco

mm

and

)

grap

hica

lus

erin

terf

ace.

cal

user

inte

rfac

e.T

hest

ruct

ures

are

easy

tole

arn

)

The

tech

nolo

gyis

up-

tech

nolo

gyis

chan

ged

asan

dre

mem

ber.

grad

edto

resp

ond

tone

wth

eyca

nen

hanc

eth

eE

IS.

user

need

sif

nece

ssar

y.

Page 11: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 403

5.M

anag

emen

tof

UU

U>

>>

data

))

))

))

The

syst

empr

oduc

esda

taU

sers

can

only

get

the

The

desi

red

data

are

ob-

The

syst

emre

prod

uces

The

yar

eun

able

toob

tain

Use

rsca

nnot

get

thei

rde

sire

d)

inno

vel

form

ats.

The

data

inth

eE

IS;

thos

eda

tata

ined

and

are

read

ily

data

that

are

alre

ady

avai

l-th

ede

sire

dda

tafo

rth

eE

ISda

tafr

omth

eE

IS,

both

inte

rnal

))

)

syst

emad

dsva

lue

toth

ear

eno

tav

aila

ble

from

othe

rav

aila

ble

for

the

EIS

.ab

leon

pape

r.D

ata

are

even

ifit

isin

tern

al.

Thi

san

dex

tern

al.

Dat

aar

eno

t)

))

)

exis

ting

repo

rts.

Dat

aar

eso

urce

s.D

ata

are

tim

ely,

The

yve

rify

the

feas

ibil

-no

tup

date

dan

dar

ein

com

-in

crea

ses

the

tim

eof

the

prov

ided

onti

me.

Dat

aar

e)

tim

ely,

reli

able

,ac

cura

tere

liab

le,

accu

rate

and

con-

ity

ofob

tain

ing

info

rma-

plet

e.N

oex

tern

alda

taE

ISde

velo

pmen

t.no

tpr

esen

ted

inde

sire

dfo

r-)

))

and

cons

iste

nt.

The

sys-

sist

ent.

The

syst

emco

n-ti

onbe

fore

com

mit

ting

toar

epr

ovid

ed.

mat

s.T

hesy

stem

dupl

icat

es

tem

cons

ists

ofre

quir

edsi

sts

ofre

quir

edha

rdan

din

corp

orat

ein

toth

eE

IS.

pape

rre

port

s.)

hard

and

soft

data

,in

tern

also

ftda

ta,

inte

rnal

and

ex-

Dat

aar

eti

mel

y,re

liab

le,

and

exte

rnal

data

.te

rnal

data

.ac

cura

tean

dco

nsis

tent

.

6.C

lear

link

toU

UU

U>

>

bu

sin

ess

ob

jec-

tive

s)

))

))

)

Key

perf

orm

ance

indi

ca-

Ali

nkfr

omth

eE

ISto

The

EIS

isde

velo

ped

toT

heE

ISis

desi

gned

toE

ISdo

esno

tha

vea

clea

rE

ISis

not

star

ted

wit

han

y)

tors

are

iden

tifi

ed.

Ake

yth

eob

ject

ives

ofth

ebu

si-

mee

tth

ebu

sine

ssob

jec-

link

its

capa

bili

ties

dire

ctly

link

tobu

sine

ssob

ject

ives

.sp

ecif

icbu

sine

sspr

oble

man

d)

))

busi

ness

oppo

rtun

ity

isfo

-ne

ssis

defi

ned.

The

crit

i-ti

ves

that

are

iden

tifi

edby

toth

eus

ers’

info

rmat

ion

EIS

isno

tpe

rcei

ved

asne

ed.

Use

rsdo

not

unde

rsta

nd)

))

cuse

d.B

enef

its

ofus

ing

cal

succ

ess

fact

ors

are

al-

the

top

man

agem

ent.

Ane

ed.

The

valu

eof

the

impo

rtan

tby

the

exec

u-th

eob

ject

ives

and

bene

fits

of)

the

EIS

are

defi

ned.

read

yde

fine

dbe

fore

the

link

betw

een

the

EIS

and

EIS

isde

fine

d.ti

ves.

usin

gE

IS.

EIS

has

nocl

ear

com

men

cem

ent

ofth

eE

ISbu

sine

ssob

ject

ives

isde

-li

nkto

busi

ness

obje

ctiv

es.

proj

ect.

fine

d.

()

cont

inue

don

next

page

Page 12: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418404

Ž.

Tab

le2

cont

inue

d

ŽŽ

ŽŽ

ŽŽ

.C

riti

cal

succ

ess

Maj

orra

ilw

aysu

cces

sful

Inte

rnat

iona

lai

rlin

esu

c-H

ealt

hca

repr

ovid

ersu

c-L

arge

univ

ersi

tyun

re-

Shi

ppin

gco

mpa

nyfa

ilur

eU

tili

tyfa

ilur

eca

se

..

..

.fa

ctor

sca

sece

ssfu

lca

sece

ssfu

lca

seso

lved

case

case

7.M

anag

emen

tof

UU

UU

>>

orga

niza

tion

alre

-

sist

ance

))

))

))

The

EIS

deve

lope

rsre

-T

heE

ISde

velo

pers

re-

The

EIS

deve

lope

rsre

-R

esis

tanc

eis

foun

din

i-R

esis

tanc

eis

foun

dR

esis

tanc

eis

foun

dth

roug

h-

port

that

orga

niza

tion

alre

-po

rtth

ator

gani

zati

onal

re-

port

that

orga

niza

tion

alre

-ti

ally

due

toth

eun

frie

ndly

thro

ugho

utth

eE

ISde

vel-

ou

tth

eE

ISd

evel

op

men

t.)

)

sist

ance

isno

tsi

gnif

ican

t.si

stan

ceis

not

sign

ific

ant.

sist

ance

isno

tsi

gnif

ican

t.us

erin

terf

ace

and

slow

re-

opm

ent.

Dat

apr

ovid

ers

Cor

pora

tecu

ltur

eis

not

read

y)

))

))

Am

ajor

ity

ofus

ers

are

All

outp

ort

man

ager

sar

eM

ost

ofth

eex

ecut

ives

spon

seti

me.

Som

eus

ers

and

mid

dle

man

agem

ent

dofo

rth

eE

IS.

Som

eus

ers

are

wil

ling

tous

eth

esy

stem

.ke

ento

use

the

syst

em.

are

keen

tous

eth

esy

stem

.se

emto

bete

chno

phob

ic.

not

co-o

pera

tew

ith

the

EIS

stil

lre

luct

ant

toem

brac

eth

e)

))

))

Res

ista

nce

isha

ndle

dby

Res

ista

nce

isha

ndle

dby

The

ysu

cces

sful

lybu

ilt

Afe

wus

ers

seld

omor

proj

ect

man

ager

.T

here

iste

chno

logy

.)

educ

atio

nan

dne

goti

atio

n.tr

aini

ngan

dco

mm

unic

a-up

abe

lief

that

ITr

ISis

anne

ver

use

the

syst

em.

Re-

noac

tion

tom

anag

eth

e

tion

.im

port

ant

tool

tohe

lpst

aff

sist

ance

isle

sssi

nce

trai

n-re

sist

ance

.

achi

eve

busi

ness

obje

c-in

gis

prov

ided

and

the

tive

s.te

chno

logy

isen

hanc

ed.

8.M

anag

emen

tof

UU

U>

>>

syst

emev

olut

ion

and

spre

ad)

))

))

)

Spr

ead

from

17di

visi

onS

prea

dfr

omsi

xou

tpor

tS

prea

dfr

om50

exec

u-S

prea

dis

reas

onab

le,

The

yha

veno

plan

ning

The

reis

nosp

read

sinc

eth

e)

head

sto

over

40m

anag

ers.

man

ager

sto

over

60ou

t-ti

ves

inth

eH

eadq

uart

ers

from

50us

ers

to10

0.fo

rE

ISsp

read

and

evol

u-E

ISpr

ojec

tis

stop

ped.

Evo

lu-

))

))

Use

rsar

eco

nsul

ted

ona

port

man

ager

s.N

ewfe

a-to

500

over

40ho

spit

als.

The

yha

veno

evol

utio

nti

on.

The

yha

veno

logi

-ti

onis

not

mad

eto

resp

ond

to)

))

regu

lar

basi

s.N

ewm

od-

ture

san

dfu

ncti

ons

are

The

yad

dex

tra

mod

ules

due

toin

adeq

uate

hum

anca

lfo

llow

-up.

Lon

gde

-us

ers’

need

s.)

)

ules

orre

fine

men

tsan

den

-ad

ded

tom

eet

incr

easi

ngco

ntin

uall

y.T

hey

man

-re

sour

ces.

The

EIS

can-

velo

pmen

tti

me

lead

sto

hanc

emen

tsar

eca

rrie

dou

tus

erre

quir

emen

ts.

age

use

rex

pec

tati

on

s.no

tbe

enha

nced

quic

kly

disc

oura

gem

ent.

)

foll

owin

gth

eir

com

men

ts.

The

yen

cour

age

user

par-

enou

ghto

capi

tali

zeon

the

tici

pati

onto

expr

ess

thei

rne

wfo

und

requ

irem

ents

.

need

s.

Page 13: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 405

9.

UU

U>

>>

ab

Evo

luti

onar

yr

Pro

toty

ping

appr

oach

))

))

))

Evo

luti

onar

yde

velo

p-

Evo

luti

onar

yde

velo

p-

Evo

luti

onar

yde

velo

p-

Wit

hout

usin

gev

olut

ion-

Wit

hout

usin

gev

olut

ion-

Onl

yus

ing

prot

otyp

ing

ap-

))

))

men

tap

proa

ch.

Pro

toty

p-m

ent

appr

oach

.P

roto

typ-

men

tap

proa

ch.

Pro

toty

p-ar

yor

prot

otyp

ing

ap-

ary

orpr

otot

ypin

gap

-pr

oach

.W

itho

utus

ing

evol

u-

ing

appr

oach

.in

gap

proa

ch.

ing

appr

oach

.pr

oach

.pr

oach

.ti

onar

yap

proa

ch.

10.

Car

eful

lyde

-U

UU

>>

>

fine

din

form

atio

n

and

syst

emre

-

quir

emen

ts)

))

))

)

The

yde

fine

avi

ewof

The

yar

rang

eon

-sit

eT

hey

not

only

ask

man

-T

hey

just

revi

ewth

eex

-E

xecu

tive

sca

nnot

devo

teU

sers

are

unab

leto

arti

cula

te

wha

tth

eE

ISis

inte

nded

tom

eeti

ngw

ith

the

EIS

user

sag

emen

t,bu

tal

soas

kth

eis

ting

repo

rts

tode

fine

in-

tim

eto

the

EIS

proj

ect.

thei

rin

form

atio

nre

quir

emen

ts.

))

))

achi

eve.

The

yre

view

the

atea

chou

tpor

t.E

ISis

per

son

nel

wh

osu

pp

ort

form

atio

nre

qu

irem

ents

.In

form

atio

nan

dsy

stem

Use

rsdo

not

have

tim

eto

))

exis

ting

man

agem

ent

re-

cust

omiz

edto

mee

tth

ein

-m

anag

emen

t.T

hey

en-

The

yha

veno

tca

refu

lly

requ

irem

ents

cann

otbe

disc

uss

wit

hth

eco

nsul

tant

s.)

)

port

s.T

hey

inte

rvie

wex

-fo

rmat

ion

requ

irem

ents

ofco

urag

eus

ers

tode

vote

defi

ned

real

user

s’ne

eds.

clea

rly

defi

ned.

Ex

tern

alco

nsu

ltan

tsh

ave

ecut

ives

and

pers

onne

lw

hoea

chou

tpor

tm

anag

er.

tim

eto

try

the

EIS

prot

o-pr

oble

ms

toun

ders

tand

user

s’)

wor

kfo

rex

ecut

ives

.T

hety

pe.

need

sbe

caus

eof

ala

ckof

fa-

desi

gnis

capa

ble

ofm

eet-

mil

iari

tyw

ith

the

busi

ness

.

ing

the

requ

irem

ents

of

diff

eren

tex

ecut

ives

.

U,

CS

Fw

ell

addr

esse

d.>

,C

SF

igno

red.

aIt

erat

ive

proc

ess

tole

tde

velo

pers

desi

gnth

esy

stem

inpa

rts

but

part

sar

eca

refu

lly

defi

ned.

bIt

erat

ive

proc

ess

tole

tus

ers

test

each

part

ofth

esy

stem

.

Page 14: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418406

6. Discussion

Our study clearly supported the importance ofCSFs for system success. However, it also showed avery interesting pattern related to the absence orpresence of CSFs. Simply stated, the three successcases seemed to manage all CSFs right, while thetwo failure cases seemed to manage all of themwrong. This suggests two things.

First, there might exist a smaller number ofmeta-CSFs, which, if managed correctly, result in allothers to go right as well, or vice versa. Why so? Inessence, without the presence of such meta factors, itwould require a high level of coincidence for us tosee the very clear patterns of success and failure.Furthermore, previous research, including the study

w xof EIS at British Airways 6 suggests a smallernumber of very CSFs. Second, the failure cases areso drastic in their failure, one might suggest that theyhad been meant to fail. Apparently, there were forcesin the organizations that wanted the EIS to fail, andpursued this goal in a very systematic way.

Six cases are too few to identify meta-CSFs withany certainty. However, based on our analysis ofinterviews and questionnaires, and especially the fo-

Ž .cus on the yet unresolved case large university ,together with the data from the British Airwaysstudy, we can make several educated guesses. Largeuniversity did well on championship, having bothexecutive and operating sponsors. As the BA studysuggests as well, championship is a fundamentalfactor. For large university, it was one of few thathad gone right and that had given the system enoughimpetus to get well under way. Large university didnot do well on availability of resources, neither onpeople resources, nor appropriate technology, norfinancial resources. This seemed to be a fundamentalmissing factor. In the BA study, availability of re-sources, especially staff resources, played a major

Žrole. Furthermore, one of our success cases major.railway seemed to clinch success through very Adeep

pocketsB that allowed the company to obtain anyŽ .necessary technology and technology infrastructure ,

so that lack of resources never became an issue.Finally, the unresolved case suggests the importanceof one more factor, namely the tight link to businessobjectizes. This was a factor that was present in all

successful systems, also present in the unresolvedcase, but absent in the failure cases.

Clearly, executives will have a strong bottom-lineorientation, and very limited time to hunt for bene-fits. Thus, a system that can clearly demonstratebenefits, by being linked to business objectives, willhave a strong selling point with respect to useracceptance. Reflecting on the factors, we might alsosuggest a temporal consideration. Even before anEIS development is launched, it will require strongsponsorship to result in its initiation and seed re-sources. However, as the implementation continues,operational factors, such as resource availabilityŽ .people, technology and money become a necessarycondition. And finally, as the system moves into usephase, while continued executive sponsorship andresources are required, a system will receive littleuse if it cannot establish clear benefits.

The two failure cases and their peculiarcomplete-failure condition, offer some evidence forthe presence of additional critical failure factors.Apparently, the two organizations did not want anEIS to succeed. Comparing the two failures with theother cases in our set, interestingly, they also repre-sented the only two organizations with a Chinesemanagement system in place. In the Chinese man-agement system, the owner typically makes allstrategic and major personnel decisions and the dele-

w xgation to middle management is low 32 . Directsupervision of work and personal reporting relationsare more important forms of control, and the formalinformation system is often ignored and bypassed in

w xthe Chinese management system 32 . Therefore, atUtility, the top management preferred to receive datathrough informal personal reporting rather thanthrough an information system. On the other hand,support staff members at Utility wanted to maintaintheir influence by providing critical data for the topmanagement. Therefore, they were unwilling tochange, fearing of loss of influence once top man-agement would be able to circumvent them by ac-cessing the information system. Hence, it was no

Žsurprise that the staff of Utility as well as the staff.of Major Shipping was unwilling to supply data for

the system. At Major Shipping, the data providersand middle management did not co-operate with theEIS project manager. At Utility, the IT manager

Page 15: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 407

reported that the corporate culture was not ready forthe system’s development.

This factor is different from the CSFs Aclear linkto business objectivesB and Amanagement of organi-zation resistanceB. The management system, whichmight not be based on formal written rules, but onpeople’s experiences and beliefs of what it takes toget ahead in the organization, may be opposed tobusiness objectives. Consequently, if strong enough,the management system may cause initiatives to failŽby delaying them, or denying them some of their

.benefits that otherwise could have been beneficialw xfor the business 24 .

Mismatch of the information system with theorganization’s management system should also bedifferentiated from AnormalB organization resistance,which might be considered a generic fear of theunknown, or the Afear based cultureB, which illus-

w xtrated by Flowers 10 . In our failure cases, thereseemed to exist an interest in letting the system failrather than a lack of interest in system success.

7. Conclusions

With the growing influence of information sys-tems for executives, OLAP, and EIS components ofERP software, understanding system failure and suc-

cess is becoming more important as well. AssociatedŽwith EIS is a trend that is OLAP on-line analytical

.processing . In contrast to on-line transaction pro-Ž .cessing OLTP , which focuses on order entry and

other transaction-processing systems, OLAP includesdecision-making systems for marketing, sales, andfinance. OLAP is a way of looking beyond transac-tions to forces driving them. It can help companiesaccurately forecast sales in order to better plan in-ventory and production levels, know where advertis-ing is working and where they are wasting millionsof dollars, and determine if their products are cor-rectly priced.

In our study, we were able to confirm the applica-bility of all of Rockart and DeLong’s original eightCSFs, as well as two additional factors. Yet based onour findings, we suggest that organizations may Agetit rightB simply by managing three factors, champi-

Ž .oning at the executive and operational levels , re-sources, and linking the system to business objec-tives. We also saw evidence that these systems can-not succeed if they contradict the prevailing manage-ment system. As usual, companies that believe theycan solve their problems with an information systemwill likely fail. Those that translate business goalsinto corresponding information needs and then into awell-managed system will likely succeed.

Page 16: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418408

Appendix A

Page 17: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 409

Page 18: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418410

Page 19: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 411

Page 20: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418412

Appendix B

Page 21: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 413

Page 22: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418414

Page 23: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 415

Page 24: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418416

Page 25: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418 417

Page 26: Critical success factors revisited: success and failure cases of information systems for senior executives

( )P. Poon, C. WagnerrDecision Support Systems 30 2001 393–418418

References

w x1 C. Barrow, Implementing an executive information system:seven steps for success, Journal of Information Systems

Ž .Management, Spring 1990 41–52.w x2 F. Bergeron, L. Raymond, Evaluation of EIS from a manage-

Ž . Ž .rial perspective, Journal of Information Systems 2 1 199245–60.

w x3 M. Bensaou, M. Earl, The right mindset for managing infor-mation technology, Harvard Business Review, Sept.–Oct.Ž .1998 118–128.

w x4 J. Bird, Executive Information Systems Management Hand-book, NCC Blackwell, 1991.

w x5 W.C. Burkan, Executive Information Systems From ProposalThrough Implementation, Van Nostrand Reinhold, 1991.

w x6 N. Cottrell, K. Rapley, Factors critical to the success ofexecutive information systems in British Airways, European

Ž . Ž .Journal of Information Systems 1 1 1991 65–77.w x7 T. Davenport, Think Tank: Finding the Information that

Ž .Matters, CIO-Online, June 1, 1996 http:rrwww.cio.comrarchiver060196 dave.html.–

w x Ž .8 A. Dragoon, A day in the life, CIO Magazine 1997 Sept.15.

w x9 B. Fitzgerald, C. Murphy, Factors Involved in the Introduc-tion of Executive Information Systems into Organizations:An Empirical Study, Executive Systems Research Centre,University College Cork, 1994, ESRC Research and Discus-sion Papers, July.

w x10 S. Flowers, Information systems failure: identifying the criti-cal failure factors, Failure and Lessons Learned in Informa-

Ž . Ž .tion Technology Management 1 1 1997 19–29.w x11 G. Houdeshel, H.J. Watson, The Management Information

Ž .and Decision Support MIDS System at Lockheed-Georgia,Ž . Ž .MIS Quarterly 11 1 1987 21–30.

w x12 P.G.W. Keen, Value analysis: justifying decision supportŽ . Ž .systems, MIS Quarterly 5 1 1981 15–24.

w x13 D.E. Leidner, J.E. Elam, Executive Information Systems:Their Impact on Executive Decision Making, Proceedings ofthe Twenty-Seventh Annual Hawaii International Conference

Ž .on System Sciences 1993 206–215.w x14 N. McBride, The rise and fall of an executive information

Ž .systems: a case study, Information Systems Journal 7 4Ž .1997 277–288.

w x15 J.D. McKeen, T. Guimaraes, Successful strategies for userparticipation in systems development, Journal of Manage-

Ž . Ž .ment Information Systems 14 2 1997 133–150.

w x16 H. Mintzberg, The manager’s job: folklore and fact, HarvardŽ . Ž .Business Review 53 4 1975 49–61.

w x17 M. Newman, R. Sabherwal, Determinants of commitment toinformation systems development: a longitudinal investiga-

Ž . Ž .tion, MIS Quarterly 20 1 1996 23–53.w x18 J.H. Nord, G.D. Nord, Executive information systems: a

study and comparative analysis, Information and Manage-Ž . Ž .ment 29 2 1995 95–106.

w x19 A. Paller, R. Laska, The EIS Book, Dow Jones-Irwin, Home-wood, IL, 1990.

w x20 K.R. Rainer, H.J. Watson, What does it take for successfulexecutive information systems? Decision Support Systems 14Ž .1995 147–156.

w x21 K.R. Rainer, H.J. Watson, The keys to executive informationsystems success, Journal of Management Information Sys-

Ž . Ž .tems 12 2 1995 83–98.w x22 J.F. Rockart, D.W. DeLong, Executive Support Systems The

Emergence of Top Management Computer Use, Dow Jones-Irwin, Homewood, IL, 1988.

w x23 M. Santosus, Motorola’s Semiconductor Products Sector’sŽ .EIS, CIO-Online, Nov. 15 1998 http:rrwww.cio.comr

archiver111598 smart.html.–w x24 E.C. Shapiro, Fad Surfing in the Boardroom, Capstone,

Ž .Oxford, 1996, reprint of original 1995 edition .w x25 E. Turban, Decision Support and Expert Systems: Manage-

ment Support Systems, Macmillan, 1995.w x26 B. Vandenbosch, S.L. Huff, Searching and scanning: how

executives obtain information from executive informationŽ . Ž .systems, MIS Quarterly 21 1 1997 81–107.

w x27 J.G. Walls, G.R. Widmeyer, O.A. El Sawy, Building aninformation system design theory for vigilant EIS, Informa-

Ž . Ž .tion Systems Research 3 1 1992 36–59.w x28 H.J. Watson, M. Frolick, Determining information require-

Ž . Ž .ments for an EIS, MIS Quarterly 17 3 1993 255–269.w x29 H.J. Watson, K.R. Rainer, G. Houdeshel, Executive Informa-

tion Systems — Emergence, Development, Impact, Wiley,1992.

w x30 H.J. Watson, K.R. Rainer, C.E. Koh, Executive informationsystems: a framework for development and a survey of

Ž . Ž .current practices, MIS Quarterly 15 1 1991 13–30.w x31 G. Whymark, Successful Implementation of Executive Infor-

mation Systems, Speech to the 1991 Information TechnologyResearch Centre, School of Information Systems, Universityof New South Wales, November 1991.

w x32 R. Whitley, Business Systems in East Asia, SAGE Publica-tions, 1992.