Soundly RunSound familiar?

Delegated, then overruled

You gave Owen vendor choice for his team in March. You have overruled him four times since, so he asks you first again.

InsteadWhat you delegate stays delegated, unless you take it back on the record.

The video

Video planned52 secondsHow every video is made
The script
The one point
A decision right written down but overruled again and again stops working; the decision record shows who decided against who should, and the founder settles it.
Why a video
Cause and effect: four small overrides turn into a team lead who asks first again. Then the gap shown on screen, and the founder’s own click.
  1. Intro0:00-0:03sting

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

    Picture
    The guide in the usual place and framing. Lower third with first name and ‘Soundly Run guide’.
    Voice
    You gave Owen vendor choice for his team in March, and have overruled him four times since. A growing company hands calls down while the founder still sees every one.
    On screen
    Overruled four times, so he asks first again
  3. The cost0:10-0:17motion

    Picture
    Example tag top left. A vendor card leaves one desk with a tick. A hand from another desk swaps the tick for a different vendor. It happens again, and again. By the fourth time, the first desk sends its next card straight to the second desk unopened. No other figures.
    Voice
    Each override feels small. Together they teach the team lead that the rule does not count, so the decisions drift back up.
    On screen
    Example: Stepping in feels like helping
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Team screen, Example tag top left, context ‘Dana’s crew’. Step band on ‘prepare’. Heading ‘Vendors for Owen’s team: you decided 4 of 6’. Callout 1 on Rule since 3 Mar. Callout 2 on Decided by you: ‘4 of 6, each after Owen had chosen’.
    Voice
    The decision record sets who actually decided against who the rule says should. The rule says Owen. The record says Dana, four times out of six.
    On screen
    Example: who decided, against who should
  5. The mechanism0:26-0:35screen

    Picture
    Same screen, step band on ‘review’. Callout 3 on Reasons written: ‘1 of your 4 overrides’. Cursor moves to ‘Since August: Owen asked you first on his last 3 picks’, then to Drafted.
    Voice
    Only one override has a reason. Since August, Owen asks first. A helper drafts the choice: leave vendors with Owen, and write a reason when you step in.
    On screen
    Example: Owen asked you first on his last 3 picks
  6. The decision0:35-0:42person and screen

    Picture
    Step band on ‘decide’. ‘Leave it with Owen’, ‘Take it back’ and ‘Change’ all visible. Cursor clicks ‘Leave it with Owen’, held two seconds. Rows update: ‘Owen picks his team’s vendors; confirmed today, Owen told’ and ‘Your overrides now need a written reason’. Guide in picture-in-picture.
    Voice
    Dana decides: leave it with Owen, take it back, or change it. Her click settles it, and Owen hears which.
    On screen
    Kept. Owen decides his team’s vendors, and he has been told.
  7. The difference0:42-0:48person

    Picture
    The guide, same place and framing as the moment, so it reads as a return.
    Voice
    Nobody asks first just in case any more: an override is in the decision record, with its reason. The helper drafts; people decide. It does not watch, score or replace anyone.
    On screen
    What you delegate stays delegated, unless you take it back on the record.
  8. Outro0:48-0:52sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    Delegated, then overruled

On screen as proof

  • Team screen setting who decided against who should, walked row by row, tagged Example
  • Example figures ‘4 of 6’, ‘1 of your 4 overrides’ and ‘last 3 picks’ only inside the tagged screen
  • Leave it with Owen, Take it back and Change all visible; click held two seconds

Before and after

Before
Stepping in feels like helping, so each override seems small
After
Each override kept in the decision record, with its reason
Before
The rule was written once and never checked against what happens
After
Who decided, set against who the rules say should, each month
Before
After four overrides, asking first is the safe move for Owen (upward delegation)
After
The right stays with Owen, or is taken back in writing

How it works

The decision record sets who actually decided against who the decision rights say should, so the gap is seen and settled.

  1. Owen picks his team’s vendors within a written limit: in budget, under $10,000 a year each.
  2. When you change one of his calls, the decision record keeps it as an override with your reason; AI helpers keep acting on the written rule.
  3. Each month you see who decided against who should; you keep the right with Owen, narrow it or take it back, and he hears which.
TeamExample

Dana's crew

Vendors for Owen's team: you decided 4 of 6

Rule since 3 Mar
Owen picks his team's vendors, in budget
Decided by Owen
2 of 6 vendors
Decided by you
4 of 6, each after Owen had chosen
Reasons written
1 of your 4 overrides
Since August
Owen asked you first on his last 3 picks
Drafted
Leave vendors with Owen; overrides need a reason

Source: decisions, March to October

Leave it with OwenTake it backChange

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.