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.
Subject:Re: User research From:"Peter Swisher" <PeteS -at- BMGi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 14 Jan 2003 14:39:53 -0700
This type of research will be extremely valuable to your documentation and
the organization as a whole. As I write, the engineers for the product I am
working on are coding w/out any written descriptions of who the end users
are. So, as part of my doc plan, I decided to do a more detailed "Audience"
analysis.
How to do an Audience analysis is thankfully buried in the PASS (Purpose,
Audience, Subject Self) analysis section of my Rhetoric 102 books! However,
an Audience analysis is similar to a Use Case "Actor" analysis. There are
plenty of good books on Use Case design out there. For my project, I
started with a generic description of Use Case design from "Mastering the
Requirements Process" by Suzane and James Robertson. There is probably a
copy on your PMM or PDMs shelf.
This book suggests to start by making a list of the roles that people might
have in connection to your system. For each role, then consider:
What other jobs do they have?
What other life roles do they have?
What Subject Matter Expertise do they have?
What is their attitude towards their job?
What is their technical experience?
What is their attitude towards technology?
Do they normally use a computer? Yes, some people do not..
What are their intellectual achievements? (HS, BA, BS, MBA, etc.)
What is their age, gender, social class, nationality, natural language, etc?
Do they have disabilities?
What are their hobbies?
Combined with asking these questions, I am "reverse engineering" some
marketing bullet points. For example, I want to understand how
"Collaboration" actually translates into the buttons a user role will click
w/in a system.
I hope this gets you started!
- Pete
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
---
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.