Presentation: Best Practices for Implementing Immersive Simulations
(Came in late - first person networking)
- The 'big idea' (what is your hook)
- Defining it
- Project team
- Vendor Selection
- Design it
+ Paper mock-ups important, incl. storyboarding. Mistakes on paper cheap
- Build it
+ Build to work, then build pretty
+ 20: 80 rule. For immersive learning, at least 80 percent of the project needs to be done before you can show the client.
+ Build for learners, not gamer
+ Make sure you have time to do iterative process.
- Manage it
+ Beware of feature creep. Once see it - people's imagination going.
+ Document and sign off everything
+ Disciplined change management processes important. Make very clear implications of changes.
- Test it
+ Define testing regimes at start
+ Test logic before coding (because this is what the end user sees)
+ Test from usability, learning design, IT compliance (incl. LMS)
+ Run through QA separately - typos, visuals, branding, compliance.
+ Final testing - very important to get fresh eyes
- Pre-sell it
+ Launch that it's coming.
+ Video (coming soon - around 90%)
+ Competitions and high score chart (if fits corporate environment)
+ Identify internal advocates
- Support it
+ Dummies guides
- Deploy it
+ Is it going into LMS
+ Access control?
+ Compliance reporting issues
+ Level of data needed for assessment?
+ Remember: IT needs to protect the IT infrastructure. TLC required.
+ Online preferred, but CD/DVD may be one option.
- Review it
+ Project post-mortem
- Measure it
+ What was the success factor? Did it meet it>
+ Use industry standard measurement approaches. Esp the ROI!!!!
+ Get the proof to justify the next project.
- Decision by committee - avoid like the plague
- Skimping on the design
- Diluting the design - accomomodating too many viewpoints creates confusion and waters down the results
- Treat sims as 'content' - there are fundamental differences between the 2. Simulation is how you bring the content together.
- Changing design during development - project suicide
- Failure to communicate
- Not allowing time for testing - VERY important to see whether it behaves the way you want it to.
Some white paper resources from Pixelearning.