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:Training and Documentation From:MSTSACX -at- GSUVM1 -dot- BITNET Date:Tue, 7 Jun 1994 10:59:35 EDT
The skills needed to succeed in developing training and documentation are
nearly identical. That's why people so routinely jump between the two
fields.
Having had worked in both training and documentation, and having had
received formal educations in both fields, the primary difference seems
to be the focus. Training methodology stresses planning and evaluation;
documentation methodology stresses implementation.
No, training modules cannot be used as-is in documentation and vice-versa,
but the amount of change needed to turn one into another isn't all that
great. The model that Tim Pera showed is nothing more than a model for
mastery learning (based on Bloom's nine events of learning) adapted for use
in documentation.
"
Saul Carliner
Information Architect
mstsacx -at- gsuvm1 -dot- gsu -dot- edu 404/892-3945
