Run a demo day that actually ends on time

Every sprint review starts the same way: "so… who wants to go first?" Silence. Then the same brave team volunteers again, the confident teams jockey for the prime slots, and the team with the half-finished feature manoeuvres to present last, hoping the meeting runs out before their turn. Forty minutes in, the first two demos have eaten the whole hour, the last three teams get ninety seconds each, and everyone leaves resenting the schedule. None of this is a preparation problem. It's an ordering problem and a time-boxing problem, and both have the same one-click fix.

Why demo order keeps causing friction

Order matters more at a demo day than people admit. Going first means presenting to a full, fresh room; going last means demoing to people checking the clock. When the order is set by volunteering, the slot goes to confidence rather than content. When a manager assigns it, the order gets read as a message — why were we put last? — whether or not one was intended. And alphabetical order quietly hands the same teams the same slots every single sprint. A random order is the only version nobody can take personally: no favourites, no politics, no pattern to resent. The demo day / sprint review order tool shuffles the lineup with a genuinely unbiased shuffle — the same Fisher–Yates algorithm casinos and statisticians trust, driven by your browser's cryptographic random source — so every arrangement of presenters is exactly as likely as every other.

The schedule is the real feature

Shuffling names is easy; plenty of tools do it. What kills demo days is the second problem: no agreed time budget per presenter. This tool builds the schedule as it shuffles. Set the minutes each presenter gets — five by default — and the result comes back as a numbered lineup with a concrete time box against every name: the first team owns minutes 0–5, the second 5–10, the third 10–15, and so on down the list. That small formatting choice changes the room's behaviour. "Try to keep it short" is a vibe; "Billing team, you have minutes 15 to 20" is a contract. Everyone can see exactly when their slot starts, which also means everyone can see exactly whose time is being eaten when a demo overruns — social pressure does the rest.

The arithmetic helps before the meeting, too. Seven teams at five minutes is a 35-minute block; if the calendar invite says 30, you know before anyone speaks that the plan doesn't fit, and you can cut the per-presenter time to four minutes instead of discovering the problem live at the expense of whoever drew the last slot.

A workflow for sprint review day

The practical routine takes under a minute. Paste one presenter per line — teams or individuals, whatever your review is built from. Your list is saved in your browser between sessions, so next sprint it's already there; demo day setup becomes deleting the team that has nothing to show and clicking once. Set the minutes, order the presenters, and share the result in the meeting chat so the schedule is public before the first screen share. If someone's build breaks at the last minute or a team joins late, re-roll — a fresh shuffle takes one click, and because the whole order is visibly random, a re-roll never looks like favouritism the way a manual reshuffle does. Recent orders also land in the page's history, so when someone asks "wait, what was the lineup?" mid-meeting, the answer is on the record.

One habit that compounds: rotate the pain fairly

A single random draw is fair in the moment, but over a quarter of sprint reviews the deeper fairness is statistical: with a fresh shuffle every sprint, every team spends roughly equal time in the opening slot, the graveyard slot, and everywhere in between. Nobody is permanently "the team that goes last." That's a genuinely better deal than any fixed rotation, because a rotation preserves the pattern — the team after you in the alphabet is always the team after you — while a shuffle erases it. The same logic is why so many teams already randomize their standup order : the daily reshuffle is what keeps the meeting from calcifying.

When you need a different flavour of order

Demo day isn't the only meeting with this shape. For talks, class presentations, or any lineup where you want the order without the time boxes, the plain random presentation order tool does the shuffle on its own. And when you'd rather reveal the order one name at a time — building a little suspense about who's up next instead of publishing the whole lineup — a sequential random picker deals presenters off the top of a shuffled deck, one draw per turn. Pick the shape that fits the meeting; the fairness underneath is the same.

Thirty seconds of setup, an hour saved

The best meetings spend their friction on the content, not the logistics. A demo day that opens with a published random order and a minuted schedule skips the awkward volunteering, the political slot-picking, and the end-of-hour crunch in one move. Paste your presenters into the demo day order tool before your next sprint review, set the minutes, and let the shuffle carry the politics. You'll spend the saved argument time on what the meeting is actually for — the demos.