In Progress

Workplace Harassment &
Code of Conduct Training

A scenario-based compliance module built in Vyond, targeting corporate employees. Uses branching decisions and real-world dialogue to drive behavior change — not just policy recall.

🎬 Tool: Vyond
⏱ Seat time: ~12 minutes
👥 Audience: All employees
📐 Format: Scenario-based + branching
Production Progress 30% complete
✓ Topic Research ✓ Learning Objectives ✓ Storyboard → Scripting Vyond Animation Review & Revise Final Export
Project Overview

Learning Objectives

Learners will recognize harassment behaviors, respond appropriately in the moment, and know how to report incidents using company policy.

Design Approach

Branching scenario with a recurring cast of characters. Wrong choices show realistic consequences before looping back — not just a "try again" screen.

Characters

Kezia — new employee (learner proxy)
Blaine — manager (antagonist)
Tomás — coworker & bystander
Bettina — resolution guide

Vyond Techniques

Character lip-sync, office environment, whiteboard prop, phone call scene, emotional expression changes, and smooth scene transitions.

Scene-by-Scene Storyboard
Full Module Storyboard

6 scenes · branching decision at Scene 3 · two consequence paths · resolution

Scene 01 🏢 Office lobby · Day 1 Scripted
Meet Kezia Introduction

Kezia arrives for her first week at a mid-size marketing firm. Narrator VO introduces her and establishes the stakes: "Every workplace has a culture. Sometimes that culture needs a defender."

🎬 Vyond: Character walks in, receptionist greets her. Pan to open-plan office. Upbeat but neutral music.
🎯 Objective: Set emotional buy-in before policy content appears.
💡 Design note: Show diverse ensemble cast early so learners see themselves in the story.
Scene 02 📋 Conference room · Training day Scripted
What Counts as Harassment? Instruction

Bettina leads a brief onboarding. Three realistic examples appear as short vignettes: a comment about appearance, exclusion from a meeting, and unwanted physical contact. Each is labeled — subtle, moderate, severe.

🎬 Vyond: Split-screen vignettes using the same office set. Narrator labels each on a clean text overlay.
🎯 Objective: Learners can distinguish behavior types before the scenario begins.
💡 Avoid legalese — frame every example as a real conversation, not a policy excerpt.
Scene 03 😬 Kezia's desk · Thursday afternoon Storyboarded
The Incident ⚡ Branching Decision

Blaine leans over Kezia's desk and makes a comment about her appearance in front of Tomás. Tomás looks uncomfortable but says nothing. Kezia feels her face flush. The scene freezes.

Learner chooses what Kezia does next ↓

🎬 Vyond: Blaine's character expression changes to smug. Kezia's expression shifts to uncomfortable. Soft freeze frame + choice overlay.
🎯 Objective: Trigger emotional recognition — this is the moment learners must name what they're seeing.
Scene 04A ✅ HR office · same afternoon Queued
Kezia Reports the Incident Correct Path

Kezia goes directly to HR and describes what happened. Bettina listens, takes notes, and explains the next steps. Tomás later approaches Kezia and thanks her for speaking up.

🎬 Vyond: Warm office lighting, Bettina nods and types. End with Kezia looking relieved. Positive resolution music.
🎯 Reinforce: "Speaking up protects you and your colleagues."
Scene 04B ⚠️ Break room · next morning Queued
Kezia Stays Silent Consequence Path

Kezia brushes it off. Over the next two scenes, Blaine's behavior escalates — now in front of a client. Kezia overhears Tomás telling another colleague they feel unsafe too. The narrator asks: "What could Kezia have done differently?"

🎬 Vyond: Slightly cooler color grade, Blaine's character posture grows more dominant across scenes. Subtle tension in music.
🎯 Show real cost of inaction — not just for Kezia, but for the team. Then redirect to the reporting scene.
Scene 05 📜 Policy overlay · narrator VO Queued
Your Reporting Options Policy Anchor

Short animated breakdown of the three reporting paths: direct to manager (if not the harasser), HR portal, or anonymous hotline. Each path animated as a simple flowchart, narrated by Bettina.

🎬 Vyond: Bettina presents at a whiteboard. Flowchart builds step by step with animated arrows.
🎯 Objective: Learners can name at least one reporting path and know it's protected.
Scene 06 🏆 Office · closing scene Queued
Resolution & Knowledge Check Closing + Assessment

Kezia is now 3 months in. The office feels different — Blaine has completed corrective training, Tomás feels safer, and Kezia mentors a newer employee. Five-question knowledge check follows, covering recognition, response, and reporting.

🎬 Vyond: Time-lapse effect (calendar pages), warmer color grade, uplifting outro music. Fade to company logo.
🎯 End on agency, not fear — learners feel equipped, not just warned.
Branching Logic
Decision Architecture
Scene 3: The Incident
Learner decision point
↓
Report it → ← Stay silent
Scene 4A
HR meeting · positive resolution
Scene 4B
Escalation · consequence shown
↓                 ↓
Scenes 5 → 6
Policy recap · knowledge check · both paths converge
Skills Demonstrated
Vyond animation Scenario-based design Branching logic Adult learning principles Instructional writing Character dialogue Knowledge check design Compliance content Storyboarding Visual storytelling