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.
RE: More Training Discussion: Task-based lecture vs. Systems-base d lecture
Subject:RE: More Training Discussion: Task-based lecture vs. Systems-base d lecture From:"Martinek, Carla M" <CMartinek -at- zebra -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 15 Apr 2004 15:01:32 -0500
> -----Original Message-----
> From: jsokohl -at- mac -dot- com [mailto:jsokohl -at- mac -dot- com]
> More training issues...
>
> I am the doc lead for a software product. The QA person is in
> charge of
> training a new (and radically different) version. She plans
> to lecture it
> based on the menus ("The File menu contains these items..."), while I
> strongly suggested the lecture should be task based ("To
> create XX, select
> File>Option...").
>
> Sadly, and once again, I as a tech writer need an outside authority to
> validate my knowledge and experience. What I'm looking for is URLs to
> published information that training should be task-based, even if the
> training is not hands on (too many people, not enough
> equipment). While I
> have references to statements why DOCUMENTATION should be task-based
> rather than systems-based, I would love any URLs to specific
> information
> about training.
>From JoAnn Hackos' Book, Managing Your Documentation Projects: (p237)
=======
In the design of documents that the audience will use to operate,
administer, or maintain a product, a task-oriented approach to information
is essential. We know that task-oriented information
* Reduces training time
* Enhances productivity
* Decreases customer-support costs
* Increases audience satisfaction with information
However, to be presented effectively, tasks need to be studied from the
viewpoint of the audience. per haps the greatest danger for the writer is
to spend more time studying tasks from the perspective of the product than
from the perspective of the audience.
=======
You can look up Ms. Hackos' qualifications online - they're impressive, and
hard to argue with. She's one of the premier leaders in technical
communication.
*************************
Carla Martinek, Translation Coordinator/Editor
Zebra Technologies Corporation
333 Corporate Woods Parkway, Vernon Hills, IL 60061
tel: 847.793.5616 fax: 847.821.1795
cmartinek -at- zebra -dot- com
- CONFIDENTIAL -
This email and any files transmitted with it are confidential, and may also
be legally privileged. If you are not the intended recipient, you may not
review, use, copy, or distribute this message. If you receive this email in
error, please notify the sender immediately by reply email and then delete
this email.
Have you tried the latest in Help Authoring from RoboHelp?
Try ROBOHELP X5 for Free - Now with Word 2003 support, Content
Management, Multi-Author support, PDF and XML support and much more!
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -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.
