new system training

Keep it Simple
I wouldn’t talk about the functionality of the system before I start – it’s a good way to confuse people…

I’d go for mapping their existing tasks/processes to the new functionality and then train to concrete examples of – “this is what you do”, “this is how you will do it” – with lots of room for practice and repetition.

Don’t show them confusing process maps, don’t show them diagrams of system interaction, definitely don’t train from PowerPoint… just focus on how they will do their jobs using the new system.

If you keep it simple, it should be simple for them to learn.

Exercises of having them map their tasks to the keystrokes/mouse clicks are more valuable – getting them to write things down is a valuable memory aid.

And make sure your User Guide/Training Manual for delegates follows the same structure. How do I do this? Oh, like that.

The worst systems courses always focus on system interaction, who the system manufacturer/developer is, how much the company spent, how easy it will make people’s lives. Essentially trying to sell the benefits as though people had any choice in adopting it once it’s reached this stage.

One Response

User deleted says:

February 3, 2009 at 1:08 pm

Keep it Simple
I wouldn’t talk about the functionality of the system before I start – it’s a good way to confuse people…

I’d go for mapping their existing tasks/processes to the new functionality and then train to concrete examples of – “this is what you do”, “this is how you will do it” – with lots of room for practice and repetition.

Don’t show them confusing process maps, don’t show them diagrams of system interaction, definitely don’t train from PowerPoint… just focus on how they will do their jobs using the new system.

If you keep it simple, it should be simple for them to learn.

Exercises of having them map their tasks to the keystrokes/mouse clicks are more valuable – getting them to write things down is a valuable memory aid.

And make sure your User Guide/Training Manual for delegates follows the same structure. How do I do this? Oh, like that.

The worst systems courses always focus on system interaction, who the system manufacturer/developer is, how much the company spent, how easy it will make people’s lives. Essentially trying to sell the benefits as though people had any choice in adopting it once it’s reached this stage.