TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> And how much of the blame falls squarely on the shoulders of Boeing
Techwriters
> and Managers? It was up to them to be able to demonstrate their worth to
the
> company. The worth/cost would have included mitigated risk factors.
>
> Seems the lesson needs to be learned by many techwriting departments. Put
a
> dollar figure on the errors caught, engineering time saved. This along
with a
> decent study of value added should be able to protect in-house
techwriting.
>
Wow, I hope no one from Boeing is reading this thread. It's a knife-twister.
But Eric raises an interesting question. Must workers both (a) do their work
and (b) make a business case for their value? At most companies, higher-ups
look after cost/benefit analyses. As a result, the workers need to brace
themselves for the day the manager [mis]represents the workers' value to
those who set the budgets.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
