Soundly RunSound familiar?

We used to just know

At twenty people you knew who owned what. At sixty, you ask three people and get three names.

InsteadWho owns what is one question away.

The video

Video planned52 secondsHow every video is made
The script
The one point
As a company grows, ownership leaves people’s memory; owning an area means holding its decisions, written down and confirmed, so one question finds the owner.
Why a video
Time passing: twenty people become sixty in seconds. The same question shown twice: bouncing between three desks, then answered once on screen with its source.
  1. Intro0:00-0:03sting

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

    Picture
    The guide in the usual place and framing. Lower third with the guide’s first name and ‘Soundly Run guide’. Behind, an office wall of desks quietly multiplies.
    Voice
    At twenty people you knew who owned what. At sixty, you ask three people and get three names. Nobody is careless. The company grew past what memory holds.
    On screen
    At sixty, you ask three people, get three names
  3. The cost0:10-0:17motion

    Picture
    Example tag top left. A headcount dial spins from 20 to 60. One question card hops between three desks; three different name tags come back. Two project cards, built side by side, collide at a phone icon labelled ‘customer call’. No other figures.
    Voice
    The question bounces. Two teams build the same thing. Someone finds out on a customer call.
    On screen
    Example: Duplicate work found on a customer call
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Knowledge base screen, Example tag top left, context ‘Ask about this · Company crew’. Step band on ‘prepare’. Heading ‘Who owns the export pipeline?’. Callout 1 on Answer: ‘Marco Silva owns it, since 12 Aug’. Callout 2 on He decides: ‘Export formats, schedule, who gets access’.
    Voice
    Owning an area means holding its decisions. A helper drafts who owns what from the decision record; each area’s leader confirms its line. Then anyone asks, and gets one owner.
    On screen
    Example: one owner, one source, one as-of date
  5. The mechanism0:26-0:35screen

    Picture
    Same screen, step band on ‘review’. Callout 3 on Related work: ‘Omar Haddad, customer export, started 3 Oct’. Cursor moves down to Sources: ‘Decision, 12 Aug · Project, 3 Oct’, then As of: ‘Today, 9:40’.
    Voice
    The answer carries its source and date, for people and AI helpers alike. When a new project touches an owned area, both owners see it, and they decide who leads.
    On screen
    Overlap flagged the day the second project starts
  6. The decision0:35-0:42person and screen

    Picture
    Step band on ‘decide’. ‘Open the decision’ and ‘Open Marco’s page’ visible. Cursor clicks ‘Open the decision’, held two seconds. Result: ‘Export pipeline: owner’, ‘Decided by Dana, chief executive, 12 Aug’, ‘Reason: one owner for every export path’. Guide in picture-in-picture.
    Voice
    Open the decision, or open Marco’s page. A person decided this: Dana, the chief executive, on 12 August. Only that area’s leader changes the line.
    On screen
    Every answer opens on its source.
  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 around for an owner any more. The helper answers from what leaders confirmed; people decide. It does not watch, score or replace anyone.
    On screen
    Who owns what is one question away.
  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
    We used to just know

On screen as proof

  • Knowledge base answer screen, walked row by row, tagged Example
  • He decides row: ‘Export formats, schedule, who gets access’
  • Source line ‘Decision, 12 Aug · Project, 3 Oct’ with As of ‘Today, 9:40’
  • Opened decision: ‘Decided by Dana, chief executive, 12 Aug’

Before and after

Before
Asking was always quicker than writing ownership down
After
Each area names its owner and the decisions they hold
Before
Three names come back; none is authoritative
After
One owner, one source, one as-of date
Before
Duplicate work found on a customer call
After
Overlap flagged the day the second project starts

How it works

Owning an area means holding its decisions: each owner and what they decide is written down, confirmed by that area's leader.

  1. A helper drafts who owns each area from the decision record and current projects; each area's leader confirms the decisions their line holds.
  2. Anyone asks, a person or an AI helper, and gets one owner with source and date. Only that area's leader changes a line.
  3. A new project overlaps an owned area: both owners see it the day it starts, and they decide who leads.
Knowledge baseExample

Ask about this · Company crew

Who owns the export pipeline?

Answer
Marco Silva owns it, since 12 Aug
He decides
Export formats, schedule, who gets access
State
Decided
Related work
Omar Haddad, customer export, started 3 Oct
Sources
Decision, 12 Aug · Project, 3 Oct
As of
Today, 9:40

Source: decisions, 12 Aug; projects, 3 Oct

Open the decisionOpen Marco's page

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.