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:How is editing organized in your company? From:Tom Storer <tstorer_tw -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sat, 4 Jan 2003 03:44:12 -0800 (PST)
Greetings and Happy New Year to all. I just discovered
this newsgroup and will take advantage of it to ask a
question.
(I first sent this message via the Google Groups site,
but was warned by a list member that only a small
fraction of the list would see it. So I gave myself a
Yahoo account to receive the list digest and am now
posting this for maximum distribution. Apologies if
you've seen it twice...)
The context: I work in a large-ish software firm in
France. The company is currently undergoing some
streamlining and reorganization, but at the end of the
day we'll have 15 to 20 writers plus 2 or 3 web
technology specialists, divided among 5 or 6 main
product or functional groups. The writers in each
group will report to a doc lead who in turn will
report to a dev manager, but there will be some
transversal doc duties to ensure consistency of style,
template usage, and so on.
Until now we have never had any official editing. Peer
review is encouraged and doc managers review (with
varying degrees of diligence) the guides their teams
produce. We use an in-house Style and Usage Guide to
make this review easier.
The idea of "real" editing in the medium term is now
under consideration. By "real" editing I mean a more
centralized activity with clear processes and
definition of responsibilities. We'll soon be having a
brainstorming session to collect ideas and information
on how it's done in real life. We are thinking we
might have a full-time editor, or perhaps have two
people doing it half-time, working the rest of the
time on normal documentation duties.
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.
P.S. I'm not asking about how to edit, levels of
editing, that sort of thing - I already have a list of
books and articles on that subject. What I'm
interested in is how real-life companies organize a
serious editing function in their technical
publications department.
Thanks,
- Tom Storer
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
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.
---
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.