Like I said -- there's a difference between technical documentation and training. When training technical content, absolutely make full use of the technical documentation available and teach people how to make full use of it -- all the better that it's on-line!! The training should be about helping people learn to use the application (or whatever it is) and apply it to their jobs/lives. Designing training is about designing learning experiences and, by all means, using the documentation (and other resources) available. It should not be about writing training manuals.

Example -- I could have written pages and pages about each of my company's products. Instead, learners meet with subject matter experts to gain the knowledge and write their OWN text about each product. To demonstrate understanding in class, they participate in a multitude of activities, including presenting "commercials" of their own design about the products. No training manual needed and at least 24 hours of design/development time saved (not to mention human resource time saved as there was no writing, reviewing, editing, debating about content, etc. needed).

This message has been edited. Last edited by: Laura L,

Alicia,

You may want to try

http://www.leaderguidepro.com/

It allows you to convert word to leader and participant guide and powerpoint slides.

I've not tried it but they offer a free demo.

Valarie A. Washington
Knowledge Broker
Think 6 Results
http://www.think6results.com

I interviewed a person that worked for a large bank and they used a program called LeaderGuide Pro. She said you input your information for a Leaders guide (classroom instruction and all). You can then (supposedly with a click of a button) create a participants guide and a powerpoint presentation. The end product was very professional looking. I wanted to use it, but it is not compatible with the way our network is set up.

I couldn't agree with you more!! Whenever I hear that people want a "training manual" created, I always ask whether they really mean "technical document" or "technical manual" or "reference manual". I typically end up having to explain the difference ;-) But, I've found it is well worth the time to lay out in the beginning.

I'd have to disagree with those who say avoid Framemaker. It's great and it does not try to "out think" you like MS Word does.

However, I would suggest getting professional training on the software, especially how to create templates. We were trained by Koster Associates at http://www.koster.net/