Re: Re. Documentation size & shape research?

Subject: Re: Re. Documentation size & shape research?
From: "Ann-Marie Grissino" <amarie -at- fpoint -dot- com>
To: "Hart, Geoff" <Geoff-H -at- MTL -dot- FERIC -dot- CA>, "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 25 Apr 2000 09:28:35 -0400

Don't forget Edward Tufte!
Ann-Marie Grissino
-----Original Message-----
From: Hart, Geoff <Geoff-H -at- MTL -dot- FERIC -dot- CA>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Cc: 'brad_m -at- unity -dot- ncsu -dot- edu' <brad_m -at- unity -dot- ncsu -dot- edu>;
'monicaleggoe -at- hotmail -dot- com' <monicaleggoe -at- hotmail -dot- com>
Date: Tuesday, April 25, 2000 9:06 AM
Subject: Re. Documentation size & shape research?


>Monica Leggoe is <<...conducting research on principles for choosing the
>size, shape, binding, and outer appearance of manuals, documentation, and
>user's guides but, surprisingly, is having difficulty coming up with any
>research or guidelines on the topic. Can anyone suggest any books,
articles,
>or websites that she might look at to give her some help with the topic.
I'm
>frankly surprised I haven't been able to come up with anything for her...
>
>There are several issues to consider here. First, there's the _graphic_
>design issue, for which there are a raft of good books available. I
>personally don't recommend Robin Williams (personal taste, plus I find she
>lacks a grounding in cognitive psych and information design), but Roger
>Parker's done marvelous stuff. And if you've got a big budget, the often
>erratically published newsletter "Before and After" (John McWade) is
>probably the best resource in existence for understanding how people
>perceive design, and how you develop a design based on those perceptions.
>John is an excellent graphic designer, but he also understands the user's
>perspective (something I find lacking in Williams' books).
>
>Second, there's the _information_ design issue. I generally recommend Karen
>Schriver's "Dynamics in Document Design" for anyone who needs to understand
>the cognitive principles behind how people use information. Best of all,
>there's a huge bibliography that can get you started on finding other
>articles. (One of my favorite search tips for literature reviews: find one
>good article, and see who that author cited. Find a good article by each of
>the cited authors (or find many, if the author is working on precisely what
>you need to research), and see who _they_ cited. And so on. This approach
>leverages the effort the original author did in searching the literature,
>and progressively leverages each additional author's work.) If you're doing
>a keyword search, try "contextual inquiry", since documentation is more
than
>the sum of its parts: you need to address a raft of issues (from typography
>to reproduction quality) to make documentation effective. You also need to
>determine the "size, shape, binding, and outer appearance" for any new
>project, since all of these factors depend more on the needs of your actual
>audience than on abstract design principles. Contextual inquiry tells you
>how people actually use your documentation, and you can't design something
>appropriate until you know that. Speaking of which:
>
>Third, there's the whole issue of "convention". For most situations,
>sticking with the "standard" works just fine, and for documentation, that
>standard tends to be 7x9 inches (plus or minus a bit); this works well
>because it's large enough to use graphics effectively, but small enough to
>fit even on a moderately crowded desk beside a computer. There may be
>theoretical advantages to picking a different size, but as in studies of
>typography, "proving" that one design is statistically better than another
>may produce no increase in usability if the difference isn't also
>significant in practical terms. That being said, sometimes it really does
>pay to pick a format that's different from your standard. When I worked for
>a government forestry research institute, virtually all of our publications
>were standard North American 8.5x11 paper because we were designing for
>people (largely government and university researchers) who would be reading
>the reports at a desk or in an armchair (not at a computer), and we used
>only black ink and relatively inexpensive recycled paper to keep costs low.
>But we also published a guide to determining the state of maturity of jack
>pine seed cones that would be used in the field. To make it useful, we
>measured most of the jackets used by field researchers in our building (who
>were very representative of our target audience) to find a book size that
>would fit in a typical jacket pocket. We chose to use full color because
>many of the differences we were illustrating could not have been seen in
>black and white, and we used glossy, heavy, coated stock so the photos
would
>be clear and so that the book would survive a brief rain shower in the
>field. We won an award for the results. So, convention notwithstanding, the
>rule of thumb is "different needs, different solutions".
>
>--Geoff Hart, FERIC, Pointe-Claire, Quebec
>geoff-h -at- mtl -dot- feric -dot- ca
>
>"Technical writing... requires understanding the audience, understanding
>what activities the user wants to accomplish, and translating the often
>idiosyncratic and unplanned design into something that appears to make
>sense."--Donald Norman, The Invisible Computer
>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>Sponsored by Weisner Associates Inc., Online Information Services
>Training & consulting for RoboHELP, Dreamweaver, HTML, and HTML-Based Help.
>More info at http://www.weisner.com/train/ or mailto:training -at- weisner -dot- com -dot-
>
>Sponsored by SOLUTIONS, Inc. http://www.SolutionsEvents.com or 800-448-4230
>RoboHELP 2000 for HTML Help Seminars, Basic & Advanced, 6/28-30, Boston, MA
>Hands-on Training from Char James-Tanny, Certified RoboHELP Instructor
>
>---
>You are currently subscribed to techwr-l as: amarie -at- fpoint -dot- com
>To unsubscribe send a blank email to
leave-techwr-l-33055Y -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.





Previous by Author: Creating content for a glossary
Next by Author: Non-disclosure agreement and portfolio
Previous by Thread: Re. Documentation size & shape research?
Next by Thread: Translation services


What this post helpful? Share it with friends and colleagues:


Sponsored Ads