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.
What I am trying to get up the nerve to ask you is: If what I so
loosely describe is the case, should we not write "Choose Options"
and not "Click Options"? Tell them what to do, but let them deduce
how to do it? Isn't that what their vanishing system manuals are
for?
---------End------------
I agree. We are faced with having our software available on at least 4
different user interfaces and barely enough staff and time to get one set of
documents completed; forget one set for each interface. Therefore we *must*
tell them *what* to do and let them deduce how (we help with the how by
providing a general interface document that will explain "in this interface
when the doc says xyz, you should click on the such and such button).
Its been a real challenge to go "interface independent," but it does make you
think about your writing more--and isn't that what we all love to do :)
