Re: audience analysis resources

Subject: Re: audience analysis resources
From: Keith Hood <klhra -at- yahoo -dot- com>
To: Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com>, Stuart Burnfield <slb -at- westnet -dot- com -dot- au>
Date: Tue, 13 Oct 2009 22:51:24 -0700 (PDT)

I read that review and frankly, I'm a little confused. The review author talks about Part I of the book being about how to find out what the users *really* need. Here's a quote about what the book is about:

"...the authors' purpose is to introduce techniques of user and tasks analysis so that folks ranging from software designers to technical communicators can use them to inform their design activities. "

(I won't bother to ask how someone "informs" his design activities.)

Below are some excerpts from the review, about the things covered in the various chapters:

* the importance of understanding the characteristics of potential users, their tasks, and their environments.
* the ways in which the users define themselves and their roles (e.g.,
jobs, tasks, and tools they use).
* analysis of users' work that is to be supported by an application.

So, this book is all about finding out what the users are *really* like and what kind of work they *really* do. It looks to me more like this is what I've always thought of as requirements analysis.

So, your opinions...Is this audience analysis supposed to be something separate from requirements analysis, or is one of them just an aspect of the other, or are they separate things that have some degree of overlap?

--- On Wed, 10/14/09, Stuart Burnfield <slb -at- westnet -dot- com -dot- au> wrote:

> From: Stuart Burnfield <slb -at- westnet -dot- com -dot- au>
> Subject: Re: audience analysis resources
> To: "Techwr-l" <techwr-l -at- lists -dot- techwr-l -dot- com>
> Date: Wednesday, October 14, 2009, 1:35 AM
> Mark Osborne recommended a book by
> JoAnn Hackos, "Standards for Online Communication." I
> haven't read this one but JoAnn collaborated with Ginny
> Redish on a later book, "User and Task Analysis for
> Interface Design". It's terrific, and I think you'll find it
> even more useful. Don't worry about the interface design
> part in the title; it's just as applicable to tech writing.
> TOC:
> A review:


Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

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

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:


Re: audience analysis resources: From: Stuart Burnfield

Previous by Author: OT: about the odesk web site
Next by Author: Re: #5 on the list of Low Stress Jobs
Previous by Thread: Re: audience analysis resources
Next by Thread: RE: audience analysis resources

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

Sponsored Ads