The Run-Through

See what The Run-Through gives you

Real output from an actual Cut-mode run on the update below, with a 3-minute target. Most of the result is shown; nothing is reworded.

The talk (222 words, for a weekly standup that keeps running over)

So I wanted to give everyone an update on where we are with the migration project. As you all know, we started this back in March, and honestly it's been a bit of a journey. We hit some unexpected issues with the legacy database schema that nobody had really documented well, so the first month was mostly discovery. Then we spent about six weeks building the migration scripts and testing them against a copy of production data, which took longer than expected because we found several edge cases with old customer records that had inconsistent formatting. We're now about 80% through the actual migration, running it in batches overnight to avoid downtime. There have been a couple of hiccups — one batch failed last Tuesday because of a timeout issue, but we caught it before it affected any customers and fixed the root cause. Current plan is to finish the remaining 20% over the next two weeks and then run a full validation pass before we decommission the old system. I also want to flag that we'll need about a week of buffer for that validation, so the total timeline is pushing about two weeks past our original estimate.

Real run, 2026-10-08 — one of the tool's own built-in examples.

Trimmed version (147 words)

Quick update on the migration project. We started in March — first month was mostly discovery because the legacy database schema wasn't well documented. Then about six weeks building and testing migration scripts, which took longer than expected due to edge cases with old customer records that had inconsistent formatting. We're now 80% through the actual migration, running it in batches overnight to avoid downtime. There was a hiccup last Tuesday — one batch failed due to a timeout — but we caught it before it affected any customers and fixed the root cause. Plan is to finish the remaining 20% over the next two weeks, then run a full validation pass before we decommission the old system. That validation needs about a week of buffer, so total timeline is pushing roughly two weeks past our original estimate. Flagging that now so there are no surprises.

What was cut, and why

• 'As you all know' opener and 'honestly it's been a bit of a journey' — Throat-clearing that the standup setting does not need — gets to the facts faster without losing anything the audience requires
• 'I also want to flag that' lead-in before the timeline slip — The flag itself is kept; the verbal setup for it is redundant in tight standup speech

The point that survives

The migration is 80% done, on track to finish in two weeks, but the total timeline is slipping about two weeks past the original estimate due to a needed validation buffer.

How to deliver it

Slow slightly on 'two weeks past our original estimate' — that is the number people will want to register and possibly react to, so give it a beat. The Tuesday timeout incident is context, not alarm; keep that section matter-of-fact and move through it. End on 'no surprises' with a full stop — do not trail off or immediately invite questions, let the room absorb the timeline news first.