Forum Discussion
Calling all Software Simulationists
- 6 months ago
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.
So Steve, there are a lot of ways to do this. I just finished up a project with 248 slides. I divided them into different scenes on the functions they did. In what I will call the real world I would have divided these into different presentations. But my stake holders wanted it all put into one project. The other nice thing about dividing them into scenes is, you can send just one scene for review.
Cheers Eric. It's good to have confirmation on this. We certainly have more so it would be good to know what the performance is like building all of those sims from within the file.
Or do you produce separately and then bring them into the story file at the end? I doubt anyone does this option, but it would be good to know as I suspect most of our courses would be over 6-700.
We essentially capture the sims in another product, produce the Storyline shell, usually with assessment, then import the captures at the end when ready to share the first draft for review.
Related Content
- 2 years ago