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: Hey! She messed with *my* manual From:Kathleen MacDowell <kathleen -at- writefortheuser -dot- com> To:"Downing, David" <david -dot- downing -at- fiserv -dot- com> Date:Fri, 20 Mar 2009 13:38:11 -0500
It probably depends on the situation whether I'd feel a twinge.
I think there are circumstances when the original writer should be consulted
or asked to review. For example, if she/he knew the product best, it would
be a good idea to check back before making substantive changes, especially
if a jr. writer is doing the editing. A lot depends on the company process
too.
I also think that when multiple authors are working on documentation, the
original writer should be consulted about content edits.
But you know how it is, most of us are sensitive about/protective of our
writing, whether we're an engineer or a writer. Sometimes that's a good
thing, especially when it reflects a committment to quality and making sure
the company looks good.
Regards,
Kathleen
On Fri, Mar 20, 2009 at 1:05 PM, Downing, David <david -dot- downing -at- fiserv -dot- com>wrote:
> I was wondering whether anybody else here ever had the same reaction I just
> had in a similar situation.
>
> Our document set includes several manuals that I originally wrote, that
> have been around for many years, and that I have always revised when
> required. Well this time around, someone else in the documentation
> department was called upon to revise one of these manuals. Since it was one
> of mine, I offered to assist her if need be. But I just found out at today's
> departmental meeting that she was able to make the revisions without any
> consultation from me.
>
> Now I realize that when you work for a company, as part of a documentation
> department, no one person in the department owns a manual, and furthermore,
> I've made revisions to other manuals that I didn't originally write. But
> nevertheless, I found it rather disconcerting to have someone revising one
> of "my" manuals.
>
> Is that a feeling anybody else has had?
>
> David Downing
> Senior Technical Writer
> Credit Union Solutions
> Fiserv
>
>
>
--
Kathleen MacDowell
www.writefortheuser.com
kathleen -at- writefortheuser -dot- com
kathleen -dot- eamd -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-