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.
>Have other people encountered this problem? What have they
>done to resolve
>the situation? What can I do to persuade the developers to put
Oh, and one more idea, put their 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
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.
PO Box 920, Kfar Saba 44109
rebecca -at- commercemind -dot- com