Managing User Expectations in Information Systems Development

This paper provides new ways to explore the old problem of failure of information systems development in an organisation. Based on the theory of cognitive dissonance, information systems (IS) failure is defined as a gap between what the users expect from an information system and how well these expectations are met by the perceived performance of the delivered system. Bridging the expectation-perception gap requires that IS professionals make a radical change from being the proprietor of information systems and products to being service providers. In order to deliver systems and services that IS users perceive as valuable, IS people must become expert in determining and assessing users- expectations and perceptions. It is also suggested that the IS community, in general, has given relatively little attention to the front-end process of requirements specification for IS development. There is a simplistic belief that requirements are obtainable from users, they are then translatable into a formal specification. The process of information needs analysis is problematic and worthy of investigation.

Authors:

• Linda
• Sau-ling Lai

Keywords:

• Information Systems Development
• Cognitive Dissonance
• Expectation-Perception Gap
• Requirements Analysis.

References:

[1] Ackoff, R.L. (1967). Management misinformation systems.
Management Science 14(4), B-147-156.
[2] Avison, D.E. & Fitzgerald, G. (1988). Information Systems
Development: methodologies, techniques and tools, Blackwell Scientific
Publications, Oxford.
[3] Bailey, J.E. and Pearson, S.W. (1983). Development of a tool for
measuring and analyzing computer user satisfaction. Management
Science 29(6), 519-529.
[4] Baroudi, J. and Orlikowski, W. (1988). A short-form measure of user
information satisfaction: A psychometric evaluation of notes on use.
Journal of Management Information Systems 4(4), 44-59.
1000
500
200
100
50
20
10
5
2
1
Require - Design Code Develop- Accep- Operation
ment ment test tance test
Large ISD projects
Smaller ISD projects
Relative cost to fix error during
information systems development Organization Analysis
Requirements Specification
Users-
needs
Developers-
expertise
Analysis
is organizationally
valid?
Yes
Systems Design
Yes
Yes
Specification
is systematically
accurate?
Modelling
Techniques
No
No
Users Developers
[5] Boehm, B.W. (1981). Software Engineering Economics, Prentice Hall,
Englewood Cliffs, N.J.
[6] Checkland, P.B. (1981). Systems Thinking, Systems Practice, John
Wiley & Sons, Chichester.
[7] Davis, G., and Olson, M. (1984). Management Information Systems:
conceptual foundations, structure, and development, second edition,
McGraw-Hill, N.Y.
[8] Doll, W.J. and Ahmed, M.U. (1983). Managing User Expectations.
Journal of Systems Management June, 6-11.
[9] Doll, W.J. and Torkzadeh, G. (1988). The measurement of end-user
computing satisfaction. MIS Quarterly 12(2), 258-274.
[10] Festinger, L. (1957). A Theory of Cognitive Dissonance, Row &
Peterson, Evanston, IL.
[11] Glass, R. (1991). Software Conflict: Essays on the Art and Science of
Software Engineering, Yourdon Press, Prentice Hall, Englewood Cliffs,
N.J.
[12] Hirschheim, R. and Schafer, G. (1988). Requirements Analysis: a new
look at an old topic. Journal of Applied Systems Analysis 15, 101-118.
[13] Hirschheim, R., Klein, H.K. and Lyytinen, K. (1995). Information
Systems Development and Data Modeling, Cambridge University Press,
Cambridge.
[14] Jayaratna, N. (1991). Systems Analysis: the weak link in the systems
development process? Journal of Applied Systems Analysis 18, 61-68.
[15] Kettinger, W.J. and Lee, C.C. (1995). Exploring a ÔÇÿgap- model of
information services quality. Information Resources Management
Journal 8, 5-16.
[16] Lucas, H.C. (1974). Measuring employer reactions to computer
operations. Sloan Management Review 15(3), 59-66.
[17] Miller, G.A. (1956). The magical number seven, plus or minus two:
some limits on our capability for processing information. The
Psychological Review 63(2), 81-97.
[18] Oliver I., and Langford, H. (1987) Myths of demons and users. In
Galliers, R. (eds.), Information Analysis, Addison-Wesley Publishing
Ltd., England, pp. 113-123.
[19] Pitt, L.F., Watson, R.T. and Kavan, C.B. (1995). Service quality: a
measurement of information systems effectiveness. MIS Quarterly
19(2), 173-187.
[20] Shand, R.M. (1994). User manuals as project management tools: part I -
theoretical background. IEEE Transactions on Professional
Communication 37(2) 75-80.
[21] Shemer, I. (1987). A systemic analysis of a conceptual model.
Communications of the ACM, 30(6), 506-512.
[22] Szajna, B. and Scamell, R.W. (1993). The effects of information system
user expectations on their performance and perceptions. MIS Quarterly,
17(4), 493-516.
[23] Tojib, D. R., & Sugianto, L. F. (2011). Construct Validity Assessment in
IS Research: Methods and Case Example of User Satisfaction Scale.
Journal of Organizational and End User Computing, 23(1), 38-63.
[24] Zeithaml, V.A., Parasuraman, A., and Berry, L.L. (1990). Delivering
Quality Service: Balancing Customer Perception and Expectation, The
Free Press, N.Y.