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 constitutes a good checklist? (Take II) From:"Hart, Geoff" <Geoff-H -at- MTL -dot- FERIC -dot- CA> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 25 Jun 2001 11:05:46 -0400
Christine Gonzales continues the discussion of checklists: <<I am finding
myself asking -what would a readable, function, and usable checklist look
like?>>
Well, please note that I'm not part of your audience, so the first thing you
should do is spend a few moments talking to them to find out what they've
liked about past checklists they've used--and what they've disliked! But in
terms of providing general guidance that will help you produce something you
can then test on your audience:
- Emphasize legibility: Make the text easy to read and follow, and in
particular, use large enough type with enough spacing between points that
readers can't easily skip a step.
- Avoid "turnoffs": Use enough white space, even at the expense of length,
that the page doesn't look intimidating and thus start readers off on the
wrong foot ("damn, this looks scary; look at all this information!").
Compare your initial reaction to a typical modern user manual and to a legal
disclaimer and you'll see the difference that proper design can make.
- Chunk text appropriately: For example, start each new series of steps on a
new page, or group steps into small, manageable chunks so that each chunk
looks less intimidating.
The actual design will depend on your audience, so using these three points,
ask one or two members (more, if you have time) what factors would satisfy
each of these criteria. Prepare a prototype, give it to the users, and ask
for feedback. Revise, and try again.
--Geoff Hart, FERIC, Pointe-Claire, Quebec
geoff-h -at- mtl -dot- feric -dot- ca
"User's advocate" online monthly at
www.raycomm.com/techwhirl/usersadvocate.html
"Some painters transform the sun into a yellow spot; others transform a
yellow spot into the sun."- -Pablo Picasso (1881-1973)
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.