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 have a good book; however, it's still packed from a move. ;+) Task
analysis (TA) is pretty straightforward, so it's not really a problem
finding a "good" book on the subject.
I took a one week intensive course on TA when I was completing
certification as a course developer. We had TA worksheets which helped
break the job down into its components.
Basically you're looking for the least common denominator of any task
(e.g., ability to type or knowledge of Word95 and PowerPoint), the
things without which the job cannot be done. Then you move up from there
to the more knowledge-based skills/activities.
You're mapping the dependencies and categorizing the skills or
activities based on whether they require simple capability (typing or
using a computer application), or acquired knowledge, all the way up to
analysis and judgement to complete them. The worksheets began with the
simple skills and moved on up through the various steps to the completed
job while moving up the skill ladder.
It sounds complicated, but once you have taken the time to sit with
your SME (or reviewed your own tasks if you're the SME) it becomes
easier. Most books will give you a grid to help you decide where on the
skill ladder various kinds of tasks belong. You can go crazy trying to
follow them, but don't sweat the small stuff.
The main point is to see how the ability to compete a task successfully
is built from the simple to the analytical. It's the kind of thing tech
writers do all the time, but it's codified and standardized (kind of
like the Info Mapping style which is so popular).
If I come across my book any time soon, I'll email you with the
citation.
Good luck,
BJ
Thomas Quine wrote:
>
> Can anyone recommend a great book on task analysis?
>
> Has anyone used task analysis as a basis for documentation? How did you
> do it?
>