REALITYWIPE

OLD SCRIPT DETECTED

The stand-up moved on before I unmuted

Try this response:

My update still counts even if I'm a beat behind the last speaker.

Take the 60-second self-check

SEE THE PRACTICE

Build a response for this thought—and one move to prove it.

THE THOUGHT

The stand-up moved on before I unmuted

YOUR RECORDED RESPONSE

My update still counts even if I'm a beat behind the last speaker.

ONE PRIVATE MOVE

Record a fifteen-second voice memo of your blocker line on your own phone and time how fast you can say it; keep the file private.

The red slash on your mic icon during the blocker round

Your name is still two tiles down the grid

The call is a wall of small rectangles, and yours has a red slash where your mouth should be. You found the token-refresh bug at 6 a.m. and typed a two-line summary in your notes app so you would not fumble it live. The host's cursor is already sliding to the next name. Your thumb is on the trackpad, hovering over the mic icon, waiting for a gap that keeps closing before you press it.

The fix gets logged under someone else's initials

By the time you click, the board has moved to deployment windows. You paste your summary into the team channel afterward, but the ticket is already assigned to the engineer who spoke during the gap, and the sprint notes credit their name. Next stand-up, the host calls on two other people before you and skips your tile without seeming to notice, because last time you had nothing to add out loud.

The playback you keep only on your own phone

Before the next call, open your phone's voice memo app and record yourself saying the blocker in one breath, timed from the moment the previous speaker would plausibly stop. Play it back. If it lands under fifteen seconds, you have proof the sentence was ready long before the host's cursor moved, which means the gap was never really the problem.

TRACE · 01/04

How this script runs you

  • You rehearse the blocker line silently while the host is still talking about someone else's ticket.
  • You paste the update into the team channel right after the call instead of saying it during the call.
  • You notice the host skip your tile without comment and read it as proof you have nothing worth interrupting for.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Mute Script

The hidden rule is that your update only counts if it lands inside the exact second the floor is open, so any delay past that second means the idea should be swallowed and saved for text instead of risked out loud.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • My update still counts even if I'm a beat behind the last speaker.
  • A late unmute costs a few seconds, not the whole update.
  • I can jump back in one line after the host moves on.

Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.

INSTALL · 04/04

The protocol, on one card

When I think

The stand-up moved on before I unmuted

I say

My update still counts even if I'm a beat behind the last speaker.

Then I do one thing

Record a fifteen-second voice memo of your blocker line on your own phone and time how fast you can say it; keep the file private.

STATUS: READY_TO_INSTALL

Wipe this thought

4 minutes. Your voice. Free.

Start this exact wipe in the app →

The wipe protocol
  1. Write the thought exactly as it plays: "The stand-up moved on before I unmuted". Word for word — the wipe targets the sentence, not the vibe.
  2. Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
  3. Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
  4. Run the loop: play it every morning and night, log one proof action a day for 7 days.

Straight answers

What if the host has already moved to the next ticket by the time I unmute?

You can still say the line in one breath right after the current speaker finishes; most hosts will take a short late update rather than cut it off, and if they do move on, the same line works in the channel or at the next stand-up.

Does typing the update in chat instead of saying it out loud fix the pattern?

It gets the information across, but it keeps the underlying rule intact: that speaking live is too risky, so you default to text. The pattern loosens when the spoken version gets said at least sometimes, not only typed.

Why does missing one unmute window feel like the whole stand-up went badly?

Because the rule treats the mic delay as a verdict on your contribution rather than a timing accident. One missed second gets generalized into 'I had nothing worth saying,' which is a bigger claim than the moment supports.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script