The process from April
Three new hires learned the process from April. It changed in a chat thread, and nobody updated the page.
InsteadA change agreed in chat reaches the written process the same week.
The video
Video planned56 secondsHow every video is made
The script
- The one point
- A change agreed in a chat thread reaches the written step the same week, published by its owner, and everyone on the old step is told.
- Why a video
- Time passing and cause and effect: the page ages April to October while a thread changes the rule, new hires follow the old step; then the owner’s publish click held.
- Picture
- Brand mark and sound, then the heading ‘The process from April’ on the site’s background, fading straight into the guide with no black.
- On screen
- The process from April
- Picture
- Guide in the usual place and framing, speaking to camera. Lower third: guide’s first name, ‘Soundly Run guide’.
- Voice
- Three new hires learned the process from April. It changed in a chat thread, and nobody updated the page. In a growing team, rules change in chat faster than anyone edits the page.
- On screen
- Changed in chat. The page never heard.
- Picture
- Example tag top left. Calendar pages flip April to October; a process page yellows. On 9 Oct a chat bubble rewrites step 3 beside it. Three new-hire figures open the April page and follow the old step; their refunds route to the team lead. No number shown.
- Voice
- Months pass. The thread changes the rule, the page stays in April, and every new hire learns the old step.
- On screen
- Example: The page stayed in April
- Picture
- Drawn Knowledge base screen, Example tag top left, context ‘Priya’s crew’, cursor visible, step band prepare, review, decide. Callout 1: ‘Update Refund approval from the thread?’, last checked 2 Apr. Callout 2: Agreed in: Support thread, 9 Oct. Callout 3: Step 3, April and Step 3, drafted side by side; Read since April: 3 new hires, 2 AI helpers.
- Voice
- A helper spots the change agreed in the support thread and drafts the new step beside the April one. It shows who still works from the old version: three new hires, and two AI helpers.
- On screen
- Example · Update Refund approval from the thread?
- Picture
- Screen with Publish the new step, Change and Pass all visible. Cursor clicks Publish the new step, held 2 seconds. Heading becomes ‘Refund approval: current, checked today’; rows read ‘Checked 19 Oct by you · next check January’ and ‘3 new hires and 2 AI helpers told what changed’. Guide in picture-in-picture.
- Voice
- Priya owns the support process, so she decides: publish the new step, change it, or pass. Once published, everyone who learned the old step is told.
- On screen
- Published. Everyone on the old step told, logged with your name.
- Picture
- Guide back in the same place and framing as The moment.
- Voice
- Nobody digs through old threads to learn the real process. The helper drafts; Priya publishes. It does not watch, score or replace anyone.
- On screen
- A change agreed in chat reaches the written process the same week.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- The process from April
On screen as proof
- Drawn Knowledge base screen ‘Update Refund approval from the thread?’, tagged Example
- Step 3, April and Step 3, drafted shown side by side
- Publish the new step click held 2 seconds, Change and Pass visible
- Result row: ‘3 new hires and 2 AI helpers told what changed’
Before and after
- Before
- Agreed in a thread; those who agreed already know, so nobody writes it
- After
- Each change is drafted into the written process (SOP)
- Before
- No owner for the written process; the page ages quietly
- After
- Every written process has an owner and a check-again date
- Before
- New hires ramp on the April version
- After
- Start here shows newcomers only current, owned steps
How it works
The written process is kept true: a change agreed in a thread is drafted into the step, and the process owner publishes it.
- A change agreed in a thread counts as a change to the process: it is drafted into the written step, and the process owner decides.
- Once published, everyone who learned the old step is told what changed, new hires and the AI helpers that follow it alike.
- Every step keeps an owner and a check-again date; past it, the step shows as unconfirmed until its owner reconfirms it.
Knowledge baseExample
Priya's crew
Update Refund approval from the thread?Refund approval: current, checked today
- Page
- Refund approval · last checked 2 AprChecked 19 Oct by you · next check January
- Agreed in
- Support thread, 9 Oct, Ari and Tom
- Step 3, April
- Team lead approves any refund
- Step 3, drafted
- Support decides under $500; over goes to Finance
- Read since April
- 3 new hires, in Start here; 2 AI helpers act on it3 new hires and 2 AI helpers told what changed
Source: support thread, 9 Oct
Publish the new stepChangePassPublished. Everyone on the old step told, logged with your name.
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.