Cybersecurity Essentials at Work
Audience
Non-technical employees in any workplace. People who use email, chat and shared files all day but have never been shown what an attack looks like from the inside of their own inbox.
The gap
Security training tends to teach rules people already agree with. Most employees can say “don’t click suspicious links” long before they can spot one on a busy Monday morning, when the email looks like it came from IT and the mailbox is about to be deleted in two hours. The gap isn’t knowledge, it’s recognition under pressure, and the willingness to admit a mistake once it’s made. Long, technical compliance courses can’t reach that, because they describe threats in the abstract instead of showing them in the places people actually work.
The approach
Rather than listing threats, the course follows one employee, Sara, through a single working morning. She clicks a fake mailbox warning at 8:55 and enters her password. Each lesson picks up that same story: what the attacker does with her password, how MFA stops them, how she handles a pressured request to send client data to a personal account, and what she does at 10:30 when she realises the email was fake. The learner sees one ordinary click become either a breach or an early warning, depending on what happens next.
What success looked like
Success was defined by what learners do, not what they can recall. A learner should finish able to spot the warning signs in a message, confirm requests through a separate channel, and report a mistake quickly instead of hiding it. The final quiz is built around that: eight scenario-based questions, two per objective, each asking what to do in a situation rather than what a term means.
Role
Instructional Designer, Content Developer
Tools
Articulate Rise 360, Gemini
Timeline
20 Minutes
Audience
Non-technical employees across workplace roles
Design approach
The course is six Rise lessons: a short welcome, four lessons built around one habit each, and a graded final quiz. Each habit lesson follows the same rhythm: a plain-language definition, an interaction that shows the idea in context, and a check that asks the learner to apply it.
Sara’s story is the thread that holds the lessons together. Because every lesson returns to the same morning, the four habits read as one connected response to one incident rather than four separate topics. The story closes in the final lesson, where Sara reports within minutes and the team blocks the attacker before any data is taken. Reporting is the ending deliberately: everything before it can fail, and the course still shows a good outcome when someone speaks up quickly.
Key decisions
Show the threat on a real-looking message. The phishing lesson opens with the exact email Sara received, built as a labelled graphic under a fictional brand. Five markers reveal the sender trick, the urgency, the generic greeting, the disguised link and the password request. Learners find the red flags where they would actually appear, not in a bulleted list.
Practice before the quiz. Each habit lesson includes a low-stakes check: sorting six messages into suspicious or safe, flipping password myths into facts, and making one data-sharing decision in a short scenario. Wrong choices in the scenario explain the risk and send the learner back to try again, so practice teaches rather than penalises.
Restricted navigation with purposeful gates. Continue blocks after each interaction require completion before moving on. This keeps the story in order and makes sure no learner reaches the quiz having skipped the practice it depends on.
Reporting framed as safe, not shameful. The final lesson states plainly that no one is blamed for reporting honestly and that waiting is the real mistake. The closing line, “Pause. Check. Report.”, gives learners three words to carry back to work.
Challenges
The main one was working within Rise’s fixed block types. Ideas I would normally build freely in Storyline, like tracking choices across lessons, had to be expressed through Rise’s native interactions instead. Carrying the story across lessons solved this: continuity came from the narrative rather than from variables.
The second challenge was keeping security content accurate without overwhelming a non-technical audience. Every term, from smishing to MFA fatigue, is introduced through something Sara experiences, and anything that didn’t support one of the four objectives was cut.
Storyboard
See the design plan behind this course, including screen-by-screen layout, narration, and interaction notes.
View storyboard (PDF) →