tech doc - training cooperation - interim summary

Subject: tech doc - training cooperation - interim summary
From: Erika Yanovich <ERIKA_y -at- rad -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 14 Mar 2018 09:33:20 +0000

I got quite a few on- and off-line replies with ideas, pros and cons. One of them stated âI know of no one who has effectively eliminated duplication and overlap in developing documentation and training. I do believe it can be done. [â] You are breaking ground here, and it's a very worthwhile effort.â

If so, here is a recap of what is needed and what Iâve done so far.

The task is preparing a customer-facing PDF guide that explains how to install, configure and test an entire network (tech doc dept. job) and PPT-based training sessions that explain pretty much the same (training dept. job). The network functionality showcases the latest and greatest capabilities of the network elements.

1. We (writers and trainer) discussed and aligned outlines and allocated responsibilities for all sections to respective writers.

2. A graphic artist is working on a series of diagrams with the SME.

3. We attended an SME-conducted joint training session that explained the subject matter.

4. Thanked the SME and reminded him we will also need him to review our drafts.

5. Following the training, we understood the outline should be changed, so I scheduled a meeting to discuss the changes and possible changes in responsibilities. We will also discuss deadlines, dealing with product version changes during work and a framework for periodical follow-up meetings.

6. I have set up a shared directory with all the raw materials we have gathered and [partial] drafts of deliverables.

7. Trying to find out what Training is starting with, so that the writers will start covering another area and then we can exchange drafts and benefit from each otherâs work.

My favorite part so far was the training. It was great being trained for the sole purpose of creating the deliverables (this is a high visibility project!) and I enjoyed learning the material (it reminded me why I love this profession.)

Inputs appreciated.
Visit TechWhirl for the latest on content technology, content strategy and content development |


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-leave -at- lists -dot- techwr-l -dot- com

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

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Previous by Author: RE: Impact of typos on ESL readers?
Next by Author: RE: tech doc - training cooperation
Previous by Thread: Re: The Quest for a Universal Translator for Old, Obsolete Computer Files - Atlas Obscura
Next by Thread: How to Create Technical Documents in Word - Part II

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

Sponsored Ads