Re: new kid on the block (long) Take TWO

Subject: Re: new kid on the block (long) Take TWO
From: Ed Wurster <glassnet -at- gmail -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 11 Mar 2005 06:29:14 -0500

J C wrote:

> When I ask former writer about his documentation
> procedures and working with others, I get "This
> company is used to the luxury of having me as the
> writer. I know so much about the technology that I
> just figure everything out myself and no one has ever
> had to review my work. They are not used to having to
> review anything and are spoiled in that way. They will
> have to get used to you asking them to review your
> work, but most of the time their feedback is useless
> anyway."

I worked with this guy. His comments bothered me initially, but his
description of how things work is true. Or at least true in this neck
of the woods.

> This bothers me in several ways. One thing is, as I am
> revising and updating some of the existing
> documentation and having it reviewed, the reviewers
> (QA) complain that some of the information is
> inaccurate or lacking. So I put in the updated
> information, clarifying and adding whatever might be
> missing. Then when former writer gets a hold of it, he
> chops most of it out saying "There is no need for
> this. No one reads the documentation anyway. It was
> better the without this information." I realize I may
> be dealing with some ego here and admit that nothing I
> do will ever make former writer as happy as he was
> when he was doing the writing.

Without seeing the text, no one can make a useful comment. He may be right.

What is clear is that QA wants to have a stake in the document. You
are viewed as a secretary, someone who can't possibly understand the
million bits of this product.

> Also, boss-wise. I attempted to sit down with boss
> (title: project manager) my first month to get an idea
> of what was expected, up-coming projects, and maybe
> discuss how I could like to handle documentation going
> forward or at least where it might fit in with product
> releases. (I didn't do it in a pretentious way; I was
> just trying to figure out how to survive). He
> basically told me the company motto "Just roll with
> it." He told me to have former writer review
> everything, so I'm kind of stuck with that right now.

I worked with him too. He is a survivor. Looks at your work in terms
of project cost. Very busy, and needs to fill in one more thing on the
pert chart. He will move on in 2-3 years.

> He also didn't want to give me any idea on upcoming
> projects because "things change around here so fast, I
> don't really know what you'll be doing." When I asked
> about documentation practices he told me "we don't
> want to get bogged down with procedures or processes
> (two P words I guess). Just roll with it."

Use your spare time to polish your resume. Concentrate on getting
documents "out the door."

> The other thing, (sorry this just gets longer and
> longer) I hear around here that is different than I'm
> used to is "It is better to have the product released
> BEFORE we start working on the documentation.
> Documentation is a luxury only." This has come up
> when I've asked about being part of the product
> developement cycle from the beginning and working in
> conjunction with alpha, beta and final product
> releases. Is this normal? I'm not used to trying to
> play catch up with the documentation when the product
> is already to the customer. There are loads and loads
> of products out there (this is software) with no
> documentation at all. Boss says they are an estimated
> two years behind in documentation. Frankly I don't see
> how this is going to change with the way things are.

You're in a culture that is different from your first job. You want
process and procedures because that is what you know from the first
job. Eventually you'll move on. You won't be able to change this
company's ideas about documentation. That is why "go with the flow" is
reasonable advice.

Ed Wurster
Tech Tips Blog


Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:

Your Ad Here! Have a product or service you'd like to get some attention for? Use this space to get the word out! Contact lisa -at- techwr-l -dot- com for more details.

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

new kid on the block (long) Take TWO: From: J C

Previous by Author: Numbered Lists in Framemaker
Next by Author: Re: Can't get there from here
Previous by Thread: Re: new kid on the block (long) Take TWO
Next by Thread: Re: new kid on the block (long) Take TWO

What this post helpful? Share it with friends and colleagues:

Sponsored Ads