In the last post I showed myself creating a prototype of a scenario in Twine.
Here’s the working Twine scenario. (Opens in a new window)
It’s not the whole scenario. You may not need to create the entire scenario in prototype – it depends on whether you’re using this just to give the sponsor/SME a taste of the scenario approach, or if you’re using this approach as an alternative to a full script in Word. In that case you’d develop the whole scenario.
Even this week with a new client I discovered how useful this can be if they don’t have experience of building or using scenario-based learning. In this case my task was repurposing a linear video as an elearning scenario. Although the client was able to imagine how it could be done it wasn’t until he saw a Twine version (just text, no video or stills yet) that he understood how the learning approach worked. The Twine demo took me a couple of hours to produce but it was well worth it.
The ‘working scenario’ output is one HTML file, in this case just over 250k in size, which will work on just about any browser.
Next we’ll skip from the prototyping stage to how I build this in Storyline.
Here’s the whole working-out-loud-branching-scenario series so far:
- Analysing the needs
- The learning approach
- The scenario decisions
- The situation and characters
- Prototyping in Twine (part 1)
- Prototyping in Twine (part 2)
- The full prototype (this post)