Map the change to real tasks
List who is affected and what each group does differently. A new handover process might change how one team submits a request and how another acknowledges it. If the film addresses everyone as though they perform the same task, some viewers may follow instructions meant for somebody else.
Decide whether one shared introduction and separate task explanations would be clearer than a single dense programme. The purpose is to reduce ambiguity about the next action, not merely to announce that the organisation is changing.
Stabilise the message before production
Ask the process owner to approve the effective date, affected teams, required action, transition arrangements and source of support. Mark any unsettled detail as unresolved in the brief. Do not use polished visuals to make a provisional decision appear final.
Create a version note in the production record so reviewers know which approved source the script represents. Wrong Opera provides creative approval gates and project review; the team should still define who has authority to approve the underlying organisational message.
Change: [specific process].
Applies to: [affected audience].
Begins: [approved date].
Before: [old task].
After: [new task].
Help: [approved contact or document].
Still undecided: [items excluded from final narration].Show the difference through one complete example
Build a fictional scenario around a representative task. Show the old point of confusion briefly, then spend most of the film on the new action and its result. Avoid a long catalogue of past mistakes; viewers need enough context to act correctly now.
At Board, check whether labels and transitions make the before-and-after distinction visible. At Voices, review dates, names and process terminology. If the explanation relies on a literal interface, use verified reference material and confirm the appropriate capture or finishing workflow.
- Make the affected audience explicit in the opening.
- Keep the required action visible near the ending.
- Include an approved place to find detailed instructions.
Test for practical misunderstandings
Ask representatives of the affected groups three questions: does this apply to you, when does it start, and what will you do differently? A film can feel clear while leaving one of those answers ambiguous. Use their responses to revise the specific scene or line responsible.
Before sharing the final version, compare it with the approved source and confirm the support destination is ready. Track real follow-up questions after release. Do not describe reduced confusion or improved adoption as achieved outcomes unless your organisation has measured them.
Questions & answers
Should every internal announcement become a film?
No. A short written update may be enough for a simple date or detail. A film is more useful when a sequence of actions, a scenario or a visible comparison helps people understand the change.
Can we revise the film if the rollout changes?
Plan for a revision by keeping the approved source, script and relevant shot decisions organised. Confirm the specific production and delivery steps required before promising an immediate replacement.
Evaluate the workflow with your production team.