This has been the year of software training. I've been involved in I don't know how many training modules, ranging from the overly long to the shorter chunked variety.
(Remember, all I do is online, self-paced eLearning).
We've taken scenario-based approaches, so the learner can sit with an expert and watch how he does his job using the software.
We've inserted pictures of these characters to give a course more life and interest.
We've added thoughtful, process-based questions in the middle of the software demo to break things up.
Some of it's been cool stuff; some of it's gotta be grueling and not so much fun to sit through. Sometimes there's just time to make it good enough.
The next project I'm about to take on is going to be more of a just-in-time performance support tool. Short demos (some with practice) linked right from the software itself.
What have you been doing in the software training world of late?
What are your best practices?
What's working best with today's crop of software learners?
Photo credit: Hey guys, I captured the mouse! by Darwin Bell
5 comments:
Cammy, thanks for doing this! One principle that should be incorporated but often isn't is invoking, during training, the underlying 'model' of the software. For instance, in using FreeHand, I took the tutorial, but it was only later I found what I really needed, that the objects were composed of paths. Help learners see the model, show some examples of how the model explains the steps, then have them perform some tasks by predicting, from the model, how to do things. If you train the model (and I'll bet there is one), you don't have to train all the activities because it's inferable from the model. Should lead to longer retention & better transfer, on top of shorter training times. Good stuff in your other suggestions, too.
Is the "model" the same as the "process"? I'm thinking that teaching in a scenario-based mode (e.g., watching someone else do their daily tasks using the software) gets to that model point you make. Or am I missing something?
I am completely into developing training material for software products.
I primarily develop software demos that show screen captures of tasks being done on the application or tool and they are very effective for training purposes.
Simulations are also very useful when it comes to software training.
Using scenario based mode for software training is an excellent idea.
I have seen software demos that use scenarios. However I haven't seen tutorials use scenarios.
I appreciate this idea. This would make the tool or application relevant to the user.
Hey Rupa,
I almost always go with that scenario approach -- not teaching every single drop-down menu, but teaching the task-based process through a scenario. Putting the software into the context the user can understand. Let the user watch a demo and let the user interact and practice (a simulation).
What are some other tips you have for software training?
I've been thinking about how to make it more of a challenge game...
Hi Cammy
I have included some tips to create software tutorials here Quick Tips to Create Software Product Tutorials
These are some tips to create a basic software tutorial :)
Coming to your point of software tutorials as challenge games....i guess it will work well as far as it doesnt deviate from the tasks and steps to be taught to use the product :)
Post a Comment