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: Educating Rita From:Scott Miller <smiller -at- PORTAL -dot- COM> Date:Mon, 3 May 1999 09:11:45 -0700
<<<Too much to quote, everything snipped...>>>
Some engineers are happy to take input on the UI from writers. Others
aren't. I give input in any case, based on the assumption that we're all
part of the same company.
For best results, tread lightly. You won't get a good response if you start
in with "this UI sucks," even if it does. Offering suggestions works best,
also, point out how bad UI comes across sounding dorky in the writing.
Finally, as Andrew points out, respect the division of labor, and don't
pitch a fit when your suggestions are ignored. Engineers often have really
whacked-out ideas about what should be documented, so we don't want to have
to implement their suggestions any more than they have to take ours.
