Effective Information Gathering?

Subject: Effective Information Gathering?
From: Laurence Burrows <burrows -at- IBM -dot- NET>
Date: Tue, 9 Feb 1999 18:14:34 +1100

GhostWolf Davidson <ghstwolf -at- SLIP -dot- NET> wrote:

--------------snip
We have a choice of two separate processes (described below).
--------------snip


--------------snip
Approach 1 (Our current approach):
* Each writer is responsible for specific manuals
--------------snip

OK, if you re-use chunks/chapters of standard information between *all* the
manuals. For example: each writer uses the one standard introduction
chapter, not their own 'version'.

Make sure you keep a database (even if it's handwritten notes in a folder)
of all the common elements, styles, expressions, headwords for the indexes,
'depth' of explanations, spelling conventions, screen-shot dpi., etc.

--------------snip
Approach 2 (Proposed by higher management):
* Each writer is assigned specific components of the entire product
line, and documents only that component *in each of the manuals*.
--------------snip

Well, no...

Could be a problem if one of your team leaves (for whatever reason)
half-way to the deadline. No-one else in the team will understand that
person's products, will they? And no-one will have time to teach the
replacement person.

Small team + no redundancy + tight deadlines = recipe for disaster.

Regards,

....................................................
Laurence Burrows, Navex Pty Ltd
mailto:burrows -at- ibm -dot- net, 100026 -dot- 172 -at- compuserve -dot- com
tel: +61 3 9602 4533 fax: +61 3 9602 4854
....................................................

From ??? -at- ??? Sun Jan 00 00:00:00 0000=




Previous by Author: Re: What's wrong with "too"?
Next by Author: Re: Shaded Headings in FrameMaker
Previous by Thread: Effective Information Gathering?
Next by Thread: Re: Mac users


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

Sponsored Ads


Sponsored Ads