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 agree with Suzette and my practice is much the same; however, I am finding
at the new place I work, the developers control almost every facet of the
company. It is a small company of only 41 employees and our market is
general contractors, so it is not really a software-minded organization. It
is run by the owner and creator (who was a general contractor for many
years) so, documentation goes before the developers for approval (not
review, approval). It is very frustrating to have no editorial control. More
and more, I feel like a typesetter.
Although it is my standard practice to send around a review sign-off sheet
with my documents, my request for a technical review only, is ignored. On
that sheet, I specifically state what my expectations are, but still I get
structural, grammatical, punctuation, style...(you name it) comments. If I
ignore or refuse to change something, management gets involved, and I lose.
It can cause a lot of hassles if the company you're working for doesn't
quite know why they hired tech writers only that they did some research into
how a software company works and tech writers were among the list of
positions. The moral of the story is to research the company dynamic before
you assume your writing role.. And, make sure that management has at least a
smattering of understanding of what you do and why. I have made a list of
questions I would ask from now on in an interview. Only when management
buys-in to what you do, can you expect to exercise any control over end user