This custom tool may run third-party scripts. To load it, agree in Cookie settings in the footer.

A 60-second facilitation script

Say the dilemma in one sentence, then ask the room: “Are both outcomes acceptable if we land on them?” If anyone says no, stop—chance is the wrong tool. If everyone agrees both paths are fine, nominate one person to tap Generate while others watch the screen.

Read the result aloud as Yes or No (or the exact labels on the page). Capture it in the meeting notes in the same breath so nobody “mishears” the flip later. Only allow a second flip if the group agreed on mulligan rules before the first tap.

Keep the script short on purpose. Long preambles invite lobbying that undermines the flip. Write the framed question on a sticky, whiteboard, or shared doc before opening Lompu so the binary is unambiguous when the answer appears. If remote participants join late, paste the question and the result into chat immediately—visibility is part of fairness.

  • Pre-commit: one flip is binding unless visibility failed.
  • Operator: one person clicks; everyone else watches.
  • Close: write the outcome next to the decision owner.
  • Frame first: sticky-note the exact yes/no question.

Worked example: two backlog items, one meeting slot

A product squad has already argued the merits of “polish onboarding” versus “ship the export CSV.” Both are valuable; neither is unsafe. The facilitator frames: “We will do the winner this sprint; the loser stays on the board.” Someone flips. The result is No for the framed question “Do onboarding first?”—so export CSV goes first.

What made it fair was not the webpage—it was the pre-agreed frame. Without that sentence, a Yes/No result is ambiguous and invites a re-litigation loop. Write the question on a sticky note before you open this tool.

After the flip, the loser item gets an explicit parking status in the tracker with the flip date and attendees. That paper trail stops next week’s “we never decided” claim. Reuse the same pattern for “spike now or later” or “demo A or demo B,” as long as both branches fit capacity—when one path needs a security review the other does not, skip chance.

Stream and classroom beats that stay playful

Live streamers invite chat to type a dilemma in chat, pick one clearly phrased binary, then flip on camera. The stark answer creates comedy and momentum without spinning a complex wheel graphic.

Teachers sometimes flip to choose between two prepared warm-ups (both age-appropriate and stocked). Students see impartiality; the teacher keeps pedagogical control because both branches were ready.

Writers stuck on a plot fork can personify the dilemma, flip once, and draft that branch for twenty minutes—then keep or discard based on energy, not destiny. Party hosts can flip between two games already set up on the table so guests enjoy the spectacle without endless negotiation.

Moderators of online workshops can share the URL, count down from three, and flip while cameras watch. That shared glance reduces accusations that a private host “picked” the answer. Save a screenshot when low-stakes games use the result for breakout assignments.

Odds, streaks, and when re-rolls destroy trust

Each generation samples the two published answers with equal weight. There is no stealth “usually yes” mode. Short sessions feel streaky because humans over-read patterns on tiny samples.

Repeated re-rolling until someone likes the answer defeats the ritual. Agree beforehand whether a single flip is binding. Power imbalances matter: do not force a coin flip on someone who already refused an activity that needs their consent or labor.

This is facilitation-grade randomness, not a cryptographic ceremony for security keys or legal raffles. If a streak of five Yes results appears, name the psychology aloud—“small samples look patterned; each flip was still fair”—then stop flipping for entertainment and return to the agenda.

When a custom deck beats a public yes/no

Need “Ship it / Park it / Needs data,” weighted odds, or bilingual Sí/No labels? Build that as your own Lompu generator from the homepage instead of stretching this binary page.

Teams that run the same ritual weekly often brand private labels and keep the link internal, while still browsing public cousins on Explore for inspiration.

Pair flips with activity prompts from other Lompu tools when a meeting needs more than a single bit of entropy—then document the pattern in your own runbook. Custom decks also help with translated labels or three-way escapes for facilitation styles that refuse a hard binary.

Boundaries: what a yes/no flip must never decide

Do not flip for medical choices, legal strategy, hiring, grading, or any decision that requires a person’s informed consent. Chance is a tie-breaker among acceptable options, not a substitute for duty of care.

Households can flip for takeout versus leftovers only after both meals are fine for allergies and budgets. Classes can flip between two reading activities only after both are stocked and age-appropriate. If someone cannot live with one outcome, negotiate or vote with criteria—do not call for Generate louder.

Report this tool

If this page contains abusive, illegal, or rights-infringing material, email contact@lompu.com with the URL and a short description. See also our Terms of Service and the content policy notes on Explore.

Build Your Own Random Generator

Create a custom random generator in seconds with your own list, images, and fields. Make a picker for decisions, ideas, games, giveaways, study prompts, or anything else you want to choose at random. Compare public examples on Explore, then share your finished tool with a simple link.

Frequently Asked Questions