Choose the right kind of order
A random order works for low-stakes updates, brainstorms, retrospectives, and workshop turns where each eligible person deserves an opening opportunity. It is a neutral starting sequence, not a measure of priority, seniority, or quality.
Decide whether the order is for one question or the whole meeting. For one question, a repeat-free round is usually enough. For a long agenda, generate a sequence for the next segment and revisit consent before carrying it into another topic. Teams with different time zones or communication needs may prefer volunteer order or a written queue.
Build the order step by step
The Wheel can produce a repeat-free sequence one Winner at a time. Keep a simple external record so the group can see who is next without relying on memory.
- List present, willing participants using short labels; remove absent or restricted Entries.
- Announce: “We will select each speaker once. You may pass, and we will handle that pass using the rule we just agreed.”
- Spin the Wheel, read the Winner aloud, and write the position in a shared agenda or whiteboard.
- Use Undo only if the list contained a real error. Otherwise remove the completed Entry and continue.
- Stop when the agreed round is complete; Reset before a new topic only if the group wants a fresh order.
Facilitator script for a calm round
A repeatable script makes the order feel like a shared meeting aid rather than a test. Keep the invitation short and remind people that accessibility needs take priority.
“We have eight willing speakers for this update round. I will select each person once, record the order, and keep the round to two minutes each. You can pass, ask to come back later, or use chat instead. If someone is absent, we will remove them before the next Selection. We will not rerun a result simply because it is inconvenient.”
Between turns say: “Next is Jordan. Jordan, would you like to start now, defer, or pass?” This gives the Winner agency while preserving the announced sequence.
Duplicates, absence, and transparent corrections
Each row is one Entry and one chance. Remove accidental duplicate rows before starting; intentional duplicate rows would give that label extra chances and should be explained plainly.
For shared names, add a neutral team or role label that the group already recognizes. Never use sensitive attributes to distinguish people. If somebody leaves, pause and remove their Entry before the next spin. If they return, rejoin them only under the rule agreed at the start, such as adding them to the end of the remaining pool.
Undo is for a mis-click or an Entry that was ineligible. Reset is for starting a new round. A correction should be visible: say what was wrong, what changed, and why the next Selection is the appropriate remedy. The fairness guide explains the browser randomness and commit-before-reveal model in plain language.
Privacy and accessibility in the room
Use the least identifying labels that let participants recognize the order, prepare the list before screen sharing, and keep private notes out of Entries. Browser-first operation means the list stays in the browser by default; Shared Setup fragments can still be copied into chat or captured in screenshots.
Presentation Mode reduces setup clutter for a projector or video call. Read each Winner aloud, do not rely on color alone, and keep a text record for people who cannot see the animation. Offer keyboard access, a chat response, or a private pass when a visible turn would create an accessibility or safety problem.
Know when to use a different process
Do not use random order for emergency response, formal decision rights, regulated approvals, disciplinary matters, hiring, medical or legal discussions, or any conversation where policy specifies who must be heard first.
A documented agenda, chair-managed queue, or consent-based round is better when expertise, urgency, power, or accommodation determines order. Randomly is a lightweight participation aid for ordinary group conversation; it does not make an outcome compliant, unbiased in every social sense, or suitable for a high-stakes decision.
Related Randomly guidance
Read how Randomly handles fairness and browser randomness, review the privacy approach, or choose a practical starting point from the Template library. Continue with meeting and workshop Tools.
Quick answers
Frequently asked questions
How do I keep the order from feeling rigid?
Treat it as a default invitation. Allow a pass or defer option, keep time flexible, and let the facilitator apply the announced exception rule when someone needs an accommodation.
Should I use Wheel or Race for speaking order?
Use the Wheel when you want a clear next-speaker Selection and repeat-free sequence. Use Race when a playful, visible elimination reveal fits the group and the activity is genuinely low stakes.
What happens if we discover a missing person halfway through?
Pause and explain the correction. Add the person to the remaining pool if that matches your announced rule, or invite them after the recorded order. Do not silently rewrite earlier Winners.