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:What to do when there are multiple paths From:Melanie Shook <mshook -at- com2001 -dot- com> To:"'techwr-l -at- lists -dot- raycomm -dot- com'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 15 Sep 1999 16:59:32 -0500
A twist on Amy's question:
I'm documenting a telecommunications application that has multiple ways to
perform a task:
Click on the toolbar
Using telephone keypad
Using voice commands over the telephone
Drag and drop from various places
I'm doing a task oriented user guide, and so far have come up with nothing
better than explaining each option for each task, in sequence, with a
graphic in the margin to highlight each method (e.g. a phone, a talking
head, a PC, etc.) I've included an section in the "quick start" chapter
that explains the various methods.
