Securing Protected Health Information (PHI) Scenario-Based eLearning
This scenario-based eLearning concept project was designed to decrease the amount of Protected Health Information (PHI) lost or left unsecured in the workplace.
Account representatives are presented with real-life scenarios in which they are tasked with making appropriate decisions to properly secure PHI.
Audience: Account representatives of a medical supply company
Responsibilities: Instructional Design, eLearning Development, Visual Design, Storyboard, and Mockups
Tools Used: Articulate Storyline 360, Adobe Illustrator, Figma, MindMeister, MilaNote
The Problem
The client, a mid-size medical supply company, contacted me because they’ve observed an increase in secure information being left unsecure in the workplace.
Employees of the medical supply company receive a training on PHI during onboarding, however, they stated that the training is very brief, and the skill of properly managing PHI does not maintain over time.
As the company just completed their yearly audit, they expressed that they would like to discuss a potential learning solution to be deployed prior to their next audit.
The Solution
Since the client’s problem was hypothesized to be a skill deficit, I proposed a scenario-based eLearning solution. Employees are presented with real-life scenarios in which they make decisions and experience consequences in a risk-free environment. By engaging with real-life scenarios and consequences through an eLearning experience, the employees can then generalize these skills in the real world.
Question Slide
My Process
Throughout the analysis, design, and development process, I collaborated with a cybersecurity SME. Together, we identified a learning objective and created an action map.
Following the action mapping process, I wrote a text-based storyboard, designed visual mockups, developed an interactive prototype, and ultimately developed the final eLearning experience. This was an iterative process which included ongoing feedback and collaboration with the client, the SME, and other instructional designers.
Action Map
After the learning objective was agreed upon, the SME and I used MindMeister to create an action map by identifying which actions are required to achieve this objective. I asked leading questions throughout the action mapping process to ensure all observable behaviors were included. Then, we agreed on three key actions that the SME expressed were common errors per their observation.
Text-based Storyboard
Before designing the storyboard, I asked the SME to describe the consequences if the employee didn’t follow the three key actions that we outlined. With this information, I wrote a storyboard that included three scenarios which each included one correct response and two distractors. Additionally, I utilized one of the characters, Nina, as a mentor in which the learner can seek guidance from before selecting a response. Then, each response was followed by a realistic consequence.
As the client was reviewing the storyboard, I used Milanote to create a mood board which then inspired the style guide.
Visual Mockups
I customized visual assets found on Freepik.com by using Adobe Illustrator. Then, I designed wireframes on Figma for various slide types such as a prompt slide, question slide, Ask Nina slide, etc. Through multiple iterations, I continued to build out these slides on Figma until I received approval from the client.
Using Articulate Storyline 360, I developed the introduction slides, first two questions, consequence slides for those questions, and the mentor layers as an interactive prototype for the client to review. The client reviewed the prototype and gave feedback regarding functionality such as being able to click additional data loss hotspots resulting in an inaccurate result of the total data lost. I resolved this by placing an overlay over the hotspot and changing the state from “hidden” to “normal” when the hotspot was clicked thus preventing any additional clicks. I also continued to modify entrance and exit animations until both the client and I were satisfied with the prototype.
Interactive Prototype
Once the prototype was approved, I began to fully develop the project in Articulate Storyline 360. I used triggers, states, layers, variables, conditions, motion paths, and entrance and exit animations throughout this project. I was also mindful of creating a smooth transition when the scene or character would change throughout the project.
One part that I’m proud of is my incorrect consequence slides which prompts the user to file lost data reports before trying again. I chose this consequence because it reflects a real-life consequence but in a risk-free environment. During my initial analysis phase, I asked the SME some leading questions to lead me to figuring out what motivates employees to use the proper strategies when handling PHI. We agreed that the employee’s primary motivation is extrinsic in which they are motivated to avoid additional paperwork. By the learner making the correct choice, they are reinforced by avoiding the additional paperwork.
Full Development
I received positive reactions when sharing the final project with the client, SME, and other instructional designers. Many stated that they enjoyed how “realistic” the scenarios and consequences were. Others commented on the user interface and how “clean” and “professional” it appeared. Overall, the client was satisfied with look and interactivity of this project.
Throughout this project, I was able to further develop my visual design skills as I sourced and customized visual assets using Adobe Illustrator. Additionally, I was able to troubleshoot and find solutions for various functions in Articulate Storyline 360 such as creating a looping animation. Last but not least, this project allowed me to immerse myself in various phases of the ADDIE process and utilize strategies such as action mapping which ultimately made for a much smoother design process.