In-house software manuals must satisfy many internal audiences that are adapting to computerization. Manuals must meet the operational needs of users, represent the technical requirements of in-house programmers, and achieve the goals of upper managers for stability and productivity. To achieve these multiple objectives, in-house writers, with support from their managers, need two special strategies for project management: conducting a contextual audience analysis and acting as liaisons in their workplaces. Contextual audience analyses examine the organizational dynamics that influence how users learn about and respond to a new system. These analyses investigate the relationship between users' task responsibilities and job satisfaction; the consequences of current interchanges among users, programmers, and managers; and successful adoptions of other manuals in the organization. In-house writers must also become liaisons who diagnose sources of resistance to computerization, negotiate among competing priorities, and document the fruits of their labor in their manuals. General liaison strategies include socializing oneself into that role and choosing tactics appropriate for the structure of one's workplace. Specifically, writer-liaisons may participate in multiple staff meetings, involve users in program modification and documentation development, and champion innovative uses of the system. All together, these project management strategies make an in-house manual a vital part of the entire computerization process.
Get full access to this article
View all access options for this article.
References
1.
Allen, T. (1977). Managing the flow of technology: Technology transfer and the dissemination of technological information within the R & D organization. Cambridge: MIT Press.
2.
Bougon, M. (1983). Uncovering cognitive maps: The Self-Q technique. In G. Morgan (Ed.), Beyond method: Strategies for social research (pp. 173-188). Beverly Hills, CA: Sage.
3.
Chisholm, R. (1988). Improving the management of technical writers: Creating a context for usable documentation. In S. Doheny-Farina (Ed.), Effective documentation: What we have learned from research (pp. 299-316). Cambridge: MIT Press.
4.
Denzin, N. (1983). Interpretive interactionism. In G. Morgan (Ed.), Beyond method: Strategies for social research (pp. 129-146). Beverly Hills, CA: Sage.
5.
Dintruff, D. , Luecke, E., Milhaven, K., & Neff, B. (1988). Gathering advance customer information: Enhancing customers' partnerships. Proceedings of the 1988 International Professional Communications Conference (pp. 237-239). New York: IEEE Publishing Services.
6.
Doheny-Farina, S. (1986). Writing in an emerging organization. Written Communication, 3(2), 158-185.
7.
Downs, G. , & Mohr, L. (1979). Toward a theory of innovation. Administration & Society, 10, 379-408.
8.
Faigley, L. (1985). Nonacademic writing: The social perspective. In L. Odell & D. Goswami (Eds.), Writing in nonacademic settings (pp. 231-248). New York: Guilford.
9.
Grice, R. (1988). Information development is part of product development-not an after-thought. In E. Barrett (Ed.), Text, context, and hypertext (pp. 133-148). Cambridge: MIT Press.
10.
Hall, B. (1982). Strategic planning for employee productivity improvement. In L. Fredericksen (Ed.), Handbook of organizational behavior management (pp. 301-328). New York: Wiley.
11.
Haselkorn, M. (1988). The future of “writing for the computer industry.” In E. Barrett (Ed.), Text, context, and hypertext (pp. 3-24). Cambridge: MIT Press.
12.
Havelock, R. , & Havelock, M. (1973). Training for change agents. Ann Arbor, MI: Institute for Social Research.
13.
Huff, A. (1983). A rhetorical examination of strategic change. In L. Pondy, G. Morgan, P. Frost, & T. Dandridge (Eds.), Organizational symbolism (pp. 187-183). Greenwich, CT: JAI.
14.
Jablin, F. (1987). Organizational entry, assimilation, and exit. In F. Jablin, L. Putnam, K. Roberts, & L. Porter (Eds.), Handbook of organizational communication (pp. 679-740). Newbury Park, CA: Sage.
15.
Kern, R. (1985). Modeling users and their use of technical manuals. In T. Duffy & R. Waller (Eds.), Designing usable texts (pp. 341-375). Orlando, FL: Academic Press.
16.
Levine, L. (1988). Corporate culture, technical documentation, and organization diagnosis. In E. Barrett (Ed.), Text, context, and hypertext (pp. 149-174). Cambridge: MIT Press.
17.
Loveless, S. , & Bozeman, B. (1983). Innovation and the public manager. In W. Eddy (Ed.), Handbook of organizational management (pp. 391-410). New York: Marcel Dekker.
18.
March, J. , & Simon, H. (1958). Organizations. New York: Wiley.
19.
Mirel, B. (1987). Text and context: The special case of in-house documentation. Unpublished doctoral dissertation, University of Michigan.
20.
Mirel, B. (1988). The politics of usability: The organizational functions of an in-house manual. In S. Doheny-Farina (Ed.), Effective documentation: What we have learned from research (pp. 277-297). Cambridge: MIT Press.
21.
Perrow, C. (1986). Complex organizations. New York: Random House.
22.
Peters, T. (1987). Thriving on chaos. New York: Alfred Knopf.
23.
Pettigrew, A. (1973). The politics of organizational decision-making. London: Tavistock.
24.
Prue, D. , & Fredericksen, L. (1982). Overcoming resistance to change. In L. Fredericksen (Ed.), Handbook of organizational behavior management (pp. 329-360). New York: Wiley.
25.
Putnam, L. (1983). The interpretive perspective: An alternative to functionalism. In L. Putnam & M. Pacanowsky (Eds.), Communication and organization (pp. 31-54). Beverly Hills, CA: Sage.
26.
Rogers, E. , & Agarwal-Rogers, R. (1976). Communication in organizations. New York: Free Press.
27.
Rosenbaum, S. , & Walters, R. D. (1986). Audience diversity: A major challenge in computer documentation. IEEE Transactions on Professional Communications, PC-29, 48-55.
28.
Rubin, D. (1984). Social cognition and written communication. Written Communication, 1(2), 211-245.
29.
Schall, M. (1983). A communication-rules approach to organizational culture. Administrative Science Quarterly, 28, 557-581.
30.
Schein, E. (1985). Organizational culture and leadership. San Francisco: Jossey-Bass.
31.
Schon, D. (1983). Organizational learning. In G. Morgan (Ed.), Beyond method: Strategies for social research (pp. 114-128). Beverly Hills, CA: Sage.
32.
Shneiderman, B. (1987). Designing the user interface. Reading, MA: Addison-Wesley.
33.
Shuchman, H. (1981). Information transfer in engineering. Glastonbury, CT: Futures Group.
34.
Smircich, L. (1983). Implications for management theory. In L. Putnam & M. Pacanowsky (Eds.), Communications and organizations (pp. 221-241). Beverly Hills, CA: Sage.
35.
Spencer, J. W. (1988). The role of text in the processing of people in organizationsDiscourse Processes, 11, 61-78.
36.
Sticht, T. (1985). Understanding readers and their uses of texts. In T. Duffy & R. Waller (Eds.), Designing usable texts (pp. 315-340). Orlando, FL: Academic Press.
37.
Stohl, C. , & Redding, W. C. (1987). Messages and message exchange processes. In F. Jablin, L. Putnam, K. Roberts, & L. Porter (Eds.), Handbook of organizational communication (pp. 451-502). Newbury Park, CA: Sage.
38.
Weick, K. (1976). Educational organizations as loosely coupled systems. Administrative Science Quarterly, 21, 1-19.
39.
Weick, K. (1979). The social psychology of organizing. Reading, PA: Addison-Wesley.
40.
Weiss, E. (1988). How to write a usable user manual. Philadelphia: ISI Press.
41.
Yin, R. (1978). Organizational innovation: A psychologist's view. In R. Radnor, I. Feller, & E. Rogers (Eds.), Diffusion of innovations: An assessment. Evanston, IL: Center for Interdisciplinary Study of Science and Technology.
42.
Zand, D. (1981). Information, organization, and power. New York: McGraw-Hill.
43.
Zand, D. , & Sorensen, R. (1975). Theory and change and the effective use of management science. Administrative Science Quarterly, 20, 532-544.
44.
Zeidenstein, K. (1988). Collaboration as innovation: Why technical communicators should be members of the software development team. Proceedings of the 1988 Internal Professional Communications Conference (pp. 79-83). New York: IEEE Publishing Services.
