Guided by Cathy Moore’s strategic action mapping process, I acted as the subject matter expert (SME) and drew from my experience in daily sustainability practices. To begin the action mapping process, I proposed a measurable performance goal for the learning experience, which is included on the left side of the action map below. 

I then identified the decisions and actions the users would need to make in a real-life situation. The process of creating an action map ensured that all of the actions relate to the overall goal of the project.

Upon recognizing the primary actions, I focused on prioritizing the crucial ones to emphasize in my learning journey. Subsequently, I crafted a textual storyboard introducing choices and their respective consequences. As users navigate through the scenario, they encounter three options: one correct choice and two distractors.

Opting for the correct action leads the user to a positive outcome, enabling them to progress through the scenario, while selecting an incorrect action exposes the user to real-life negative consequences of varying severity, accompanied by an opportunity to make another attempt. If ever a learner needs support in making a choice, they can select a mentor button that provides advice from a sustainability expert. This empowers users to decide when they want additional information rather than going to search for information outside of the course that could cause overwhelm. 

The storyboard process played a vital role in my design process, as it served as the canvas where I integrated significant instructional practices and learning theories to optimize the experience for the learners that immerses the user in the story to promote learning and retention.

Following the revision and approval of the text-based storyboard, I began the creation of visual mockups for the scenario using Figma. Leveraging Figma's flexibility, I experimented with various visual elements and layouts to achieve a polished and immersive feel.

Maintaining visual consistency across elements, from backgrounds to characters, was a priority. I established a custom color palette derived from the background illustration of my title slide, and edited each asset to match the color scheme, all within Figma.

After completing a style guide, I created a slide for each changing situation and scene in my learning experience. This included a mentor slide, a slide for question one, and correct and incorrect consequence slides. Through iterative refinement, I ensured all visual and instructional information flowed together seamlessly and was a coherent learning experience.

Satisfied with the look and feel of my mockups, I developed an interactive prototype to combine the visual mockups and text-based script. 

I used Articulate Storyline 360 to create an interactive prototype, which I had planned out visually in Figma beforehand. The prototype included the opening screen, an introduction to the scenario in which the learner meets the mentor, and the first question with correct and incorrect prompts.

With the basic framework for the rest of the project established, I shared the prototype seeking feedback on the look, feel, and overall experience of the scenario. The reception was positive and I made minor adjustments that addressed the user experience and user interface design early on in the project, such as adding audio to the checklist and removing navigation buttons as they were deemed not needed for the user to move throughout the course. 

The interactive prototype was and continues to be an essential step in the development process. It allows me to improve the experience based on user testing and feedback from the clients and community at the beginning of development, so full development can run more efficiently.

For the full development, my skills in Storyline were challenged as I excelled in completing the build of the prototype to full development. Throughout this process, I  built the additional slides, leveraging states, layers, triggers (both standard and conditional), and variables to enhance the overall functionality.

I am most proud of the consistent visual design throughout the project, which was also positive feedback I received in user testing. Even when I could not find the images I needed, I was confident in my visual design skills to create assets that aligned with the experience, such as the grocery list.