Journal of Business and Technical Communication

 

Advanced Search

Journal Navigation

Journal Home

Subscriptions

Archive

Contact Us

Table of Contents

Click here for more information

Sign In to gain access to subscriptions and/or personal tools.
This Article
Right arrow Full Text (PDF)
Right arrow References
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Alert me to new issues of the journal
Right arrow Add to Saved Citations
Right arrow Download to citation manager
Right arrowRequest Permissions
Right arrow Request Reprints
Right arrow Add to My Marked Citations
Citing Articles
Right arrow Citing Articles via Google Scholar
Google Scholar
Right arrow Articles by MIREL, B.
Right arrow Articles by ALLMENDINGER, L.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us   Add to Digg   Add to Reddit   Add to Technorati  
What's this?
Journal of Business and Technical Communication, Vol. 9, No. 3, 259-288 (1995)
DOI: 10.1177/1050651995009003001

Collaboration between Writers and Graphic Designers in Documentation Projects

BARBARA MIREL

DePaul University

SUSAN FEINBERG

Illinois Institute of Technology

LEIF ALLMENDINGER

Northern Illinois University

Few, if any, studies on collaboration examine interactions between software manual writers and graphic designers. This study analyzes these collaborations, inquiring into the ways in which writers' and designers' processes of collaboration directly affect the form and substance of a finished manual. We argue that when these developers have dialogue, draft iteratively, and jointly make decisions, they produce manuals that could not possibly be developed through linear, assembly-line collaborative processes. We characterize three possible models of collaboration—assembly line (linear drafting), swap meet (iterative drafting and joint problem solving), and symphony (codevelopment in every aspect)—and use as a case study our own collaboration in developing a manual, detailing the concerns that writers and designers bring to a manual project. Analyzing our collaboration as an example of a swap-meet model, we examine four design problems that we faced and explain the ways in which our collaborative processes uniquely shaped our solutions to these problems.


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us   Add to Digg Digg   Add to Reddit Reddit   Add to Technorati Technorati    What's this?