Soundly RunSound familiar?

Four bosses, four priorities

Function, region and two programmes each rank their own list, so one person holds four orders and no tiebreak.

InsteadShared staff get a single order and a named tiebreaker, not four lists.

The video

Video planned54 secondsHow every video is made
The script
The one point
Shared staff get one company order and a named decider, not four competing lists.
Why a video
Cause and effect rippling: four asks converge on one shared person, a tiebreak climbs and stalls, then one set order flows back out to every team.
  1. Intro0:00-0:03sting

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

    Picture
    Guide seated in the usual room and framing, speaking to camera. Lower third: guide’s first name, Soundly Run guide.
    Voice
    One analyst is shared by a function, a region and two programmes, each with its own list. With staff shared this way, nobody is named to set one order.
    On screen
    Guide’s first name, Soundly Run guide
  3. The cost0:10-0:17motion

    Picture
    Four coloured arrows land on one desk at once. The person’s week bar splits into four slivers. A tiebreak bubble climbs the org chart, waits at the top, and drops back as calendar days flip. No figures.
    Voice
    Four asks land on one desk. Every clash climbs to the top, waits, and comes back. The week goes on arbitrating, not working.
    On screen
    Four asks, one person, no tiebreak
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Priorities screen, Example tag top left, context ‘Company crew’. Heading: Four first priorities, drafted into one order. Step band on prepare. Cursor walks rows #1 to #4: Renewals first, Platform move, Western region growth, Supplier portal, each with who proposed it. Callout 1 on #1.
    Voice
    A helper drafts one company order from all four lists, for the person Who decides names: the chief executive. Each row says who proposed it.
    On screen
    Four first priorities, drafted into one order
  5. The mechanism0:26-0:35screen

    Picture
    Step band moves to review. Callout 2 on Objections row: 3 raised, each answered in writing. Cursor opens the side panel, What the western region will see; callout 3 on its three rows in company rank.
    Voice
    Each list’s owner accepts or objects in writing. Three objections, each answered. The western region sees only its own rows, in the company’s rank.
    On screen
    3 raised, each answered in writing
  6. The decision0:35-0:43person and screen

    Picture
    Step band on decide. Decides row: You, chief executive. Set this order, Change and Pass all visible. Cursor clicks Set this order, held two seconds. Heading turns: One order for the whole company. Guide in picture-in-picture.
    Voice
    The chief executive decides: set this order, change it, or pass. They set it, and why goes on each row. Every team sees its rows in this rank.
    On screen
    Order set. Every team sees its rows.
  7. The difference0:43-0:50person

    Picture
    Guide back in the same framing as The moment, so the viewer sees a return. Calm, no inset.
    Voice
    Nobody shared between four bosses has to referee their asks any more. The helper drafts the order; a person decides. It does not watch, score or replace anyone.
    On screen
    Shared staff get a single order and a named tiebreaker, not four lists.
  8. Outro0:50-0:54sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    Four bosses, four priorities

On screen as proof

  • Example-tagged Priorities screen with four proposed first priorities and who proposed each
  • Objections row: 3 raised, each answered in writing
  • Set this order click held two seconds, then confirmation: Order set. Every team sees its rows in this rank.

Before and after

Before
Four backlogs, four owners, no shared rank
After
One company rank; each unit sees its rows
Before
Tiebreaks escalate ad hoc to the top
After
One named decider sets rank at the planning cadence
Before
Shared staff say yes to all four, and let three down
After
Shared staff work in rank, down to the capacity line

How it works

Who decides names one person to set the order for shared staff; every function, region and programme sees its slice of one company rank.

  1. Who decides names one person to set the order for shared staff, here the chief executive; one company rank is drafted from all four lists, with a capacity line.
  2. Each list’s owner accepts where their rows land or objects in writing; the decider sees every answer.
  3. The decider sets the order; the decision record keeps why on each row, and each unit, its shared staff and their AI helpers work down it to the line.
PrioritiesExample

Company crew

Four first priorities, drafted into one order

#1
Renewals first · proposed by Sales
#2
Platform move · proposed by the platform programme
#3
Western region growth · proposed by the region
#4
Supplier portal · proposed by the operations programme
Objections
3 raised, each answered in writing
Decides
You, chief executive, from the Who decides table

Example · Planning draft, 14 Oct

Set this orderChangePass

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.