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.
Re: Thinking like a user, or sticking to tried and true?
Subject:Re: Thinking like a user, or sticking to tried and true? From:Steven Jong <SteveFJong -at- comcast -dot- net> To:TECHWR-L Digest <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 21 Dec 2006 08:18:55 -0500
What a thoughtful question! When in doubt, put yourself in the user's
shoes.
You call this a "document," which I'm conditioned to think of as a
multi-chapter creature with a foreword, etc. However, "copying
settings from one router to another" sounds like a (single) procedure
that could be covered in a page or two, or in a single Help topic.
Assuming it's closer to the latter in simplicity, I'd be inclined to
skip the overview as well. Remember, though, audience diversity:
different people will read and use the document, and some might want
at least a brief overview.
I have had success, even in brief procedures, with stating up front
the purpose of the procedure, and listing any information that the
user has to have before beginning. (For instance, "Before you begin,
you need to know the IP address of the new router....") This is
functionally an overview, but it could be as little as a paragraph's
worth of material, or a paragraph and a bulleted list.
-- Steve
Steven Jong, Past President
STC Boston Chapter
978-413-2553 [C]
Boston Chapter Web site: www.stcboston.org
* I am a candidate for STC Director *
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList