Green, green, green, red
Every status slide said on track, week after week, until the week before launch.
InsteadStatus comes from the work itself, so red shows early and nobody has to soften it.
The video
Video planned52 secondsHow every video is made
The script
- The one point
- The end date is re-forecast weekly from the work, so red reaches the owner weeks earlier.
- Why a video
- Time passing and the same moment twice: weeks of green slides flip toward launch, then one October week side by side, green slide beside forecast; the owner’s click held live.
- Picture
- Brand mark and sound, then the heading ‘Green, green, green, red’ on the site’s background, fading straight into the guide with no black.
- On screen
- Green, green, green, red
- Picture
- Guide in the usual place and framing. Lower third: guide’s first name, Soundly Run guide.
- Voice
- Every status slide said on track, week after week, until the week before launch. Where many teams type their own status by hand, green is the easy answer.
- On screen
- Soundly Run guide
- Picture
- Weekly status slides flip: green, green, green, calendar pages flying toward launch. The last flips red. The red ripples outward: neighbouring team tiles turn red one by one as their plans for that date break. No numbers.
- Voice
- Watch the weeks. Green, green, green, red. When it turns, launch is days away, and every team planning around that date has to move at once.
- On screen
- Green until it is too late to plan around
- Picture
- Drawn Priorities screen, Example tag top left, context ‘Company crew’. Cursor walks heading, then Status report, Promised, Likely now, Why, Proposed, in order. Step band on prepare, then review.
- Voice
- Progress is read from the tracker, not typed in. Reported green since September. Promised 2 November. Likely now 16 November, range 9 to 30. Finishing one step a week, four left.
- On screen
- Payments launch: reported green, forecast says 16 Nov
- Picture
- Step band on decide. Cursor on ‘Move launch to 26 Nov’, Change and Pass visible; click held two seconds. Confirmation appears, then the Promised row reads ‘26 Nov proposed to the affected leads, at 85% confidence’. Guide in picture-in-picture.
- Voice
- The priority’s owner decides: move launch to 26 November, change it, or pass. Only their click tells the affected leads.
- On screen
- Proposed. The affected leads are told today.
- Picture
- Guide back in the same framing. Beside her, Example tag top left, the same mid-October week twice: the green status slide, and the forecast card already showing 16 Nov against 2 Nov.
- Voice
- Nobody types a status slide any more, or chases teams for one. The helper reads the tracker; the owner decides. It does not watch, score or replace anyone.
- On screen
- Status comes from the work itself, so red shows early and nobody has to soften it.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Green, green, green, red
On screen as proof
- Priorities screen with the Example tag, its five rows walked in order
- Approval click on ‘Move launch to 26 Nov’ held two seconds, Change and Pass visible
- One October week shown twice: green slide beside the forecast
Before and after
- Before
- Status is self-reported, and red invites blame, so it stays green
- After
- Status is read from the work in the tracker
- Before
- Green until it is too late to plan around (a lagging indicator)
- After
- A date range forecast from how fast steps finish (throughput) warns early
- Before
- Each team defines on track its own way
- After
- One definition: forecast end against the promised date
How it works
The end date is re-forecast weekly from the work, so red reaches the priority's owner weeks earlier.
- Progress is read from the tools teams already use, not typed into a slide; the priority's owner defines done.
- Each week the end date is re-forecast as a range, with its confidence; the week it crosses the promise, the owner hears it.
- The owner picks a new date at 85% confidence, narrower scope or added help, and the affected leads are told that day.
PrioritiesExample
Company crew · Example
Payments launch: reported green, forecast says 16 NovNew date proposed
- Status report
- Green, every week since September
- Promised
- 2 Nov2 Nov; 26 Nov proposed to the affected leads, at 85% confidence
- Likely now
- 16 Nov, range 9 to 30 Nov (forecast)
- Why
- Finishing 1 step a week; 4 left (throughput)
- Proposed
- Move launch to 26 Nov (85% confidence) and tell the affected leads now
Source: project tracker, 14 Oct
Move launch to 26 NovChangePassProposed. The affected leads are told today.
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.