Overview

This branching scenario is inspired by the podcast, The Big One, a production from LAist that details what might happen when Southern California experiences its next major earthquake; several of the episodes are narrated in the second person. You, the listener, experience the Big One and navigate the after-effects. Much like the podcast, this branching scenario features you. When the big one hits, you are faced with a number of decisions and the consequences of those decisions. In the process, you learn a lot about earthquake preparedness.

Design & Development

Drawing from the narrative presented in The Big One, as well as the tips and tricks listed at the end of each episode, I scripted scenarios in which you, the user, experience the Big One at work, at home, and on the road. Using the script, I mapped out the numerous branching scenarios in Twine. Each passage in Twine is associated with one of four basic slide types (informational ; decision-based, end-of-simulation with consequences, and end-of simulation) which were mocked up in Adobe Illustrate.

Finally, I built out a final interactive version in Articulate Storyline 360. The project features:

• Randomized variables that reset the day and time that the disaster occurs;

• Custom images, all of which are modified versions of vectors provided by Storyset;

• Multiple different endings, some positive and some unfortunate;

• “What Went Wrong” tabs to illuminate the errors you made;

• An earthquake preparedness guide that you may review at the end of each simulation before trying again.

Design Theory

In this activity, users “learn by doing.” Rather than structure this learning experience around an “information dump" that forces users to digest loads of information prior to a traditional assessment, this activity begins with limited contextual information, then sets the user in action. This narrative-driven approach allows users to immerse themselves in the aftermath of the Big One and face the consequences of their actions.

Only after completing one simulation will users will have the opportunity to review an earthquake preparedness guide. This is optional, and users may try the activity again either way.

Reflection

This was my first attempt at a branching scenario, and I had a lot of fun with it. Initially, I found it challenging to keep track of the scenarios as I scripted them. I gained an appreciation for the complexity of the project when I began building it in Twine, so in future projects, I intend to use Twine to map out scenarios and user choices before I begin scripting them.

That said, one thing helped keep me organized and on track was a commitment to backwards planning. From the beginning, I knew the ideal outcome in this activity was for the user to be at home and inspect the house to ensure its safety while waiting for aid to arrive. By working backwards from that point, it was able to build out multiple different scenarios that funneled into this scenario, while allowing some to end prematurely.

Finally, very few free vectors speak to natural disasters and the trauma of their aftermath. While I relied heavily on Storyset's archive of images, most feature scenes of business, commerce, and traditional daily life. That meant I had to edit the SVGs in Adobe Illustrator--modifying facial expressions, mixing and matching elements, and adding things like smoke, cracks, and injuries. The experience left me with a much greater understanding of the tool. I imagine I'll run into plenty of instances in which there's a limited budget for illustrations or a lack of free and relevant images, so I look forward to continuing to build my skills in Adobe Illustrator.

Future Application

Using the skills that I learned during this project, I am confident that I will be able to develop a scenario-based training that speaks to a specific business need such as utilizing a protocol or delivering quality customer service.