Decided, then decided again
Your team settled it in March. The person who lost the argument raises it again every month, and the work waits each time.
InsteadOnce your team decides, everyone commits. Only a new fact reopens it.
The video
Video planned57 secondsHow every video is made
The script
- The one point
- Once the team decides, everyone commits, and only a named new fact reopens the call.
- Why a video
- Time passing: March to October in seconds, the same question back in April, June and October, work stalling each time; then the decider keeps the call, click held.
- Picture
- Brand mark and sound, then the heading ‘Decided, then decided again’ on the site’s background, fading straight into the guide with no black.
- On screen
- Decided, then decided again
- Picture
- Guide in the usual place, room and framing; lower third on first appearance; quiet music bed.
- Voice
- Your team settled it in March. It returns every month, and work waits. When a team decides together, nobody writes down what would reopen it.
- On screen
- [Guide first name], Soundly Run guide
- Picture
- A calendar flips March to October. In April, June and October the same decision card slides back onto a meeting table, and a work progress bar beside it stops each time, leaving visible gaps. No numbers.
- Voice
- Raised again in April, June, October. Each time, work stalls while the team waits to see if it flips.
- On screen
- Same question again. The work waits.
- Picture
- Drawn Record screen, Example tag top left, context ‘Company crew’, music out, step band on prepare. Cursor walks the heading, ‘Decision: Mobile app built on the web stack, not native · 12 Mar’, ‘Decider: Ravi, platform lead’, ‘Disagreed: Nadia, Mobile, in writing; committed 12 Mar’.
- Voice
- At the decision, the decision record keeps who disagreed and why. Nadia committed, and Ravi named what would reopen it.
- On screen
- Third ask to reopen the mobile decision, no new fact
- Picture
- Step band on review. Cursor walks ‘Reopens if: App crash rate passes 2% for a month’, the warning row ‘This ask: Third since March; crash rate 0.8%, same case as March’, then ‘Drafted: Back to Nadia with the March reasoning; work carries on’.
- Voice
- It reopens if crash rate passes 2% for a month. It is 0.8%, same case as March, so the draft sends it back.
- On screen
- Reopens if crash rate passes 2% for a month
- Picture
- Step band on decide. ‘Keep the decision’, ‘Reopen anyway’ and ‘Change’ all visible. Ravi’s cursor clicks ‘Keep the decision’, held two seconds. Heading turns ‘Decision stands; Nadia told why’; row ‘Sent to Nadia; reopens only if crash rate passes 2%’. Guide picture-in-picture.
- Voice
- Ravi decides: keep the decision, reopen anyway, or change it. Nadia is told why.
- On screen
- Decision stands; Nadia told why
- Picture
- Guide returns, same place and framing as the moment, so the viewer sees a return.
- Voice
- Nobody re-argues March every month any more. A helper drafts; Ravi decides. It does not watch, score or replace anyone.
- On screen
- Once your team decides, everyone commits. Only a new fact reopens it.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Decided, then decided again
On screen as proof
- Record screen ‘Third ask to reopen the mobile decision, no new fact’, tagged Example
- Rows ‘Disagreed’, ‘Reopens if’ and ‘This ask’
- ‘Keep the decision’ click held two seconds
- Confirmation: ‘Kept by Ravi. The ask and the reason stay in the decision record.’
Before and after
- Before
- Dissent never written down, so the losing side relitigates to be heard
- After
- Dissent recorded once, in writing, then everyone commits
- Before
- Reopened by persistence, not new evidence
- After
- A reopen needs a linked new fact, or it goes back
- Before
- The team slow-walks, waiting to see if it flips
- After
- Work proceeds; the fact that would reopen it is named up front
How it works
Disagree and commit, written down: dissent kept in the decision record, and only a new fact reopens the call.
- At the decision, the decision record keeps who disagreed and why; each dissenter commits, and the decider names what would reopen it.
- A reopen with no linked new fact goes back to its proposer, with the March reasoning attached; the team keeps working.
- When the named fact appears, it reaches the decider, who weighs only what is new.
RecordExample
Company crew
Third ask to reopen the mobile decision, no new factDecision stands; Nadia told why
- Decision
- Mobile app built on the web stack, not native · 12 Mar
- Decider
- Ravi, platform lead
- Disagreed
- Nadia, Mobile, in writing; committed 12 Mar
- Reopens if
- App crash rate passes 2% for a month
- This ask
- Third since March; crash rate 0.8%, same case as March
- Drafted
- Back to Nadia with the March reasoning; work carries onSent to Nadia; reopens only if crash rate passes 2%
Source: decision record, 12 Mar; crash reports, 19 Oct
Keep the decisionReopen anywayChangeKept by Ravi. The ask and the reason stay in the decision record.
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.