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.
RE: Question about expanding the role of technical writers
Subject:RE: Question about expanding the role of technical writers From:Ed <glassnet -at- gmail -dot- com> To:"Wroblewski, Victoria" <victoria -dot- wroblewski -at- necect -dot- com> Date:Sat, 5 Dec 2015 09:32:22 -0500
I transitioned to a new job this summer. The role is something like
Victoria's position. The manuals are large, on the order of 900 pages. The
system is a combination of mechanical, piping, and controls.
- liaison between the customer and doc developer.
- analyze engineering docs and markup doc pdf's for changes.
- editing, writing, re-writing.
- request data from vendors.
- markup or edit graphics.
- convert pdf's to graphics format.
- track changes at a level which allows edits to additional documents.
- quality checks.
- physical delivery of docs.
- provide monthly report internally and to client.
- bring a new controls tech up to speed.
- remove periods from end of list items.
- ekcetera, ekcetera, ekcetera.
Got a little stooge-esque at the end of that list, but you get the picture.
Excel, Acrobat, Word, Photoshop, Visio, three highlighters, and a ton of
emails.
On Dec 4, 2015 14:37, "Wroblewski, Victoria" <victoria -dot- wroblewski -at- necect -dot- com>
wrote:
>
> In our group, my running joke is that we are really more systems analysts
than documentation. If I write/edit more than a paragraph of text that
will end up in a document a day, it's been a Big Writing Day.
>
> Our system is complex with a lot of parts, and the way some engineering
tasks get so compartmentalized, there is not always the best understanding
of how each little thing can have a big impact to other parts that they may
not be aware of.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com