MyWheelName.com Guides

A Wheel Spinner for Team Standups, Retros and Demos

By My Wheel Name Team·Published June 11, 2026·5 min read

Every team meeting has an invisible seating chart. The same person kicks off standup (usually whoever's loudest or most senior), the same two volunteer for demos, and the same poor soul gets 'voluntold' to facilitate the retro. None of it is malicious — it's just what happens when order is left to social gravity. A spinning wheel is the cheapest possible fix: thirty seconds of setup, a visible spin, and the meeting's politics get replaced by luck. Here are the four rituals teams actually run on it, plus the setup details that make them stick.

Random speaking order for standup

Fixed standup order has two failure modes. People stop listening once their turn has passed, and the first speaker sets the tone for everyone — when the most senior person goes first, updates subtly reshape themselves around what leadership signaled. (Meeting facilitators sometimes call this the HiPPO problem: the highest-paid person's opinion anchors the room.) Random order fixes both: nobody can zone out, because they might be next, and the first update of the day belongs to whoever luck picked.

On remote calls, open Full Screen Mode in its own tab and share that — the presentation view mirrors your control tab, spins stay synchronized in both, and the team watches the selection happen instead of taking the host's word for it. Skip someone who's out sick by removing their entry before the first spin; the saved wheel restores the full roster tomorrow.

Rotating the jobs nobody volunteers for

Facilitator, notetaker, the person who files the tickets after retro — rotating thankless jobs by spreadsheet rota breaks the moment someone's on leave, and 'any volunteers?' selects for guilt rather than fairness. Keep a second wheel for role assignment and spin it at the end of each retro for the next cycle. Two refinements teams converge on: use weights as a fairness ledger (just did the job? drop your weight for one cycle — the wheel's memory replaces the spreadsheet), and log assignments by attaching a note to the spin result in history, so January-you can prove to March-you that it really is their turn.

A retro prompt wheel that asks better questions

Retrospectives decay through repetition: ask 'what went well, what didn't' every fortnight and you'll harvest the same three answers from the same three people. A prompt wheel injects variety with zero prep — build it once with fifteen or twenty prompts and spin two or three per retro:

• What's something a teammate did this sprint that you'd like to see more of?
• What did we spend time on that we shouldn't have?
• What almost went wrong but didn't — and what saved it?
• If this sprint had a movie title, what would it be?
• What's one thing we're pretending not to notice?
• What slowed you down that you didn't mention at the time?
• What would you tell a new joiner about how this sprint actually went?
• Which of our processes earned its keep this sprint? Which didn't?

The spin matters as much as the prompts: a facilitator choosing 'what are we pretending not to notice?' is making a statement, but the wheel landing on it is just luck — which gives the team permission to actually answer. Combine with the name wheel (or run both rings of the Multi-Wheel: person on one ring, prompt on the other) for a fully random who-answers-what.

Demo order for sprint reviews

Demo order is quietly contested territory — early slots get a fresh audience, late slots get the 'we're running long, can you be quick?' treatment. Random order is fair in expectation across sprints even when any single review is unlucky, and it kills the pre-meeting jockeying entirely. Load the demo list (the items, not the people — 'checkout flow revamp' demos fine regardless of which engineer drives), spin live as the review opens, and let the order be the order. Multiple Winners set to the full count gives you the entire ordering in one spin session.

Pairing and review assignment, with one caution

The Multi-Wheel can pair reviewers with authors or mentors with mentees — names on the outer ring, names on the inner ring, lock one ring and re-spin the other when the wheel pairs someone with themselves. The caution: pure random pairing is a starting point, not a policy. Reviewer assignment sometimes needs to respect expertise (the database change wants a database reviewer), so treat the wheel as the default that can be overridden with a stated reason, rather than a rule that overrides judgment. The 'stated reason' part is doing the work — it keeps overrides honest.

Why such a small ritual sticks

Teams keep these wheels not because randomness is magical but because the alternative — a human making a micro-decision in front of the group, every day — has costs that compound: the same voices anchoring standup, the same people absorbing the unglamorous work, the same low-grade negotiation before every review. The wheel converts each of those into a five-second spin with a result nobody owns and everybody accepts. Build the team wheel once, save it, share the link, and let luck run the parts of the meeting that never deserved deliberation in the first place.