Forum Discussion
Calling all Software Simulationists
There are several options here and depending on the stakeholder's requirement I will do one of these.
Option 1. I will build a storyline project on one function. Make sure it works, test and have the stakeholder review and approve. This can now be used as a standalone project. Quick and can be used as a review by learners when needed.
Option 2. Use the above project as a scene and import these slides into a bigger project. I keep it as standalone for changes as needed down the road.
Option 3. Take all my standalone projects and put them in a learning path on the LMS.
A lot depends on your stakeholder's and what they want. In reading your post, I think option 2 will work the best.
Good luck.
Hi Steve,
Great question. Definitely use multiple scenes.
I create very lengthy simulations with multiple steps, including integrations with other systems.
- I start off the course with a high-level "big picture" overview of the complete process.
- For example, perhaps the complete process has 9 "big steps" with multiple individual steps within each.
- I create separate scenes for each of the 9 "big steps" in the process. Scenes make the menu structure much easier to manage.
- At the start of each scene, I show the "big picture" process again, reminding users what they've completed and what's next.
- Creating an easy-to-understand visual for the complete process is essential! Not only do we use the visual in the training, but we also leverage it for job aids, communications, etc.
Hope that helps. Best wishes!
Thanks Debbie. Much appreciated and totally makes sense to have the summary overview before the split into the scenes.