One missed step stalls everything
One file never got uploaded, and the approval sat untouched for a week while everyone assumed it was moving.
InsteadA stalled step is flagged the day it stalls, not found a week later.
The video
Video planned53 secondsHow every video is made
The script
- The one point
- A stalled step is flagged the day it stalls, with the blocking input named and the ask drafted.
- Why a video
- Cause and effect over time: one missing file holds every later step while the days tick past; then the same stall twice, unflagged beside flagged on day four.
- Picture
- Brand mark and sound, then the heading ‘One missed step stalls everything’ on the site’s background, fading straight into the guide with no black.
- On screen
- One missed step stalls everything
- Picture
- Guide in the set place, medium shot, same room as every video. Lower third appears on first appearance.
- Voice
- One file never got uploaded, and the approval sat untouched for a week. As work passes through more hands, the wait between them belongs to nobody.
- On screen
- Guide’s first name, Soundly Run guide
- Picture
- A day counter ticks Monday to Friday. A missing file icon blinks at the first step; downstream, a chain of steps stays grey, each waiting on the one before. Status pings reply ‘moving’. No numbers shown.
- Voice
- The wait hides inside a handoff nobody owns. The blocked input surfaces only when someone chases status.
- On screen
- Waiting since Monday
- Picture
- Drawn Needs you screen, Example tag top left, context ‘Company crew’. Step band on prepare. Cursor walks in order: Work, Acme vendor approval, waiting since Monday; Age, 4 days, median 3 days for this kind (amber); Blocked by, security form not uploaded yet (flag). Callout 1.
- Voice
- Work past its usual time is flagged: four days, against a median of three. Blocked by the security form, not uploaded yet.
- On screen
- Example: Acme vendor approval stalled, security form missing
- Picture
- Step band on review. Cursor on Proposed: ask Ken, the Acme contact, for the form today; then Next step: Dana approves once the form lands. Callouts 2 and 3.
- Voice
- A helper drafts the ask: Ken, the Acme contact, for the form today. Next, Dana approves once it lands.
- On screen
- Proposed: ask Ken for the form today
- Picture
- Step band on decide. Team lead at a desk; Ask Ken for the form, Change, Pass all visible. Click held two seconds; row 4 turns green: Asked Ken, Fri 10:12. Guide in picture-in-picture.
- Voice
- The team lead decides: ask Ken for the form, change it, or pass. A gap that repeats goes to the process owner.
- On screen
- Asked. Dana gets it when the form lands.
- Picture
- Guide back in the same place and framing as the moment. Two second insert, side by side, Example tag: left, the counter runs on into the next week, still ‘moving’; right, the flag appears on day 4.
- Voice
- Nobody chases status to find the blocked step any more. The helper flags and drafts the ask; the team lead decides. It does not watch, score or replace anyone.
- On screen
- A stalled step is flagged the day it stalls, not found a week later.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- One missed step stalls everything
On screen as proof
- Drawn Needs you screen, Example tag: Age 4 days, median 3
- Blocked by: security form not uploaded yet
- Ask Ken for the form click held two seconds, Change and Pass visible
- Screen source line: approvals tracker, 16 Oct
Before and after
- Before
- Each person did their part, so the queue time between them is nobody's
- After
- Each step's wait is measured against its usual cycle time
- Before
- Blocked inputs surface only when someone chases status
- After
- The blocking input is named, with who holds it
- Before
- The same gap recurs next quarter
- After
- Root cause fixed in the written step, not chased again
How it works
Ageing work is flagged in days, the blocking input named and a nudge drafted.
- Each step has a usual time; work that waits past it is flagged that day, and the team lead decides whether it matters.
- The flag names the missing input and who holds it, with the ask drafted; the lead sends, changes or passes.
- Where the same gap repeats, a change to the written step goes to the process owner, who accepts or refuses it, so everyone who runs the step works from the new version.
Needs youExample
Company crew
Acme vendor approval stalled: security form missingAsked
- Work
- Acme vendor approval, waiting since Monday
- Age
- 4 days; median 3 days for this kind
- Blocked by
- Security form not uploaded yet
- Proposed
- Ask Ken, the Acme contact, for the form todayAsked Ken, Fri 10:12
- Next step
- Dana approves once the form lands
Source: approvals tracker, 16 Oct
Ask Ken for the formChangePassAsked. Dana gets it when the form lands.
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.