Whether you're rolling out a new time-and-attendance system, upgrading your accounting software, or sharing the best tips and tricks on Microsoft Excel, eLearning can be a great way to get software training out to the people in your organization. But how do you approach such a project? Before recording simulations in tools like Captivate, Storyline, or Camtasia, you've got some important decisions to make. Should they just sit back and watch, or do they need to practice? Should we teach all the ways to do something or just one way? Do we really need a lesson on how to log in?

In this program, you'll look at six key design decisions you'll need to make when creating online software training. You'll tackle everything from whether to teach just the procedural steps or whether to teach underlying business rules and concepts to how to structure practice activities to provide just enough support to your learners. You'll walk away with specific tips on how to tackle issues like these:

• They don't just need to know where to click—they need to know how to make decisions and adjust their workflow.
• This needs to work for folks who know the old system, as well as people new to the organization.
• I call it a menu but my co-worker calls it a drop-down.
• A lot of this is self-explanatory, but that might not be true for everyone.
• I need to start developing but the software isn't done yet.
• You'll get to see real, live examples of different options so you can get a real sense of what the learner experience would be like and how that approach might work in your environment.

In this session, you will learn:

• To uncover the needs of your learners around software training
• How to get the right people on the team and the right access to the system you're training on
• To balance the need for "where-to-click" training with the need for business process training
• To use clear, consistent language when writing scripts or procedural steps
• Design practices with just the right amount of support and guidance
• How to adjust your process when encountering delays or changes to the software

Audience:
Designers, developers, managers

Technology discussed:
Articulate Storyline, Adobe Captivate