Soundly RunSound familiar?

Who owns this now?

After the reorg, half the processes lost their owner. Nobody noticed until vendor payments sat unapproved for three weeks.

InsteadA reorg goes live once each step has an owner.

The video

Video planned58 secondsHow every video is made
The script
The one point
A reorg lists every step it would leave without an owner, and goes live once each step has an owner by role.
Why a video
Cause and effect rippling: one role ends on 1 Oct, its approval goes dead, invoices stack and vendors chase; then Grace’s own decision, her Assign click held on the real screen.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘Who owns this now?’ on the site’s background, fading straight into the guide with no black.
    On screen
    Who owns this now?
  2. The moment0:03-0:11person

    Picture
    Guide seated in the usual room, usual framing, speaking to camera. Lower third on first appearance.
    Voice
    After the reorg, half the processes lost their owner. In a company this size, org charts move people, and the steps they quietly owned stay behind.
    On screen
    Guide’s first name, Soundly Run guide
  3. The cost0:11-0:19motion

    Picture
    An org chart reshuffles. The box Regional procurement lead fades out; its line to Approve vendor payments goes grey. Calendar pages turn while invoices stack on an empty desk, a vendor’s mail goes unanswered, a delivery waits at a dock. No number.
    Voice
    One role ends. The approval it held has nowhere to go. Payments wait, vendors chase, and nobody sees why.
    On screen
    One role ends. The approval goes nowhere.
  4. The mechanism0:19-0:29screen

    Picture
    Drawn Team screen, Example tag top left, context ‘Company crew’. Heading: Give vendor payment approval an owner. Step band on prepare. Cursor walks: Approve vendor payments over $10k; Was owned by, role ended 1 Oct; Waiting now, 7 payments, oldest 9 days; side panel.
    Voice
    A helper finds the step the reorg left unowned, shows the work waiting on it, and lists two more steps still unowned.
    On screen
    Example. Waiting now: 7 payments, oldest 9 days
  5. The mechanism0:29-0:39screen

    Picture
    Step band moves to review. Callout 1: Drafted owner, Finance operations lead, marked as a draft. Callout 2: Why this role, Already approves payments under $10k. Callout 3: Limit, Up to $50k; above that, the CFO co-signs.
    Voice
    It drafts an owner by role, not by name, says why, and sets the limit where the CFO co-signs. Once accepted, it goes into Who decides.
    On screen
    Example. Drafted owner: Finance operations lead
  6. The decision0:39-0:47person and screen

    Picture
    Step band on decide. Assign to finance operations, Change and Pass all visible. Cursor rests on Assign; the click is held 2 seconds. Row turns to Finance operations lead, from today. Confirmation names Grace. Guide in picture-in-picture.
    Voice
    Grace, the finance operations lead, decides: assign to finance operations, change it, or pass. If two leads disagree, the COO settles it.
    On screen
    Assigned. 7 waiting payments route to Grace now.
  7. The difference0:47-0:54person

    Picture
    Guide back in the same framing as The moment, so the viewer sees the return.
    Voice
    Nobody has to chase a stuck payment back to a role that ended. The helper lists unowned steps; a person decides who owns them. It doesn’t watch, score or replace anyone.
    On screen
    A reorg goes live once each step has an owner.
  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
    Who owns this now?

On screen as proof

  • Team screen, tagged Example: Was owned by Regional procurement lead, role ended 1 Oct
  • Waiting now: 7 payments, oldest 9 days
  • Assign to finance operations click held 2 seconds, row updates to from today
  • Side panel: Supplier risk review and Renewals under $50k still unowned

Before and after

Before
Org charts move people; the chart of who does what (RACI) misses the steps they quietly owned
After
Decision rights redrawn as part of every reorg
Before
Handoffs fail silently between old and new teams
After
A reorg lists every step it would leave without an owner
Before
Process owners named by person, not role
After
Every step owned by role, surviving the next move

How it works

Decision rights are redrawn as part of the reorg: it goes live only once every process step has a named owner by role.

  1. Before the reorg is approved, every step it would leave unowned is listed with the work waiting on it; the COO signs off.
  2. Each orphaned step gets a drafted owner by role, with its limit; the receiving lead accepts or names someone.
  3. The new owners go into Who decides, so people and AI helpers route work there from day one; where two leads disagree, the COO settles it.
TeamExample

Company crew

Give vendor payment approval an owner

Step
Approve vendor payments over $10k
Was owned by
Regional procurement lead, role ended 1 Oct
Waiting now
7 payments, oldest 9 days
Drafted owner
Finance operations lead
Why this role
Already approves payments under $10k
Limit
Up to $50k; above that, the CFO co-signs

Source: reorg plan, 1 Oct

Assign to finance operationsChangePass

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.