Soundly RunSound familiar?

Heard it with my team

Your managers learn about the reorg in the same all-hands as their teams, so they cannot answer a single question.

InsteadManagers hear first, so they can answer their teams.

The video

Video planned54 secondsHow every video is made
The script
The one point
The decision reaches each lead before their team, with a drafted brief, so they can answer at the all-hands.
Why a video
Time passing and the same moment twice: one reorg calendar played before (managers learn at the all-hands, answers weeks late) and after (decided 22 Oct, brief 26 Oct, team told 27 Oct, all-hands 28 Oct).
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘Heard it with my team’ on the site’s background, fading straight into the guide with no black.
    On screen
    Heard it with my team
  2. The moment0:03-0:10person

    Picture
    Guide seated in the usual room and framing, to camera. Lower third: guide’s first name, Soundly Run guide.
    Voice
    Your managers learn about the reorg in the same all-hands as their teams. In a company this size, news kept close for fear of leaks reaches every layer at once.
    On screen
    Guide’s first name, Soundly Run guide
  3. The cost0:10-0:17motion

    Picture
    A calendar strip. All-hands marker lights up; question bubbles rise from teams to their managers and stack unanswered as the days flip. The impact review marker lands weeks later at the far end. No figures.
    Voice
    The questions start at once. Managers have no answers yet. The impact review arrives weeks later, after doubt has set in.
    On screen
    Announced first. Answers weeks later.
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Company crew’. Heading: Brief your team before the all-hands on 28 Oct. Step band on prepare. Callout 1 on Decided (Field Ops moves to three regional hubs, Dana, 22 Oct), callout 2 on Your unit (42 people; 6 roles change site, none removed).
    Voice
    Dana decided on 22 October. Before the all-hands, Marta’s brief is drafted: Field Ops, 42 people, 6 roles change site, none removed.
    On screen
    Example: brief your team before the all-hands
  5. The mechanism0:26-0:35screen

    Picture
    Step band on review. Callout 3 on Likely questions: 8, each with a drafted answer. Cursor moves to Open question: night cover in the north hub, with Dana; then Your brief: 26 Oct, all-hands 28 Oct. Side panel shows lead briefs: Field Ops with Marta, Billing brief booked, Sales no change.
    Voice
    Her team’s likely questions come with drafted answers. One stays open, night cover in the north hub, and Dana answers it at the brief.
    On screen
    Your brief 26 Oct; all-hands follows 28 Oct
  6. The decision0:35-0:43person and screen

    Picture
    Step band on decide. ‘Tell my team 27 Oct’, ‘Change’ and ‘Pass’ all visible. Marta’s cursor clicks ‘Tell my team 27 Oct’, held two seconds. Row turns: From Marta, 27 Oct, a day before the all-hands. Guide in picture-in-picture.
    Voice
    Marta, the Field Ops lead, decides: tell my team 27 October, change it, or pass. Her team hears it from her first.
    On screen
    Set. Marta’s team hears it from her on 27 Oct.
  7. The difference0:43-0:50person

    Picture
    Guide in the same framing as The moment. Small inset replays the calendar strip: decided 22 Oct, brief 26 Oct, team told 27 Oct, all-hands 28 Oct, question bubbles answered as they rise.
    Voice
    Nobody learns the reorg from the stage any more, or waits weeks for answers. The helper drafts the brief; each lead tells their team when they choose. It does not watch, score or replace anyone.
    On screen
    Managers hear first, so they can answer their teams.
  8. Outro0:50-0:54sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    Heard it with my team

On screen as proof

  • Example-tagged screen: 42 people; 6 roles change site, none removed
  • Dates on screen in order: decided 22 Oct, brief 26 Oct, team told 27 Oct, all-hands 28 Oct
  • ‘Tell my team 27 Oct’ click held two seconds, confirmation: Set. Marta’s team hears it from her on 27 Oct.

Before and after

Before
Kept close for fear of leaks, so middle managers learn with their teams
After
Each lead gets the decision before the all-hands
Before
Change impact worked out centrally, weeks after the announcement
After
Each unit’s impact drafted for its lead the day it is decided
Before
Managers face questions they cannot answer; adoption stalls
After
Leads briefed first, with answers to their team’s likely questions

How it works

The decision reaches each lead before their team, with their unit’s impact and a briefing pack, so they brief their own people first.

  1. Once a change is decided, each unit’s impact is drafted for that unit’s lead: what changes, and for whom.
  2. Each lead gets the decision and a briefing pack before the all-hands, with drafted answers to the questions their team is likely to ask.
  3. Each lead sends any open question to the decider and chooses when to tell their team, before the all-hands.
Needs youExample

Company crew

Brief your team before the all-hands on 28 Oct

Decided
Field Ops moves to three regional hubs · Dana, 22 Oct
Your unit
42 people; 6 roles change site, none removed
Likely questions
8, each with a drafted answer
Open question
Night cover in the north hub, with Dana
Your brief
26 Oct, 9:00; all-hands follows on 28 Oct
Your team hears
From you, on a day you choose

Source: decision record, 22 Oct

Tell my team 27 OctChangePass

Built to work in the email, calendar, chat, finance and sales tools you already use.

What it never does

  • Acts alone only inside limits a person sets; asks first for anything else.
  • Reaches only what its job needs.
  • Never watches, scores or replaces anyone.