1993
DOI: 10.1177/026839629300800307
|View full text |Cite
|
Sign up to set email alerts
|

Moving from An Executive Information System to Everyone's Information System: Lessons from a Case Study

Abstract: The history of a major steel company's executive information system (EIS) is reported from its inception in 1984, through its demise as a system for top management, to its transformation in 1991 as a strikingly successful information system for all managers and administrative staff. This case has significant implications for all those who are interested in providing technical support to top decision-makers. It also has important lessons for any organization that has an EIS or that is planning to implement the … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
1
0
2

Year Published

2006
2006
2021
2021

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 8 publications
0
1
0
2
Order By: Relevance
“…Manajemen puncak perlu membangun arsitektur TI yang sesuai dengan bisnis. Hal ini akan memperjelas kebutuhan teknologi yang sesuai untuk bisnis perusahaan [28]. 6.…”
Section: Keselarasan Bisnisunclassified
See 1 more Smart Citation
“…Manajemen puncak perlu membangun arsitektur TI yang sesuai dengan bisnis. Hal ini akan memperjelas kebutuhan teknologi yang sesuai untuk bisnis perusahaan [28]. 6.…”
Section: Keselarasan Bisnisunclassified
“…Melakukan pelatihan bisnis khususnya kepada kepala departemen TI untuk meningkatkan pemahaman bisnis. Dengan demikian fungsi direktur sistem informasi dapat dicapai tanpa merekrut orang baru atau menambah departemen baru [28].…”
Section: Keselarasan Bisnisunclassified
“…Successful support systems initially aimed at the executive level are likely to gain increasing acceptance and gradually expand into an enterprise-wide system embraced at several organizational levels (Wheeler et al 1993). This scenario suggested designing scalability into the proposed system (Power 2002) and considering the possibility of future (semi-)automated learning to alleviate the anticipated knowledge acquisition bottleneck (Fogel et al 1993).…”
Section: Defining System and User Requirementsmentioning
confidence: 99%