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.
Document, document, document!!
From consulting, I've learned that, when a client asks/insists
that I do something I think is dumb, I send a letter or memo saying that,
as per our conversation of XX/XX/XX, I am submitting whatever as
requested.
When it's politic, I'll also write my recommendations *and the
style guide {or whatever} I'm basing them on*. If they're dissed, then I
send a subsequent document documenting the dis.
This saved my butt when I did a manual under the project mgmt of
a
paranoid illiterate, otherwise a nice guy <g>, at the insistence of *his*
boss, who really should've known better.
Any *recent* mil spec style guides to back up your side? Some SBIR
proposal writing info I've seen requests clarity. Maybe ask proposal
writers' list?
Mary Durlak Erie Documentation Inc.
East Aurora, New York (near Buffalo)
durl -at- buffnet -dot- net
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
