WheelMigo

A fair random order for sprint retrospectives

In a sprint retrospective, the first voice quietly frames what the team decides to fix. A random speaking order takes that framing power away from any single person.

Quick answer

Save your squad as a reusable roster, turn on no-repeat rounds, and spin at the start of the retro to set the speaking order. Because the order is random, no single person — not the most senior, not the loudest — anchors every round, and everyone gets a turn before anyone repeats. Spin a fresh order for each prompt so the same person doesn't always open.

Key points

  • A random order stops the same senior or loudest voice anchoring every retro round.
  • No-repeat rounds mean everyone shares once before anyone goes twice.
  • Save the squad once as a roster and reuse it each sprint; mark anyone away or newly added.
  • Reshuffle a fresh order for each prompt (went well / didn't / try next).
  • It fixes turn-taking, not psychological safety — pair it with good facilitation. Everything stays in your browser.

Retrospectives are where a team decides what to change next sprint, so the order people speak in is not a cosmetic detail — it shapes the outcome. If the same person opens every retro, their read of the sprint becomes the reference point everyone else reacts to. Drawing a random, even, no-repeat order at the start hands that framing role to a different person each time, and guarantees everyone a turn.

Why order matters more in a retro than in stand-up

A stand-up is a quick status sync; a retrospective asks people to be candid about what went wrong and what to try. Three well-documented effects make the first voice powerful in that setting. Anchoring means the first problem raised becomes the number everyone adjusts from. The serial-position effect means what is said first (and last) is remembered and weighted more than what came in the middle. And once a senior or highly confident voice frames the sprint, others tend to fall in line rather than open a competing thread — the pull toward groupthink. A random order does not remove these effects, but it stops any one person owning the powerful first slot every single sprint.

Random, but still fair

Random only helps if the draw is even and does not quietly repeat. WheelMigo draws each pick from your browser's crypto.getRandomValues with rejection sampling, so no name is favoured, and no-repeat rounds mean everyone speaks once before anyone speaks twice. We checked this the boring way: across a test of seven million draws the distribution stayed flat, with no position winning more than chance.

Set it up once, reuse it each sprint

Retros are periodic, not daily, so the setup should survive between them. Add your squad, save it as a roster, and it is there for the next retro and the one after. When someone joined mid-sprint, add them; when someone is on leave or in another meeting, mark them as not present so the wheel skips them without deleting them from the team. Nothing is uploaded — the roster lives in your browser on your device.

Reshuffle for each prompt, not just once

This is where a retro differs from a single stand-up order. A retro usually runs several prompts — what went well, what did not, what to try next — and each one benefits from a fresh order. If you keep the same order across every prompt, the person drawn first still opens the whole session. Spin a new order for each prompt: within a prompt, no-repeat rounds give everyone a turn; between prompts, a reshuffle means a different person opens each topic.

Retro momentWhat to useWhy
Setting the stage / check-inOne no-repeat roundEveryone speaks once, in an order nobody can predict
Each data-gathering promptReshuffle, then a no-repeat roundA different person opens each topic, so no one frames them all
Voting or deciding actionsNo wheel — discuss openlyPrioritisation needs judgement, not a draw

For remote and hybrid retros

On a video call, turn on Present mode: it hides the editor and shows just the wheel, large enough to read on a shared screen. Remote retros are exactly where a visible, obviously-fair draw helps, because people cannot see the room and are quicker to assume the facilitator is picking favourites.

What a random order will not do

A fair order is one lever, not the whole retro. It will not create psychological safety on its own, it will not make people candid in a culture that punishes candour, and it does not replace a facilitator who draws people out and keeps the conversation useful. What it does is remove one small, recurring source of unfairness — the same person always going first — so the facilitation you do add lands on a more level start.

How this works

The order is drawn entirely in your browser. For each pick, WheelMigo requests random bytes from crypto.getRandomValues, discards any value that would fall outside a whole multiple of the current roster size (rejection sampling), and maps the remainder to a person. This removes the small bias a plain modulo would introduce. No-repeat rounds remove each drawn name from the pool until the round is complete, so every person is chosen once before anyone repeats. No roster or draw leaves your device.

Frequently asked questions

Why randomise the speaking order in a retrospective?
Because whoever speaks first tends to anchor the discussion — the first problem raised becomes the reference point, and early speakers are remembered and weighted more. Rotating the order randomly stops the same senior or loudest voice framing every sprint and gives quieter teammates a guaranteed, unpredictable turn.
Should I use the same order for every part of the retro?
No — reshuffle for each prompt. Within a single prompt, use no-repeat rounds so everyone speaks once; between prompts (went well, didn't, try next), spin a fresh order so a different person opens each topic instead of the same person opening the whole session.
Does a random order make a retro psychologically safe?
On its own, no. A fair order fixes turn-taking and reduces first-voice anchoring, but safety comes from how the team and facilitator handle what is said. Treat the wheel as one small lever that removes a recurring unfairness, not as a substitute for good facilitation.

References

  1. Anchoring (cognitive bias) — Wikipedia
  2. Serial-position effect — Wikipedia
  3. Esther Derby & Diana Larsen, Agile Retrospectives: Making Good Teams Great

← All articles