Soundly RunSound familiar?

The new tool faded by spring

Launched with fanfare in January. By spring, everyone is quietly back in the old spreadsheets.

InsteadEach process has an owner who keeps it running.

The video

Video planned53 secondsHow every video is made
The script
The one point
Each core process keeps one owner after launch, who hears where work drifts back, and why, and decides what changes.
Why a video
Time passing: January’s launch to spring in seconds as work drifts back to the spreadsheet; then Priya’s own decision, her click held on the drawn screen.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘The new tool faded by spring’ on the site’s background, fading straight into the guide with no black.
    On screen
    The new tool faded by spring
  2. The moment0:03-0:11person

    Picture
    Guide in the set place, medium shot, same room as every video. Lower third appears on first appearance.
    Voice
    Launched with fanfare in January. By spring, everyone is quietly back in the old spreadsheets. In a busy company, a launch has a sponsor, but after launch day nobody owns it.
    On screen
    Guide’s first name, Soundly Run guide
  3. The cost0:11-0:18motion

    Picture
    Calendar pages flip January to spring. A launch banner fades; one by one, desk screens switch from the new tool back to the old spreadsheet. A training manual’s steps drift out of line with the work. No numbers shown.
    Voice
    Training teaches steps that drift from real work. Use is judged by logins, not by the work. The spreadsheet comes back.
    On screen
    January to spring
  4. The mechanism0:18-0:27screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Priya’s crew’, step band on prepare. Heading: Support tool, 12 weeks on: refunds are back in the old spreadsheet. Cursor walks Launched, then In the tool. Callout 1 on Back on the spreadsheet: night shift refunds and the billing queue, since March.
    Voice
    Twelve weeks on, the tool shows which work went back to the old spreadsheet: night shift refunds and the billing queue, since March.
    On screen
    Example. Refunds are back in the old spreadsheet
  5. The mechanism0:27-0:36screen

    Picture
    Step band on review. Callout 2 on Why, in their words: ‘A refund takes four screens; the sheet takes one row.’ Ari, night shift. Callout 3 on Drafted: refunds in one screen, billing queue added, by 1 May.
    Voice
    Ari, on the night shift, says why: a refund takes four screens, and the sheet takes one row. A helper drafts a plan to fix that.
    On screen
    Example. Why, in their words
  6. The decision0:36-0:43person and screen

    Picture
    Step band on decide. Priya at a desk; Approve the plan, Change and Pass all visible. Click on Approve the plan held two seconds; heading turns to Plan approved and the Drafted row turns green. Guide in picture-in-picture.
    Voice
    Priya owns the support process, so she decides: approve the plan, change it, or pass. The team is told what changes, and when.
    On screen
    Approved. The team is told what changes, and when.
  7. The difference0:43-0:49person

    Picture
    Guide back in the same place and framing as the moment, so the viewer sees a return.
    Voice
    Nobody learns in spring that the tool was quietly dropped any more. The helper drafts; Priya decides. It does not watch, score or replace anyone.
    On screen
    Each process has an owner who keeps it running.
  8. Outro0:49-0:53sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    The new tool faded by spring

On screen as proof

  • Drawn Needs you screen, Example tag: refunds and the billing queue back on the spreadsheet since March
  • Why, in their words: Ari, night shift
  • Approve the plan click held two seconds, Change and Pass visible

Before and after

Before
After launch, nobody owns whether people use it (adoption)
After
Each core process has one named owner after launch
Before
People drift back to the old spreadsheet, and nobody hears why
After
The owner hears which work went back, and why
Before
Use is judged by logins, not by the work
After
The owner sees how much work runs in the tool

How it works

Keeping it true outlives the launch: each core process keeps one owner, who hears where work drifts back, and why, and decides what changes.

  1. Each core process names one owner; the sponsor confirms that owner before launch, not after.
  2. When work drifts back to an old tool, the owner sees which work, and why, in the words of the people doing it.
  3. The owner decides what changes, in the tool or the process; the decision record keeps why, for people and AI helpers alike.
Needs youExample

Priya's crew

Support tool, 12 weeks on: refunds are back in the old spreadsheet

Launched
14 Jan · owner Priya
In the tool
Most ticket types, every team
Back on the spreadsheet
Night shift refunds and the billing queue, since March
Why, in their words
“A refund takes four screens; the sheet takes one row.” Ari, night shift
Drafted
Refunds in one screen, billing queue added, by 1 May

Source: help desk and team replies, 8 Apr

Approve the planChangePass

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.