Technical communicators migrating from product documentation to product development collaborate with more established development professionals from engineering and programming to produce usable new technologies. Although product developers have rightfully claimed the technological
triumphs society has come to expect, they are also the principal source of poor product designs, delayed product shipments, and infamous cost-overruns. Technical communicators will find their own product development contributions thwarted by the same factors that have frustrated the best efforts
of their more practiced colleagues. To retain their hard-won place on the product development team, technical communicators must re-engineer the project environment to ensure product usability and their role as user advocates. To do so, however, technical communicators must understand and
master the forces that undermine projects. An experiential learning strategy in project management has been designed at Bentley College to help technical communicators work with other IT practitioners to accomplish that goal.
Document Type: Research Article
Publication date: February 1, 2002
More about this publication?
Technical Communication, the Society's journal, publishes articles about the practical application of technical communication theory and serves as a common arena for discussion by practitioners. Technical Communication includes both quantitative and qualitative research while showcasing the work of some of the field's most noteworthy writers. Among its most popular features are the helpful book reviews. Technical Communication is published quarterly and is free with membership.