Think Fast»Free resources»Would you rather questions safe to ask at w…

80 questions, zero landmines

Would you rather questions safe to ask at work

A good would you rather question for work offers two options with roughly equal appeal, stays away from politics, religion, money, and anything medical, and can be answered out loud in under ten seconds. That's the whole formula, and it's stricter than it looks: most would-you-rather lists on the internet fail the second rule by question five. Below are 80 that pass, sorted by the room you're using them in, plus a rapid-fire this-or-that set for when even one sentence of justification is too much ceremony. Steal freely; deliver with confidence.

Why this format keeps beating fancier icebreakers: a would you rather hands people a decision instead of a blank page. "Tell us something interesting about yourself" is an essay question sprung on the unprepared. "Would you rather never sit in traffic again or never wait in line again" is multiple choice, and everyone has an instant opinion plus a reason they're suddenly eager to share. The format does the talking for the quiet half of the room, which is the entire point of an opener.

The 3 rules of a work-safe would you rather

Rule 1: Both options have to be genuinely tempting (or genuinely terrible). "Would you rather have a million dollars or a sandwich" is not a question, it's a delay. The debate lives in the trade-off; if 90% of the room picks the same side, the question dies on contact. Every question below was written to split a room somewhere near the middle.

Rule 2: No politics, no religion, no money, no bodies. Salary, health, dating, and anything you'd hesitate to say in front of your boss's boss is off the board. This isn't squeamishness; it's engineering. The instant one person feels cornered by a question, the format's magic (instant, cheerful, low stakes) is gone for the whole room.

Rule 3: Ten seconds to answer, one sentence to defend. The question is a spark, not the agenda. Take four or five answers, let one mini-debate flare up briefly, then move. A would you rather that runs fifteen minutes wasn't a good question, it was a meeting hijack with better branding.

Openers for any meeting

Safe with any audience, any seniority, zero context needed. Rotate these through recurring meetings and nobody gets question fatigue.

The funny ones

For rooms that are already a little warm, or need to be. These reward the one-sentence defense; the reasoning is always funnier than the pick.

The food ones

Food questions are the cheat code of the genre: universal, opinionated, and completely safe. If a team lunch is on the calendar, open with one of these and watch the debate outlast the entrée.

The office-life ones

Work-flavored without being about anyone's actual work. These land hardest because everyone in the room shares the same reference points.

The remote-work edition

For distributed teams, where the shared reference points are a webcam and a delivery driver. These double as a gentle census of how everyone actually works.

The slightly deeper ones

For smaller rooms, offsites, or teams that already trust each other. Still safe, but the answers carry actual information; expect follow-up questions, and budget time for them.

This or that: the rapid-fire round

This or that questions are the espresso shot version: two words, no scenario, answer instantly. Run ten in ninety seconds as a lightning round, in chat or out loud, and read the room by the splits. They also work solo as a one-line message when a full question feels like too much production, the same job a question of the day for work does on the days you want zero setup.

How to actually run one

In a meeting: ask the question, answer it yourself first with one sentence of reasoning, then take four or five volunteers. Your answer sets the tone; go medium, not polished. Total cost: three minutes. The delivery mechanics are the same as any opener, and the full playbook lives at icebreakers for meetings.

In chat, synchronously: post the question, have everyone answer at once with just "A" or "B" plus an optional one-liner, then read out the split like election results. Simultaneous answering beats sequential unmuting by about a mile, especially past eight people.

Async in a channel: post one question at a recurring time, use emoji reactions as the voting mechanism, and let the replies be the discussion. The ritual matters more than the question; same day, same time, and it becomes the one thread everyone actually reads.

As a poll: every major chat tool has a built-in poll. The reveal is the moment, so hold the results until the votes are in if your tool allows it. A 51/49 split on garlic bread generates more genuine cross-team conversation than most facilitated workshops.

If you're building a rotation rather than grabbing one question, the broader question supply lives at icebreaker questions for work, and the icebreaker generator deals a fresh one on demand so you never maintain a list again.

And when the would you rather goes too well (the room splits 50/50, someone demands a tiebreaker, the debate outlives the agenda item), that's your team telling you they want an actual game. That's the moment to book twenty minutes of Think Fast: live typed-answer trivia where everyone plays from their own phone, free for up to 8 players, and the arguing comes with a scoreboard.

The shameless plug

Run a trivia event that runs itself

Think Fast is live typed-answer trivia on everyone's phone: free for up to 8 players, flat $99 for events up to 50 with AI-written rounds about your company. No app installs, no host to schedule, full refund if the team doesn't love it.

Play a free round  See event pricing

FAQ

What's the difference between would you rather and this or that?

Scale and speed. A would you rather sets up a scenario with a trade-off and invites a one-sentence defense; a this or that is two nouns and an instant pick. Use would you rather when you want a short discussion, this or that when you want energy and volume: ten answers in sixty seconds, no justification required. In practice they're interchangeable enough that this page covers both, but don't run a this-or-that pace with scenario questions; the whiplash kills the fun of each.

How many questions should I use in one meeting?

One. Two at the absolute most. The format works because it's a spark, not a segment; the moment a second and third question appear, people sense a program has begun and start checking the clock. The exception is a deliberate lightning round of this-or-thats, which is its own bit with its own energy and should still be done inside two minutes. Save the rest of the list; a good rotation beats a good marathon.

What topics should would you rather questions avoid at work?

Politics, religion, money, health and bodies, dating, and anything about actual coworkers or actual company decisions. The test: would every person in the room, including the newest hire and the most senior leader, answer comfortably out loud? Questions about food, logistics, superpowers, and mild inconveniences pass. Questions that reveal salary expectations, health situations, or how someone votes do not, no matter how funny the framing is.

Do would you rather questions work asynchronously in chat?

Better than almost any other icebreaker, because the format survives without a live room. Post one question at a recurring time, let emoji reactions carry the vote, and let the reply thread carry the jokes. Two mechanics matter: consistency (same slot, so it becomes a ritual people expect) and a visible split (the 60/40 result is what pulls the lurkers in). If replies dry up after a few weeks, the questions got too samey; rotate categories.

What if a question accidentally gets too personal?

Deflect with speed, not ceremony. Anyone can pass, so say "pass is always allowed" once at the start and mean it. If a question lands wrong mid-flight (someone's clearly uncomfortable), answer it yourself with something light, move to the next person, and quietly retire that question from your rotation. A recovery handled in five seconds is invisible; an apology tour makes it a moment. The better fix is upstream: the three rules at the top of this page exist precisely so this FAQ stays theoretical.