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.
Kathryn Scoffield wrote:
>
> Hello.
>
> I write a small column on techwriting for a local pub. This month's column
> will approach the topic of how NOT to personalize reviewers' feedback, even
> when it's delivered in an insensitive manner. The main focus of the piece
> will be that the users come first. If the reviewer's feedback will help the
> users, that's all that matters. So...does anyone have any suggestions on
> this matter? If you'd like, I'll immortalize you in the piece (send your
> name and job title). If you want to remain anonymous, that's okay too.
By "personalize," I take that you mean "take comments personally"?
If so, that's largely a matter of developing a thick skin through
experience. But it helps to realize that you'll never satisfy everyone
and that, in the end, you have to be the judge of what's relevant. The
unfortunate fact is that some people take reviewing as a chance to vent
frustration, either about you or the world at large. Others see it as a
chance to assert their place in the hierarchy. Still others seem to feel
that, unless they criticize severely, they won't be perceived as doing
their jobs properly.
However, you can keep your hypertension under control if you educate
reviewers to give you useful feedback. Accompany a review document with
a brief cover letter or guide that has samples of useful comments. One
of the main goals is to have reviewers not only point out errors, but
suggest corrections. For example, if they find that a passage is
technically incorrect, get them to write the correct information in the
margin. If they find a passage is unclear, encourage them to suggest
proper wording. If you can get reviewers to respond in these ways, then
they'll be more focused on suggesting improvements, and, just possibly,
have more understanding of what writing is about.
--
Bruce Byfield 604.421.7177 bbyfield -at- axionet -dot- com
"Down at the river one day waits the ghost
Turning into the people that we hide from the most."
-Rev Hammer, "Drunkard's Waltz"
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
