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.
Subject:Re: How is editing organized in your company? From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sat, 4 Jan 2003 10:24:57 -0500
Tom,
You will probably get one or more responses from people in traditional hierarchical organizations that more closely resemble your situation, but I thought I'd throw in my gadfly editor strategy to give you another data point.
I work for a small software company that was once somewhat larger. We're down to two tech writers in development now. They are both seasoned professionals and write well enough and consistently enough to produce documentation that is good enough. "Good enough" in this context means that a professional editor could probably improve it, but it communicates accurate information in a clear way, it is delivered in a medium and a format the users can access easily, and it doesn't delay the release of the software. "Good enough" provides a greater value to the company than "perfect" would.
However, I don't work for development. I set up my own communications services department (down to just me right now) under the company's operations VP. This enables me to offer editorial services to everyone in all departments. So if the documentation folks want me to take a pass at a document, I can. If the marketing folks (my main customers) want some prose cleaned up, I'm their guy. If the support people want help with their Web pages, they call on me. If a sales proposal or an RFP response is going out, I'm available to turn it into English. Etc.
I set my department up this way for a few reasons.
First, I wanted to take the corporate politics out of the equation. I've had the experience of being told by a PHB not to do work for department X because I belong to department Y--no matter that I had the time, was willing, and could have helped the company. I didn't want to repeat that experience here.
Second, I wanted to encourage a consistent external presentation for the company--to give it the feel of being a larger corporation than it is.
Third, I wanted to provide an interface where people with good technical or business skills could take advantage of my communications skills.
This is an efficient arrangement because we don't have individual departments hiring and training their own communications specialists. They can instead request resources from my department when needed. It also means that consistency is maintained in a more natural way than having divergent style guides negotiated back into a compromise by various power centers.
I'm not saying this is the only way to go, but it has worked so far for us. On any given day I might be updating the Web site for the marketing department, working with the CEO on a white paper, putting together a sales proposal, designing marketing collateral, creating new PowerPoint slides for an analyst presentation, editing a letter for a sales rep, or developing a document for the customer services organization.
I stay busy and entertained. The company knows where to go for editorial help. People own their documents whether or not they choose to avail themselves of my services, so accountability is straightforward. All in all, I recommend this approach.
Dick
Tom Storer <tstorer_tw -at- yahoo -dot- com> wrote:
[snip]
>The question: How *is* such an activity handled in
>real life? If those of you who work in companies with
>a well-defined editing activity could describe the way
>it's organized, and perhaps give a few tips and warn
>against pitfalls, I would be very grateful.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Order RoboHelp X3 today and receive a $100 mail in rebate and a FREE
WebHelp Merge Module for merging multiple Help systems on any desktop
or server. Order online today at 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.