Abstract
OFTEN the quality of product documentation affects the user's perception of the product. Shortcomings in product documentation, therefore, may cause users to assume that the product quality has been compromised. The solution is to keep the reader in mind as we write. To do so will engender confidence and minimize misinterpretation. In the first article Gudknecht reminds us that procedures should be presented in a format that allows the reader to locate and use information efficiently. For example, if we're writing about how to calibrate or troubleshoot a device, using a flowchart may be better than using only text.
- Journal
- IEEE Transactions on Professional Communication
- Published
- 1982-09-01
- DOI
- 10.1109/tpc.1982.6447771
- CompPile
- Open Access
- Closed
- Topics
- Export
- BibTeX RIS
Citation Context
Cited by in this index (0)
No articles in this index cite this work.
References (0)
No references on file for this article.
Related Articles
-
Computers and Composition Jun 2026Tim Lockridge
-
Journal of Response to Writing Apr 2026Gilliland, Betsy; Moussu, Lucie
-
Journal of Response to Writing Apr 2026Laflen, Angela
-
Journal of Response to Writing Apr 2026Testa, Andrew
-
Res Rhetorica Apr 2026The rhetorical dimension of the justification for the absence of direct military support for Ukraine in Joe Biden’s statements ↗Marta Kobylska