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.
I am not sure where the ethical dilemma resides. There is no doubt that
this is a screwy situation, but that is SNAFU.
If you feel very strong about the risks of doing it the way the change
manager wants you to, then I suggest spending about 2 hours (max) to write a
coherent risk analysis of the project as you see it and then meet with the
change manager to explain your position.
Then do it her way.
Tech writers can not save the world. We must raise the red flag when we see
trouble, but if your manager wants a manual about how to make toast then
write a manual about it. It might be moronic, but it isn't worth the fight.
IF you feel that you have to do it your way, then find a solution that
allows you to do both and pad your schedule so that both can be done. BUT
get your manager's task done first and to her satisfaction.
I am not talking about just being a brown-nose. There are fights worth
fighting and fights that take more time to fight than to actually do the
Finding roadblocks is normal. Being discouraged to actually talk to your
audience or your SME's is normal. Fighting the good fight is normal as
well. Don't give up, just make whatever improvements you can wherever you
As for requirements, All projects should have requirements, parameters,
scope, etc. Most writers make up their own. If you think the requirements
person is infringing on your job, then you write up some requirements (in
requirements language) and hand them to the RE as a jump start and then ask
to help develop the requirements. At my current client site, the RE's have
discovered that all my writers do a better job at getting requirements that
they do. SO... instead of hiring more RE's, we are hiring more writers.
People learn at their own rate. But if you push them hard, they don't learn
She's also having a requirements person write requirements for an addition
to the "manual!" Isn't requirements usually written for software, or do
people write formal requirements for info added to a manual?
Absolutely FREE! FrameMaker/Win 6 & 7 Express Customization (v3):
Quick-access buttons & keys to common functions, char tag/font drop-down
lists, charset browser, QRef guides & much more: http://www.microtype.com/2
Experience RoboHelp X3! This new RoboHelp release combines single sourcing,
print-quality documentation, conditional text and much more, into the most
monumental release of RoboHelp ever! http://www.ehelp.com/techwr-l
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.