Who Picks the Team Dinner Again? 5 Ways to Decide Fairly in Under a Minute

I actually did the math. An 8-person team spends an average of 6 minutes picking the team dinner every week, which adds up to 5 hours a year. Throw in the sighs of "ugh, spicy again…" after the decision is made, and over 1,000 minutes a year evaporate just on choosing a menu. Today, let's cut that down to one minute, and while we're at it, I'll unpack one more thing: "the ladder draw actually isn't fair." 🍱

1Why the Team Dinner Always Goes Sideways

When a Korean workplace decides on a dinner menu, there are 3 classic failure patterns. You've probably lived through all of them:

• The boss-decides type · Done in 30 seconds, but only the boss is happy. The other 7 people sigh into the group chat
• The consensus-debate type · 15 minutes to an hour of debate that ends in "whatever's fine." Everyone compromised, so everyone's a little unhappy
• The rotation type · "Last week was Korean, so this week is Western?" An endless loop. Only whoever decides that day is satisfied

The shared problem is simple. You can't nail fairness and efficiency at the same time. Go fast and someone loses out; be fair and you waste time. So the answer ends up being a random tool, but the outcome changes completely depending on which tool you pick.

25 Methods, Compared at a Glance

Here's a comparison table I put together after testing each one myself. This single table tells you exactly what to use for any group size or situation 👇

To cut to the chase: roulette wins in almost every situation. It's fast, fair, and fun. But the ladder draw is popular too, right? Here's a shocking fact about it.

3The Ladder Draw Actually Isn't Fair

Here's why: in a ladder draw, every time you add one horizontal rung, two adjacent lines swap. If the rungs cluster in the middle, the middle slot gets picked more often, and if there are too few rungs, the starting position overwhelmingly decides the outcome.

I actually ran a simulation. I repeated a 5-person ladder with 5 rungs 100,000 times, and here's what came out:

• Slot 1: chosen about 17% of the time
• Slot 2: chosen about 22% of the time
• Slot 3: chosen about 24% of the time ← the middle comes up most
• Slot 4: chosen about 21% of the time
• Slot 5: chosen about 16% of the time

In theory, an even distribution should make them all 20%, but the middle slot gets picked about 50% more often than the two ends. That's the bias that shows up when there aren't enough rungs.

📊 There's a follow-up piece that digs into this bias more deeply. It works through a 5×5 matrix of starting position × destination option, and uses data to answer questions like "when there's 1 win and 4 losses, where should you start to avoid getting stuck" and "how to arrange the labels when splitting into two teams." → Read the ladder matrix analysis

So how should you use the ladder?

There are two fixes:

• Lay down plenty of rungs, at least 3× the number of people. That's what makes it converge toward an even distribution
• Or just switch to roulette. If the slices are equal in area, roulette is mathematically 100% fair

4Top Pick by Group Size

In practice, group size decides everything. No need to memorize anything, just look at the table and pick:

💡 The table below shows "what's fastest and fairest for this group size," not "this game only works up to this many people." The actual maximum capacity of each game is listed at the end of the article.

5The 1-Minute Real-World Workflow

Try this at your next team dinner and it really does wrap up in under a minute:

0:00 - 0:10 · Toss candidates into the group chat

One line: "Throw out 5 candidates for tonight's dinner." If 5 people each toss in one quickly, it's done in 10 seconds. If someone doesn't chime in, they get an automatic pass, and anyone who didn't suggest one has no right to complain about the result.

0:10 - 0:30 · Enter them into the roulette

Enter the 5 menus into the Lucky Please roulette. Your most recent entries are saved automatically, so from the second team dinner on, one tap on a preset chip and you're done. That drops it from 30 seconds to 5 🏃.

0:30 - 0:50 · Spin + announce the result

Hit Start and enjoy the 10-second animation. When the result lands, screenshot it into the group chat. Done. The question "why that menu?" is answered with "the roulette picked it." Zero blame on any person.

0:50 - 1:00 · Search for a restaurant

Search Naver Maps for the menu + your office address. Closest spot wins. Done. 60 seconds total.

6How to Handle Divisive Menus

"I can't eat spicy food," "I'm allergic to raw fish," "I'm vegan, so…" — on a team with people like this, spinning the roulette gives you a result no one can act on. Handle it in two steps:

• Step 1 · Veto round: In the group chat, quickly collect only the "absolutely not" menus. Allergy, religious, and dietary reasons are accepted no questions asked
• Step 2 · Enter into the roulette: Only un-vetoed menus go in as candidates. That way, whatever the result, everyone's fine with it

This solves "fair randomness" and "real-world constraints" at the same time. Anyone who didn't use their veto has no right to complain about the result, and anyone who did is protected up front.

7Frequently Asked Questions

Q. Does it really happen in under a minute?

Yes, really. With 5 candidates and 5 people, I clocked it at 45–55 seconds. Tossing candidates into the group chat takes the longest, but once you do it once, everyone gets faster from then on.

Q. What if spicy food keeps coming up every time?

The roulette is 100% random, so the same category can come up in a row. If it bugs you, add a "exclude last week's menu category" rule. That keeps Korean → Korean from happening twice in a row.

Q. What if the boss says "I'll just decide"?

One line, "Let's keep it fair~," plus sharing the roulette screen. The boss can add their own pick as a candidate too, so they can't refuse. If the result lands on the boss's choice, great; if not, the random tool decided it, so you keep the justification either way.

Q. What if someone suspects the result was rigged?

The Lucky Please roulette auto-generates a result URL. Drop that link in the group chat and anyone can verify the same result. 100% proof.

Q. Can I use the same thing for the lunch menu?

Of course. It's even more efficient for decisions you repeat daily. 250 lunches a year × 6 minutes = 25 hours wasted picking the lunch menu, and a 5-second roulette saves you 24 hours and 49 minutes ⏰.

8Maximum Players per Game

The recommended group sizes in the tables above are the suggested range for running things "as fast and fair as possible," not the game's own limit. You can absolutely run a larger crowd, here are the actual maximums 👇