Soundly RunSound familiar?

Managers managing managers

Your org chart puts six layers between the customer and the decision. Each adds a meeting, so good managers spend the day relaying.

InsteadDecisions move closer to the work before anyone adds a layer.

The video

Video planned58 secondsHow every video is made
The script
The one point
An overloaded lead gets the smallest fix first: move a decision closer to the work, and add a layer only when the load shows it.
Why a video
Cause and effect rippling: one customer question climbs six layers and back, a meeting at each, and a seventh layer lengthens every climb; then Ines’s own click held on the real screen, moving a decision down instead.
  1. Intro0:00-0:03sting

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

    Picture
    Guide seated in the usual room, usual framing, speaking to camera. Lower third on first appearance.
    Voice
    Six layers sit between your customer and the decision, and each adds a meeting. As a company grows, a new layer is easier than moving a decision.
    On screen
    Guide’s first name, Soundly Run guide
  3. The cost0:11-0:19motion

    Picture
    A question card climbs a six-tier org chart; at each tier a meeting block fills the calendar. The answer climbs back down. A seventh tier slots in and the climb lengthens. Below, a work card waits as a clock hand sweeps. No number.
    Voice
    One question climbs every layer and back, a meeting each step. Add a layer, and every climb gets longer.
    On screen
    Every layer adds a climb
  4. The mechanism0:19-0:29screen

    Picture
    Drawn Team screen, Example tag top left, context ‘Ines’s crew’. Heading: Ease Owen’s load without a new layer. Step band on prepare. Cursor walks: Oversight load, 28 hours a week, line is 20; Of which, 9 hours reviewing AI drafts; Shared by, Owen, 2 Oct.
    Voice
    Owen, a team lead, counts his own oversight load, reviewing AI drafts included, and shares it: 28 hours, against a line of 20.
    On screen
    Example. 28 hours a week, line is 20
  5. The mechanism0:29-0:39screen

    Picture
    Step band moves to review. Callout 1: Drafted fix, Refund approvals under $500 move to Elif, closest to the customer, marked as a draft. Callout 2: Load after, 22 hours, no new layer. Callout 3: If not enough, Split the team in two.
    Voice
    The smallest fix comes first: move a decision closer to the work. Refund approvals under 500 dollars go to Elif, who talks to the customer. Load drops to 22 hours, with no new layer.
    On screen
    Example. Load after: 22 hours, no new layer
  6. The decision0:39-0:47person and screen

    Picture
    Step band on decide. Move refunds to Elif, Change and Pass all visible. Click held 2 seconds. Rows turn to 22 hours a week and Elif, from today. Guide in picture-in-picture.
    Voice
    Ines, the department head, decides: move refunds to Elif, change it, or pass. She moves them, and the move goes into Who decides.
    On screen
    Moved. Elif decides refunds under $500.
  7. The difference0:47-0:54person

    Picture
    Guide back in the same framing as The moment, so the viewer sees the return.
    Voice
    Nobody adds a layer just because it is the easiest fix. Owen counts his load; the helper drafts the smallest fix; Ines decides. It doesn’t watch, score or replace anyone.
    On screen
    Decisions move closer to the work before anyone adds a layer.
  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
    Managers managing managers

On screen as proof

  • Team screen, tagged Example: Oversight load 28 hours a week, line is 20, shared by Owen, 2 Oct
  • Of which: 9 hours reviewing AI drafts
  • Move refunds to Elif click held 2 seconds, load updates to 22 hours
  • Screen source line: Owen’s own hours, shared 2 Oct

Before and after

Before
Team size set by a headcount ratio (span of control)
After
Team size set by the oversight work each team needs
Before
Reviewing AI helpers’ work invisible in anyone’s workload
After
Each lead counts reviewing AI helpers’ output in their own load
Before
A new layer is easiest: nobody has to give up a decision
After
Smallest fix first: move decisions, reshape, then layer

How it works

Before a new layer, decision rights move closer to the work; each lead counts their load in oversight hours, and a layer needs a measured signal.

  1. Each lead counts and shares their own oversight hours, including reviewing AI helpers’ drafts.
  2. When load stays over the line, the first fix moves a decision to someone closer to the work, written in Who decides; the department head chooses.
  3. A new layer goes to the people lead only after smaller fixes fail; AI helpers never count as reports.
TeamExample

Ines’s crew

Ease Owen's load without a new layer

Oversight load
28 hours a week, line is 20
Of which
9 hours reviewing AI drafts
Shared by
Owen, 2 Oct
Drafted fix
Refund approvals under $500 move to Elif, closest to the customer
Load after
22 hours, no new layer
If not enough
Split the team in two

Source: Owen’s own hours, shared 2 Oct

Move refunds to ElifChangePass

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.