No specifications (dealing with)

Subject: No specifications (dealing with)
From: Michael Andrew Uhl <uhl -dot- mike -at- epamail -dot- epa -dot- gov>
To: "TECHWR-L, (Tech Writers)" <TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM>
Date: Thu, 04 May 2000 08:50:29 -0400

Rebecca sums up my experience as well. These are great ideas and

Michael Andrew Uhl (mailto:uhl -dot- mike -at- epa -dot- gov)
Lockheed Martin - U.S. EPA Scientific Visualization Center
Ph. (office) 919.541.4283; 919.541.3716 (lab)
P.O. Box 14365 Research Triangle Park, NC 27709

rebecca rachmany wrote:

> Oh, and one more idea, put their [developers] ideas to paper yourself. Keep a file of the
> ideas, and distribute it from time to time to the appropriate people in the
> company. Be modest, say you are just recording things you hear. As time goes
> by, you will find several things happen:
> 1. The meeting summaries and informal "ideas" documents you distributed
> mysterioulsy are getting actually implemented the way you thought they
> should be.
> 2. Other people in the company will realize that documenting is a source of
> power, and they will start doing it themselves.
> 3. People will appreciate what you do.
> If those things don't happen, there are serious organizational problems at
> your company. However, if you like working with the people because they are
> nice and the job is fun despite the chaos, that's fine.
> Rebecca Rachmany
> Commercemind
> PO Box 920, Kfar Saba 44109
> 972-9-7642000 x217
> Mobile: 050-900600
> rebecca -at- commercemind -dot- com

Previous by Author: Terminology Software
Next by Author: Online Courseware: Need URLs
Previous by Thread: Documenting a product with no specifications?
Next by Thread: OT: BEWARE!!!

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

Sponsored Ads