Having gone through the stages of specifying the characters and the decisions we want them to make, we reach the stage of creating a first draft. This is where many designers will opt for a script in Word, either of their own volition or because their customer demands it. And that’s fine. But it doesn’t bring it to life in the way a prototype does.
Here’s the first of two passes through the scenario using Twine. In this pass, we create the ‘best’ route, in other words the path someone will take if they make the best decision each time. To a degree I’m trying to recreate an experience I never had here, as I didn’t have Twine when I first designed this scenario with Jackie. But we did use Quandary, a similar tool.
I realised when I’d finished this video that I’ve missed something out in Twine – giving each screen an identifier visible on the screen – even something as simple as p1, p2 etc. This makes it easier for reviewers to comment back to you.
For more on the tool itself, see my earlier post on Twine.
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 (this post)