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.
> ...I'm currently writing my diploma thesis ... about
> minimalist manuals (the concept by John M. Carroll) compared
> to "ordinary" manuals...
> What I would like to know:
> 1) Is minimal design discussed in this list ? Is it a topic or not ?
> 2) Does anyone know of good examples of minimal manuals
> that can be bought or
> looked at online ?
Minimalism comes up as a topic here from time to time. But it's
been my experience that minimalism is generally misunderstood and
much maligned. Whenever information is missing or incomplete and
whenever a writing style becomes choppy and ungrammatical, someone
moans "d*** minimalism".
I'm not sure why minimalism hasn't been more globally embraced by
the TW community. Maybe because it began life as an instructional
design technique and the transition to user manual technique isn't
necessarily straight forward? Maybe because the technique was never
reduced to the "cookbook" formulas put forth by other techniques
such as information mapping? But I find that the myths that Carroll
tries to disspell in _Minimalism Beyond the NF_ are, for the most
part, alive and well and thriving in TWing.
OTOH, some minimalist techniques have been so thouroughly adopted
by TWs that they are thought of as "conventional wisdom" or "standard
practice". Witness Geoff Hart's response to a post asking how much
users need to be told:
<begin quote from Geoff>
The standard rule of thumb for such things is emphasize only one way to do
things in the text, but provide a list of shortcuts and alternatives
somewhere (typically in an appendix or a separate topic in the online help).
I'd wager that maybe 25% of us know that this is a minimalist technique.
(Well, more now that I've spilled the beans, huh???<g>).
I've been a proponent of minimalism since I first read an article by
John Carroll in the mid-80s. I was working as a trainer at the time and
embraced his work wholeheartedly. While I can't provide an online manual
sample, I'd be happy to try to dig something up if you'll contact me off
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.