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: Thoughts on Working With Developers (long) From:Elna Tymes <etymes -at- LTS -dot- COM> Date:Mon, 5 Apr 1999 10:50:59 -0700
SEnglish -at- MICROS -dot- COM wrote:
> Have any of you have ever taught your SMEs *how* to do a tech edit?
What a great approach he then outlined! The point of his approach was that,
when you're not getting the kind of feedback you want, pay attention to how
you're asking for it.
While the lunchtime 'training' session is one approach, another that seems to
work is to outline what you want on paper, and sent it along with the review
copy. You can make some of the same points Steve made (about not wasting
developer time on English edits, but that their perspective on technical
content is really important), but they'll get pretty much the same ideas about
what's important for them to check and what they can leave for others.
