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.
I believe you're right. Another way to think of it is that you first state
the requirement and then how to meet it. You need to "drive a car," "access
the reports database." The need occurs to you before you try to figure out
how to meet it; that's just basic temporality--state the problem (the
condition, the requirement), then give the fix (the instruction). Stating
the need provides needed context for further statements about how to meet
it. Otherwise, why should the reader care? S/he's being told to exit the
personnel screen, but why should s/he? What's the need? Clear that up first.
Why baffle and irritate the reader by making him/her wait till the end of
every sentence before s/he can learn the point of it?
steve wax stevewx -at- eskimo -dot- com
-------------------------------------------------------------
After the final no there comes a yes
and on that yes the future world depends. --Wallace Stevens
