Re: Chattiness in manuals

Subject: Re: Chattiness in manuals
From: "John Cook" <john -dot- cook -at- gmail -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 17 Oct 2006 11:09:56 -0500

On 10/17/06, David Farbey <dfarbey -at- yahoo -dot- co -dot- uk> wrote:

Sarah Bouchier asked:
> How would you react to a manual that said, "The installation of this
> component may take several minutes. This would be a good time to go and
> get a cup of tea"?
>
> (Other than concluding that the author had run mad and needed to be
> fitted with a snazzy waistcoat with long sleeves, of course)

It depends. In some cases, that would be really inappropriate. But I can
imagine a scenario in which the manual was for a "laid-back", "cool"
product, and was deliberately designed to be friendly and whimsical in
order to fit into the atmosphere - the "branding" - that the product's
owners wanted to create, and then it would be fine. There's no rule
that says user assistance information must always be formal.

Scot Hacker wrote The BeOS Bible, and it was a primer for this sort of
writing. It was for a niche OS favored by hobbyists, it was
informative, but it was also casual. He wrote in plain English and
had a genuine gift for introducing complex technical concepts and
making them self-apparent with a little explanation. He feels like
like a tech-savvy older brother or mentor, giving you the straight
dope without cutting corners and without formality.

I keep The BeOS Bible on my bookshelf to this day to remind myself
what great, casual tech writing can look like in the right environment
and in the right hands.

Hacker's approach works great in some environments, but would not fly,
say, in a medical devices company. As always, know your audience.
There are places where it's possible (even desireable) to loosen up a
bit as long as one doesn't get too cutesy.
--
John Cook
Technical Writer / Help Author
john dot cook at gmail dot com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.


References:
Chattiness in manuals: From: Sarah Bouchier
Re: Chattiness in manuals: From: David Farbey

Previous by Author: Re: YATQ - Yet Another Tool Question... InDesign?
Next by Author: Re: Chattiness in manuals
Previous by Thread: RE: Chattiness in manuals
Next by Thread: Re: Chattiness in manuals


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


Sponsored Ads