Strategy for Getting Information

Subject: Strategy for Getting Information
From: Barbara Ridley <BRidley -at- USCCMAIL -dot- USCC -dot- BMS -dot- COM>
Date: Wed, 17 Jul 1996 09:14:43 -0500

Hello:

I'm two for two on receiving choice and alternative solutions.
With this kind of success, I'd like to make it three for three.

Situation:

* An computer application has been developed and needs to be
documented. Documentation was an afterthought.

* I do not have access to the application. It is live, meaning
it is currently in use.

* One person has been assigned to be my resource person. This
person knows who uses the application, what they use it for and
can give me step-by-step procedures for the tasks.

* We have had several meetings that helped me produce an
information plan. The plan includes the scope of the project and
my suggestions on presentation for the manual, etc.

* The resource person's supervisor thinks we have already spent
too much time discussing things (approx. 5 hours) and wants to
see the documentation.


Need advice on:

* Does anybody have a strategy for quickly and efficiently
getting information and writing the procedures that go in the
documentation?

Currently I lurk over the shoulder of the resource person, watch
as they move through how a task is done, write a rough draft of
the procedures. I also ask for screen captures on everything so
that I can pick and choose later. Back at my office, I will
rewrite for what the end-user will read.

BTW, I cannot ask the resource person to write a rough draft of
the procedures...that would be doing too much of the work I'm
suppose to be doing.

Thanks for any helpful suggestions.

-- Barb --
bridley -at- usccmail -dot- bms -dot- com

TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-



Previous by Author: ARE SECTIONS/CHAPTERS ALWAYS NEEDED?
Next by Author: "tridant" vs. "trident"
Previous by Thread: Screwdrivers
Next by Thread: Re: Strategy for Getting Information


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


Sponsored Ads