Soundly RunSound familiar?

Monday's priority, Thursday's maybe

One big customer call on Tuesday, and Thursday's plan is rewritten. Nothing shows what the change pushes aside.

InsteadA priority changes on purpose, and everyone sees it.

The video

Video planned56 secondsHow every video is made
The script
The one point
A priority changes on purpose: affected leads answer first, the decider sees this quarter’s off-cycle count, and the reason is logged.
Why a video
Cause and effect rippling: one Tuesday call visibly pushes work back across Platform and Growth, Monday to Thursday in seconds, then the owner’s own click held on screen.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘Monday's priority, Thursday's maybe’ on the site’s background, fading straight into the guide with no black.
    On screen
    Monday’s priority, Thursday’s maybe
  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
    One big customer call on Tuesday rewrites Thursday’s plan. At this size, changes travel by hallway, not on paper.
    On screen
    Thursday’s plan, rewritten by Tuesday’s call
  3. The cost0:11-0:19motion

    Picture
    A week strip, Monday to Thursday. A call icon drops on Tuesday; ripples spread into Platform and Growth paths. Their cards slide back; half-done cards turn grey and stack up with no counter beside them. No number shown.
    Voice
    Watch one call travel. Platform’s work slides, Growth’s onboarding waits, and half-done work piles up, uncounted.
    On screen
    What one call pushes aside
  4. The mechanism0:19-0:37screen

    Picture
    Drawn Priorities screen, Example tag top left, context ‘Company crew’, cursor visible, step band prepare, review, decide. Callout 1: Asked for, offline mode in the mobile app, from a customer call, Tue 13 Oct; Pushes back, 3 priorities across Platform and Growth. Callout 2: Ravi’s and Theo’s answers. Callout 3: This quarter, 2 off-cycle changes so far, and the drafted reason.
    Voice
    Before anything moves, a helper drafts the cost: three priorities across Platform and Growth. Ravi and Theo answer in writing. Two off-cycle changes already this quarter; this would be the third.
    On screen
    Example · Third off-cycle change this quarter?
  5. The decision0:37-0:45person and screen

    Picture
    Screen with Move offline mode up, Change and Pass all visible. Cursor clicks Move offline mode up, held 2 seconds. Heading becomes ‘Offline mode moved up; third this quarter’; This quarter row reads ‘3 off-cycle changes this quarter, each with its reason’. Guide in picture-in-picture.
    Voice
    The list’s owner decides, every answer and the count in view: move offline mode up, change it, or pass. Reason, cost, name and date go in the decision record.
    On screen
    Moved. Logged with your reason and name.
  6. The difference0:45-0:52person

    Picture
    Guide back in the same place and framing as The moment.
    Voice
    Nobody learns of a switch from their own team, or counts half-done work by hand, any more. A helper drafts; the list’s owner decides. It does not watch, score or replace anyone.
    On screen
    A priority changes on purpose, and everyone sees it.
  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
    Monday's priority, Thursday's maybe

On screen as proof

  • Drawn Priorities screen ‘Third off-cycle change this quarter?’, tagged Example
  • Ravi’s and Theo’s written answers, tagged Example
  • Move offline mode up click held 2 seconds, Change and Pass visible
  • Result row: ‘3 off-cycle changes this quarter, each with its reason’

Before and after

Before
Reprioritised in a hallway, never written down
After
Every change recorded with decider, reason, cost and date
Before
Leads learn of the switch from their own team
After
Each affected lead answers before the decider moves anything
Before
Half-done work piles up, uncounted
After
Off-cycle changes counted this quarter, in view at each new one

How it works

Every reprioritisation goes in the decision record: its cost drafted, leads heard, reason kept.

  1. Before anything moves, a helper drafts the cost: what the change pushes back and which leads it touches.
  2. Each affected lead reads the draft in Priorities and answers: works, works if, or cannot.
  3. The list’s owner decides with every answer and this quarter’s off-cycle count in view; reason, cost, name and date go in the decision record.
PrioritiesExample

Company crew

Third off-cycle change this quarter?

Asked for
Offline mode in the mobile app, from a customer call, Tue 13 Oct
Pushes back
3 priorities across Platform and Growth
Ravi, Platform
Works if the API rework moves to November.
Theo, Growth
Onboarding slips three weeks. Can live with it.
This quarter
2 off-cycle changes so far; 5 half-done items parked

Reason: two renewals this quarter depend on offline mode. Revisit at the January planning.

Source: planning board, 16 Oct

Move offline mode upChangePass

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.