Roue Oui ou Non

How the yes-or-no wheel works

The wheel defaults to two equal slices, Yes and No, and picks one using crypto.getRandomValues(), the same cryptographic random source used across RandoKit. Behind the animation, the outcome is a single random draw between two equally sized options — there's no bias toward whichever side you glance at first, and no memory of past spins. You can relabel the slices to anything binary: "Order in / Order out," "Left / Right," "Truth / Dare," and the mechanics stay identical.

An honest note: this is a coin flip in costume

Mathematically, a two-slice wheel and a coin flip produce the exact same result: one random binary outcome with equal odds on each side. Nothing about spinning a wheel makes the outcome "more random" than tossing a coin — both draw from the same cryptographic source and both give each option a 50% chance. The reason this tool exists separately from the coin flip is ceremony, not statistics. A slowing, ticking wheel that visibly lands on an answer feels more decisive and more fun to watch in a group setting than a coin landing silently on a table, especially on a shared screen or during a live stream. If you don't need that visual moment, the coin flip is faster and just as valid.

When a 50/50 tool is (and isn't) the right call

This tool is meant for low-stakes calls and tie-breaks: who goes first, whether to order pizza or tacos, whether a meeting starts with icebreakers. It's a reasonable way to end a genuine stalemate where either outcome is fine and someone just needs the group to move on. It's the wrong tool for decisions with unequal weight or more than two real options — if there are three or more choices, use the wheel of names with each option as a slice instead of trying to force a binary. For decisions with a defined pool of candidates (like picking a person rather than an option), the random winner picker or random team generator fit better.

Worked example

A team of six can't agree whether Friday's retro should be in-person or remote. Both options are genuinely acceptable to everyone, so it's a fair candidate for a coin-flip-style decision. Set the wheel to "In-person" and "Remote," spin once, and go with the result — the point isn't finding the objectively correct answer, it's ending a debate that has no objectively correct answer. If the stakes were higher (say, choosing which vendor to hire), a random draw would be the wrong tool entirely; use it only where either outcome is acceptable.

Common mistakes

• Re-spinning until you get the answer you wanted — that defeats the purpose and isn't random decision-making, it's just delay.
• Using a 50/50 wheel for something with more than two real outcomes by cramming multiple ideas into one slice.
• Treating the result as binding for high-stakes calls it was never meant to settle.

Fairness note

With two equal slices, each option has a 50% chance on every spin, independent of previous spins — there's no "it's due" effect where No becomes more likely after several Yeses in a row. Each draw is a fresh, independent sample from the browser's cryptographic random source. For a broader look at why this matters compared to non-cryptographic random generators, see Math.random() vs crypto.getRandomValues().

Privacy

The wheel runs entirely in your browser. Any custom labels you set are stored in local storage on your device, shared across RandoKit tools in that browser, and never sent to a server. Nothing about your spins is uploaded or logged remotely.