This scene depicts a Team without Trust. Unlike the dysfunctional team they portrayed, this group of actors had terrific chemistry and were incredible to work with.

Five Behaviors Team Development Video Update

My Role
  • Full-stack producer
  • Lead editor
  • Scriptwriter
  • Learning design
Year
  • 2024-2025
Tools
  • Final Cut Pro X
  • Motion
  • After Effects
  • ChatGPT
  • Lottie

Strategic Overview & Impact

I updated the video assets for The Five Behaviors Team Development training. I rewrote 10 scenarios that depicted what it looks like when a team is struggling with one of the behaviors and what it looks like when they get it right. These scenarios now reflect modern workplaces, sound more authentic, and offer deeper learning. In total, I wrote, produced, and edited about 20 minutes of new content.

AI as a Strategic Partner

I used AI as a research tool to verify industry-specific workflows, check scripts for potential bias, and confirm alignment with core learning objectives. I also evaluated the likability of the characters and used that information to ensure characters were balanced in how often they exhibited “wrong-way” versus “right-way” behaviors.

Scene number
Emojis represent the characters likability along a scale of 1 to 7.
I asked Chat GPT to give me three words that describe that person in the scene. While I did want to have that information, it was just one of those little guardrail checks I put in to make sure the AI hasn’t started hallucinating. AI and my prompting skills have come a long way, but I still include content validation checks because its useful, easy, and tells you a lot.

Strategic Asset Consolidation

I recommended that we replace the dated Team Development intro with the Personal Development intro (which I had also created) since the two programs were now being sold together. I used the time and money I saved to update and upgrade the motion graphics.

Preservation Strategy

I determined that Patrick Lencioni’s core segments remained high-value. I preserved these assets so I could focus production resources only on necessary updates, such as lower thirds and the new scenarios.

This project reinforced how important it is to know when not to redo something. Sometimes the best content decision is recognizing what already works.