Added by Geoff Sauer on Jan 12, 2003.
Average rating: 3.67/5.00 (n=3, std dev: 1.15)
 


Unlike many other professions, our work products rarely stand by themselves. The work product of an engineering team may be a new pager or PDA; the work product of a development team may be a general-market software application. Data sheets, programmers reference manuals, and microprocessor design guides don't have their own standalone markets. They are designed and produced specifically for supporting standalone products. Their value, therefore, lies in how well they serve as a conduit for transferring and translating knowledge about the product to customers or end users according to their requirements.
 
  View all 11 works by Le Vie, Donald S., Jr.  
  View all 13 works published by GaryConroy.com  


Reviews
Thomas Parks What's the Value of Technical Communication
Finally, someone has tackled the issue of assigning value to technical communications in a way that outlines how to implement a value-add measurement system for companies. LeVie's papers in technical communication have always provided insight and perspectives that offer something of interest to practitioners in the field.

Please share your rating/opinion of "What's the Value of Technical Communication?".
 PoorExcellent 
The link to this work seems to be broken.

Copyright © 2001-09 by the EServer. All rights reserved.Add a Work | Update this Work | Discussion Forum | Habitués