Soundly RunSound familiar?

One person knows how it works

One person knows how the billing system really works. When they are away, month-end waits.

InsteadHow the work runs is written down, so the person who knows it can take a holiday.

The video

Video planned58 secondsHow every video is made
The script
The one point
How the work runs is written down and a backup has run it once, so the person who knows it can take a holiday.
Why a video
The same moment shown twice: month-end with the one person away, before and after. Time passing: days of waiting compressed into seconds.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘One person knows how it works’ on the site’s background, fading straight into the guide with no black.
    On screen
    One person knows how it works
  2. The moment0:03-0:11person

    Picture
    Guide in the usual place, medium shot. Lower third: guide’s first name, Soundly Run guide.
    Voice
    One person knows how the billing system really works. When they are away, month-end waits. As a company grows, a process one person built stays in their head.
    On screen
    When they are away, month-end waits
  3. The cost0:11-0:19motion

    Picture
    A month-end calendar; days tick past while invoices stack beside one empty chair. No numbers.
    Voice
    Nobody wrote it down, because writing it takes longer than doing it. So every time they are away, the invoices wait too.
    On screen
    Writing it takes longer than doing it
  4. The mechanism0:19-0:28screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Grace’s crew’. Heading: Confirm Iris as backup for billing month-end. Step band on prepare. Callout 1 on Run only by: Pete. Callout 2 on Written steps: 14, from Pete’s last three runs.
    Voice
    Only Pete has ever run billing month-end. Its steps are written from his last three runs, and Grace, who owns it, named Iris as backup.
    On screen
    Example: confirm Iris as backup for billing month-end
  5. The mechanism0:28-0:37screen

    Picture
    Step band on review. Callout 3 on Practice run: September month-end, run by Iris from the written steps. Cursor moves to Corrections, then Who can run it.
    Voice
    Iris ran September’s month-end from the written steps, with Pete beside her, and fixed two steps that were wrong.
    On screen
    Run once by Iris, from the written steps
  6. The decision0:37-0:46person and screen

    Picture
    Step band on decide. ‘Confirm Iris as backup’, ‘Change’ and ‘Pass’ visible. Grace clicks Confirm; held two seconds. Heading turns: Billing month-end has a backup. Guide in picture-in-picture.
    Voice
    Grace owns the process, so she decides: confirm Iris as backup, change it, or pass. Confirmed.
    On screen
    Billing month-end has a backup
  7. The difference0:46-0:54person

    Picture
    Month-end replayed with Pete away: Iris runs it from the written steps, the chair no longer empty. Then guide, same framing as The moment.
    Voice
    Nobody waits for one person to come back to close the month any more. A helper drafts the steps; people run them and correct them. It does not watch, score or replace anyone.
    On screen
    Same month-end. Nothing waits.
  8. Outro0:54-0:58sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    One person knows how it works

On screen as proof

  • Drawn card, tagged Example: Confirm Iris as backup for billing month-end
  • Practice run: September month-end, run by Iris from the written steps
  • Confirm click held two seconds; Who can run it reads Pete and Iris

Before and after

Before
How it runs lives in one head; writing it takes longer than doing it
After
Procedure written from the work itself, updated each run
Before
Nobody sees only one person can run it until they are out (key-person dependency)
After
Any process only one person has run is flagged
Before
A backup is named on paper but has never run it
After
The backup runs it once from the written steps

How it works

How work runs is kept true on the Team page; each critical process has a backup who has run it.

  1. Each process is written from the work as it runs; whoever runs it corrects the written steps.
  2. A process only one person has run is flagged to its owner, who names a backup to run it once from the written steps.
  3. Once the backup has run it and fixed any step that was wrong, the owner confirms them as backup.
Needs youExample

Grace’s crew

Confirm Iris as backup for billing month-end

Run only by
Pete, every month since March 2024
Written steps
14, from Pete’s last three runs
Backup
Iris, named by you, Fri 25 Sep
Practice run
September month-end, run by Iris from the written steps, 1 Oct
Corrections
2 steps fixed by Iris; Pete checked them
Who can run it
Pete; Iris once you confirm

Example · Source: Team page, 2 Oct

Confirm Iris as backupChangePass

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.