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.
Subject:Re: issues in communication From:Diane Blake <Diane_M -dot- _Blake -at- TSPB -dot- COM> Date:Fri, 31 Oct 1997 10:17:37 -0600
Good question! Here are my issues and solutions:
1. They wrote something and they don't like your rewrite because theirs is
more exact. You don't like theirs because it is not user friendly.
Solution: Rewrite it so you are both happy. Good relationships with
developers is essential.
2. Complaints about the documentation.
Solution: This is typically because the previous writers did not listen to
their ideas. Ask them about the documentation all along the process, spend
time listening to them. This is time well invested. Note: I think the
same applies to technical support. They are a main source of info.
3. Don't keep you up-to-date with product changes.
Solution: The time you took to listen will pay back here. Also, you have
to ask them periodically if anything's new.
4. Don't give you information about the product in time, change the time
schedule at the last minute, don't let you know about the need for a
document until the product is almost going out the door.
Solution: Be slightly ahead on the project, plan time in for unexpected
problems, and again, develop an ongoing dialogue with them. Finally, be
prepared for these problems and don't loose your cool (this doen't resolve
anything, but it feels better).
"Jeffrey R. Wiggin" <wiggin -at- RPI -dot- EDU> on 10/31/97 09:23:30 AM
Please respond to "Jeffrey R. Wiggin" <wiggin -at- RPI -dot- EDU>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
cc: (bcc: Diane M. Blake/PBTS)
Subject: issues in communication
Greetings fellow tech writers!
I'm a graduate student in tech. comm. conducting research on the
communication problems tech writers often face when dealing with product
developers, project managers, and so on. I'm currently trying to get
information about how these problems typically manifest themselves, how
we might prevent them from arising, and how we might alleviate them once
they do arise. Of particular interest to me is hearing about solutions
people have come up with when faced with such problems.
Any "real world" stories from the voices of experience would be
invaluable -- and greatly appreciated!
The archive search engine does not seem to be working, so if the list
has covered this topic in the past I apologize for bringing it up again.
Please feel free to mail me off-list.
Thanks in advance!
jw
--
_/_/_/_/ _/_/_/_/ _/_/_/
Rensselaer _/ _/ _/ _/ _/
Polytechnic _/_/_/_/ _/_/_/_/ _/
Institute _/_/_/ _/ _/
_/ _/ _/ _/
_/ _/_/ _/ _/_/_/ mailto:wiggin -at- rpi -dot- edu
Posts: mailto:techwr-l -at- listserv -dot- okstate -dot- edu
Commands: mailto:listserv -at- listserv -dot- okstate -dot- edu (e.g. SIGNOFF TECHWR-L)
Archives: http://listserv.okstate.edu/archives/techwr-l.html, http://www.documentation.com/, or http://www.dejanews.com/
Subjects: JOB:, QUESTION:, SUMMARY:, ANNOUNCE:, or none of these.
