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: Training and documentation teams play well together?
Subject:Re: Training and documentation teams play well together? From:Bill Swallow <techcommdood -at- gmail -dot- com> To:Rebecca Hopkins <rebecca_hopkins -at- comcast -dot- net> Date:Fri, 30 Mar 2012 10:31:45 -0400
Yep. We used the same tools and shared the same core content.
Conditional text allowed Documentation to keep examples and procedures
more generic while Training could use them in creating custom
scenarios based on who they were training. We spent a lot of time
meeting to determine specific style, both in writing and in structure
(not structure-structure, but formatting and general composition
rules).
All that said, reuse between departments was only about 30%. The goal
was savings in appropriateness of content, not maximization of reuse.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
