Soundly RunSound familiar?

Fixed the chart, broke three teams

At 60 people, the team split into squads. It looked clean on the chart; three teams that worked well together quietly came apart.

InsteadReorgs move one small step at a time, after counting which teams depend on each other.

The video

Video planned56 secondsHow every video is made
The script
The one point
Structure moves only on a measured signal, by the smallest step; the decision record keeps the signal so it is read again six weeks on.
Why a video
Cause and effect rippling and the same moment twice: a clean redraw snaps working links between teams, then side by side, the smaller step keeps them; the founder’s click held.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘Fixed the chart, broke three teams’ on the site’s background, fading straight into the guide with no black.
    On screen
    Fixed the chart, broke three teams
  2. The moment0:03-0:11person

    Picture
    Guide in the usual place and framing, speaking to camera. Lower third: guide’s first name, ‘Soundly Run guide’.
    Voice
    At 60 people, the team split into squads. It looked clean on the chart; three teams that worked well together quietly came apart. Past fifty people, one team stops working as one, and the chart is the quickest thing to redraw.
    On screen
    Clean on the chart, broken underneath
  3. The cost0:11-0:19motion

    Picture
    Example tag top left. A tidy chart of one team; underneath, working lines between Billing, Support and Finance light up. The chart redraws into six squad boxes; three lines snap and work cards stall. No number shown.
    Voice
    Redraw the boxes and the working lines snap. Work that crossed teams stalls.
    On screen
    Example: The chart moved. The work broke.
  4. The mechanism0:19-0:37screen

    Picture
    Drawn Team screen, Example tag top left, context ‘Company crew’, cursor visible, step band prepare, review, decide. Callout 1: ‘Team of 60: six squads, or a smaller step?’, Signal: 9 days, up from 3. Callout 2: Six squads cut and Smaller step rows. Callout 3: Ade’s and Marcus’s answers, People affected row.
    Voice
    The signal goes on the decision record: work waits nine days to start, up from three. A helper counts what six squads would cut, and drafts a smaller step beside it. Ade and Marcus answer in writing.
    On screen
    Example · Six squads, or a smaller step?
  5. The decision0:37-0:45person and screen

    Picture
    Screen with Start the smaller step, Change and Pass all visible. Cursor clicks Start the smaller step, held 2 seconds. Heading becomes ‘Smaller step started: two squads’; Signal row reads ‘On the decision record; re-read 23 Nov, then decide again’. Guide in picture-in-picture.
    Voice
    You decide: start the smaller step, change it, or pass. On 23 November, the signal is read again.
    On screen
    Started. Both leads told, logged with your name.
  6. The difference0:45-0:52person

    Picture
    Guide back in the same place and framing as The moment. Inset, side by side: the six-squad chart with snapped lines, and the smaller step with the lines intact.
    Voice
    Nobody redraws the whole chart and untangles the broken work afterwards. The helper counts; you decide. It does not watch, score or replace anyone.
    On screen
    Reorgs move one small step at a time, after counting which teams depend on each other.
  7. Outro0:52-0:56sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    Fixed the chart, broke three teams

On screen as proof

  • Drawn Team screen ‘Team of 60: six squads, or a smaller step?’, tagged Example
  • Signal row: ‘Work waits 9 days to start, up from 3’, tagged Example
  • Start the smaller step click held 2 seconds, Change and Pass visible
  • Result row: ‘On the decision record; re-read 23 Nov, then decide again’

Before and after

Before
Drawn on who reports, not who works together
After
Design starts from who works with whom, day to day
Before
Every team changes at once, in one go
After
Smallest change that answers a measured signal
Before
Declared done on announcement; reopening it would look like a mistake
After
The signal read again six weeks on, then decide again

How it works

Structure moves only on a measured signal, by the smallest step, and the decision record keeps that signal so it is checked again six weeks on.

  1. Before any move, the handoffs it would cut are counted and the signal behind it is written into the decision; you decide if it goes ahead.
  2. Each affected lead answers the impact draft in writing; you pick the smallest change that works, and the decision record keeps why.
  3. Each person’s change is agreed with whoever runs people and told by their manager before any announcement; six weeks on, you read the signal and decide again.
TeamExample

Company crew · Example

Team of 60: six squads, or a smaller step?

Signal
Work waits 9 days to start, up from 3
Six squads cut
Billing’s daily loop with Support and Finance
Smaller step
Two squads first; Billing, Support and Finance stay as one
Ade, Billing
Smaller step works. Keeps our Support loop.
Marcus, Product
Two squads is enough for Q4.
People affected
14 change squad; nobody changes manager

Source: team dependency count, 12 Oct

Start the smaller stepChangePass

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.