RE: Order of tasks in task-based documentation

Subject: RE: Order of tasks in task-based documentation
From: "Steve Hudson" <steve -at- wright -dot- com -dot- au>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 27 Mar 2001 10:22:29 +1000

A very formal breakdown sees minor (sub-topic) headings like these:

Considerations (whack config stuff in here)
Prerequisites (must do's pre steps below - skills/knowledge required etc)
Procedure (ye olde steps)

I think I would tend towards separating the config instructions and the
usage instructions completely and cross-reference to each other - eg:

This sets the configuration to enable the functionality of SETUP.
Blah blah how to config

This requires the configuration described in CONFIG.
Blah blah how to setup

Steve Hudson
Lead Technical Writer
Wright Technologies (Aus)
steve -at- www -dot- wright -dot- com -dot- au
(612) 9518-1822
The best way to predict the future... is to create it!

-----Original Message-----
From: bounce-techwr-l-62124 -at- lists -dot- raycomm -dot- com
[mailto:bounce-techwr-l-62124 -at- lists -dot- raycomm -dot- com]On Behalf Of Bevan
Sent: Monday, 26 March 2001 21:10
Subject: Order of tasks in task-based documentation


just wondering what people's opinions are on ordering sections in a manual.
I'm writing task-based documentation, and there are a variety of tasks that
have to be done in order to use our software. Our software lets you build an
application. I think it is most likely that users will jump right in and
start drawing windows, placing controls on them, etc (call this step 5). But
actually there is some configuration information which I want the users to
set first (call this steps 1-4). This configuration stuff can be done later
- after step 5, but I think it is good practice to do it first, and I want
the documentation to be arranged so as to encourage people to do steps 1 to
Also, for the people who look at the documentation before starting work,
they will be shown the correct way to do things.

So, in the contents, I could put the tasks in the order that people will
actually do them, or in the order that I want them to be done.
Every time I consider it I think it's "six of one and half a dozen of the
other", but I am tending towards the "best practice" model.


*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available 4/30/01 at or info -at- devahelp -dot- com

A landmark hotel, one of America's most beautiful cities, and
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.

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 for more resources and info.

Previous by Author: RE: Feeling tense about tense - a call for examples please
Next by Author: RE: ISO Document Control for Outside Authored Manuals
Previous by Thread: Order of tasks in task-based documentation
Next by Thread: Help Needed

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

Sponsored Ads