Defense Against Training Surprises (Part 2 of 2)

Joe Wynne is a versatile Project Manager experienced in delivering medium-scope projects in large organizations that improve workforce performance and business processes. He has a proven track record of delivering effective, technology-savvy solutions in a variety of industries and a unique combination of strengths in both process management and workforce management.

 

In Part 1, we began looking through typical sections of a Training Design Document, a key document in controlling activities of training designers and developers no matter how the training will be delivered. There are other areas in the document and more ways to defend yourself against costly surprises in the training function.

The Practice of Best Practices

Beware of optimistic durations listed for the units/modules of training. Actual delivery is typically longer because designers tend to underestimate the time involved in their design.

If unit/module durations are longer than appropriate for your project, take a look at how "best practices" are used. Best practices in training design usually result in plenty of interaction and learning activities. Sometimes games and small group discussions are used. Be aware that these activities add lots of time. They are meant to improve delivery rather than being make or break, so you should feel free to negotiate these out.

Unwrap the Delivery Strategy

Check that the delivery strategy corresponds to all needs described in the Scope Document. For example, was travel supposed to be minimized? If so, did the designers design classroom-intensive instruction requiring travel? The delivery scope can be forgotten like the graying goop in the fridge.

If the delivery constraints …

Please log in or sign up below to read the rest of the article.