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.
Barb wrote:
I'm thinking it is helpful to the reader to see the screen
before the
instruction so he'll know he's in the right place when he takes
the action
specified in the instruction. Anybody have an opinion they'd
care to share?
I wholeheartedly agree with you. Placing the screen after the
instructions would be confusing. I like to see the screen, take the
elements of the screen in, and then start reading the procedure. This
way, by the time I start following the steps, I've already noted the
screen elements (naming conventions, list boxes, tabs, etc.). So, when
they are mentioned in the procedures, I know what they're talking about
and that I'm in the right place.
