Missing Link Found in Dirty Laundry
gantthead project management archeologists have picked through the remains of many projects, and--amidst much dirty laundry--have determined that many failures in training can be traced back to a single deliverable, and to how that deliverable was used by the project manager.
It doesn't matter whether you are training your project workforce in new software or training users in the new application being produced by your project, there is a process to follow to get the results you want without costly errors and rework. One key deliverable in the process is the design document.
Know It When You See It
The training design document goes beyond the training scope document to add much more detail. Still, it is not so much detail that your eyes will glaze over when you review it. It should be enough for you and other stakeholders to see that training development will proceed appropriately.
-
The design document should show the performance objectives. Performance objectives are what users should be able to do, what features and functions they will be able to use.
-
The design document should show the layout and flow of training. This is not simply a detailed outline. You should see placement and descriptions of activities, practices and simulations. Durations for any segments of the training should be specified.
-
The design document
Please log in or sign up below to read the rest of the article.




