What users say they want in documentation
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
While earlier work provided a partial view of users' preferences about manuals, for most users in most work contexts the important question remains open: What do users want in documentation? This paper presents the results of a study in which a diverse cross-section of 25 users was interviewed in depth about their needs and preferences with respect to software help systems, whether printed or on-line, that they use at work. The study's participants indicated that they preferred documentation, whether online or printed, that is easy to navigate, provides explanations at an appropriate level of technical detail, enables finding as well as solving problems through examples and scenarios, and is complete and correct. These preferences give rise to difficult issues, including a possibly inherent tension between coverage and precision, and variation among users with respect to desired level of technical complexity of explanation
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Determining causes and severity of end-user frustration
Ceaparu, I., Lazar, J., Bessiere, K., Robinson, J., & Shneiderman, B. (2004) · International Journal of Human-Computer Interaction · doi:10.1207/s15327590ijhc1703_3 · Cited by 399 · cited 5×
“This study also suggests that research based on the documentation use of college students [1] or software professionals [5] may not generalize well to the busy professionals who buy and use general-purpose applications.”
BackgroundInfluentialWhy don't people read the manual?
Novick, D. G., & Ward, K. (2006) · Proceedings of the 24th annual ACM international conference on Design of communication · doi:10.1145/1166324.1166329 · Cited by 98 · cited 4×
“The information we sought on user preferences for documentation was obtained as a phase of the interviews conducted for a companion study [6] into usability problems and solutions.”
BackgroundSelf-citation
Cited by
Towards automatically generating summary comments for Java methods
Sridhara, G., Hill, E., Muppaneni, D., Pollock, L., & Vijay-Shanker, K. (2010) · Proceedings of the IEEE/ACM international conference on Automated software engineering · doi:10.1145/1858996.1859006 · Cited by 514
“From this high-level goal, we derive our problem statement: Given a method signature and body statements for a method M , generate natural language text that summarizes the overall actions of M accurately, adequately, and concisely.”
MethodAutomatically documenting program changes
Buse, R. P. L., & Weimer, W. R. (2010) · Proceedings of the IEEE/ACM international conference on Automated software engineering · doi:10.1145/1858996.1859005 · Cited by 219
Including Human Factors and Ergonomics in Requirements Engineering for Digital Work Environments
Hakansson, E., & Bjarnason, E. (2020) · 2020 IEEE First International Workshop on Requirements Engineering for Well-Being, Aging, and Health (REWBAH) · doi:10.1109/rewbah51211.2020.00013 · Cited by 15
“Our results indicate that for user support to be effective it should focus on work tasks and support the users in solving problems with the help of the system rather than described technical aspects of the system, which confirms previous research [34][43][44].”
Result
Metadata
- Authors
- Novick, D. G., & Ward, K.
- Venue
- Proceedings of the 24th annual ACM international conference on Design of communication
- Publisher
- ACM
- Published
- 2006-10-18
- Pages
- 84-91
- OpenAlex
- W2007211928
- Cited by
- 56
- References
- 2
- FWCI
- 2.89
- Type
- conference paper
- Language
- en
- Open access
- closed
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: What users say they want in documentation. https://app.cochat.ai/papers/10.1145/1166324.1166346
- The paper
- Novick, D. G., & Ward, K. (2006). What users say they want in documentation. Proceedings of the 24th annual ACM international conference on Design of communication. https://doi.org/10.1145/1166324.1166346
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.