The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
The user–developer communication process: a critical case study
Open accessAbstract
Abstract. Although user participation in systems development is widely believed to have positive impacts on user acceptance, it does not guarantee success and there is still much that we do not know about how and why user participation sometimes delivers positive benefits, but not always. Much of the prior research on user participation assumes that user–developer communication will ensure that the resulting system will be designed to meet users’ needs and will be accepted by them. The nature and quality of the communication between users and developers, however, remains an understudied aspect of user participation. In this paper, we focus on the user–developer communication process. We propose a process model that delineates four stages of communication between users and software developers, and we argue that these stages must occur for user participation to lead to effective outcomes. To illustrate our model, we apply it to analyse a ‘critical case study’ of a software project that failed despite high levels of user involvement. We show that when ‘communication lapses’ occurred in several of the user–developer communication stages, developers failed to be informed regarding the underlying reasons that users avoided the system. Based on the insights from this case study, we advise researchers and practitioners how to leverage the potential benefits of user participation, rather than take them for granted.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Organizational Information Requirements, Media Richness and Structural Design
Daft, R. L., & Lengel, R. H. (1986) · Management Science · doi:10.1287/mnsc.32.5.554 · Cited by 9,868
Information Technology and Organizational Change: Causal Structure in Theory and Research
Markus, M. L., & Robey, D. (1988) · Management Science · doi:10.1287/mnsc.34.5.583 · Cited by 2,108
Cited by
Venkatesh, V., Brown, S. A., & Bala, H. (2013) · MIS Quarterly · doi:10.25300/misq/2013/37.1.02 · Cited by 2,363
Bentley College, U., Markus, M. L., Mao, J.-Y., & Renmin University of China, C. (2004) · Journal of the Association for Information Systems · doi:10.17705/1jais.00057 · Cited by 323
Benefits of and barriers to involving users in medical device technology development and evaluation
Shah, S. G. S., & Robinson, I. (2007) · International Journal of Technology Assessment in Health Care · doi:10.1017/s0266462307051677 · Cited by 299
The Role of User Participation in Information Systems Development: Implications from a Meta-Analysis
He, J., & King, W. R. (2008) · Journal of Management Information Systems · doi:10.2753/mis0742-1222250111 · Cited by 306
A systematic review on the relationship between user involvement and system success
Bano, M., & Zowghi, D. (2015) · Information and Software Technology · doi:10.1016/j.infsof.2014.06.011 · Cited by 290
Metadata
- Authors
- Gallivan, M. J., & Keil, M.
- Venue
- Information Systems Journal
- Publisher
- Wiley
- Published
- 2002-12-18
- Volume
- 13
- Issue
- 1
- Pages
- 37-68
- ISSN
- 1350-1917 (ISSN-L)
- 1365-2575
- OpenAlex
- W2074043044
- Cited by
- 203
- References
- 2
- FWCI
- 8.98
- Type
- journal article
- Language
- en
- Open access
- hybrid
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: The user–developer communication process: a critical case study. https://app.cochat.ai/papers/10.1046/j.1365-2575.2003.00138.x
- The paper
- Gallivan, M. J., & Keil, M. (2003). The user–developer communication process: a critical case study. Information Systems Journal. https://doi.org/10.1046/j.1365-2575.2003.00138.x
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.