How to Split a Group into Fair Random Teams
The fairest way to split a group into teams is a uniform random shuffle: list everyone, shuffle the list with a Fisher-Yates algorithm so every possible arrangement is equally likely, then deal people out round-robin so team sizes stay even. This removes human bias entirely — because no person chose the result, no one can credibly dispute it.
- —A Fisher-Yates shuffle makes every one of the n! possible team arrangements equally likely — that is what “fair” precisely means.
- —Captains picking and counting off both feel random but are not — one ranks people socially, the other just copies seating order.
- —Research links public team-picking to lower self-esteem; researchers recommend teams be decided in advance, not picked one-by-one.
- —Run the draw openly and set the re-draw rule before generating, so no one can shop for the teams they want.
Why do manual team-picking methods feel unfair?
Because they usually are. The two classic methods each have a structural flaw. Captains picking in turn is a public ranking of social desirability — it is efficient, and quietly brutal for whoever is chosen last. Research on physical education is blunt about the cost: a Norwegian research review reported that being picked last is associated with reduced self-esteem, poorer social relationships, and even some children skipping class, and concluded that students should not be the ones picking teams — teams should be decided in advance. Psychologists note the same mechanism more generally: the pain of social rejection is real and measurable, and a public last-pick is a small, repeated dose of it.
Counting off (“1-2-3-4, 1-2-3-4”) looks neutral but simply maps the order people happen to be standing in onto teams. It is fully determined by seating, so friends clustered together get split in a predictable pattern. It is arbitrary, not random — and the two are not the same thing.
What does “fair” actually mean for a team draw?
A team draw is fair when every person has the same probability of landing on any team and the outcome is independent of who ran it. That is a precise mathematical property, and the Fisher-Yates shuffle guarantees it: it produces a uniformly random permutation in which each of the n! possible orderings of the group occurs with equal probability (1/n!), in linear time. In RandomHub’s implementation, the group generator runs exactly this shuffle and then deals people out round-robin, so the result is both uniformly random and balanced in size — the two properties you want from a fair split.
Manual methods vs a uniform shuffle — a comparison
| Method | Truly random? | Feels fair? | Main problem |
|---|---|---|---|
| Captains pick | No | No | Public social ranking; harms whoever is last |
| Counting off | No | Seems so | Just copies seating order; predictable |
| Pull names from a hat | Roughly | Yes | Slow; hard to balance sizes; easy to fumble |
| Fisher-Yates shuffle | Yes (uniform) | Yes | Needs a tool — but instant and balanced |
Are random teams actually better than self-chosen ones?
For learning outcomes, the evidence leans toward random. A 2024 classroom field experiment found that self-selected groups actually performed worse on group assignments than randomly assigned ones, even though students preferred choosing their own. More broadly, education research finds that randomly mixed, heterogeneous groups tend to outperform homogeneous ones on tasks requiring creativity, problem-solving, and the integration of multiple perspectives — and that lower-performing members benefit most from being mixed in. Self-selection mainly wins on short-term comfort and satisfaction, not results. So for a one-off icebreaker, let people sit with friends; for work that matters, shuffle.
A step-by-step method for fair teams
1. List everyone, unsorted. Paste or type the full set of names, one per line. Don’t pre-arrange them — the shuffle handles ordering, and any manual sorting only reintroduces bias.
2. Choose one constraint. Fix either the number of teams (“4 teams”) or the size per team (“groups of 5”) — not both. The tool balances the other dimension for you.
3. Set the re-draw rule before you generate. Announce it up front: “we draw once, with one optional re-draw.” Deciding this before seeing the result is what keeps it honest — it stops anyone, including you, from re-rolling until the teams look the way they wanted.
4. Generate openly, then commit. Run the shuffle in front of the group. Doing it visibly is half the value: people accept a result they watched a machine produce far more readily than one handed down on a sheet of paper.
When should you override the randomness?
A uniform shuffle is the right default, but a few situations justify a light touch afterwards: separating two people who genuinely should not be paired, or balancing a known skill gap in a competitive league. Do it transparently — say “I’m swapping these two for balance” out loud. The authority of a random draw comes entirely from being seen to respect it; a silent edit quietly destroys the thing that made it fair.
Make your teams now
Add your names below, choose the number of teams or the size per group, and generate a fair, balanced split in one click. It uses the Fisher-Yates shuffle described above, so every arrangement is equally likely. Re-draw once if you must — then commit.
Enter each member name on a new line
Press Cmd/Ctrl + Enter ↵
Frequently asked questions
What makes random teams actually fair?
Fairness comes from a uniform shuffle, where every person has an identical chance of landing on any team and the outcome does not depend on who organised it. The Fisher-Yates shuffle guarantees this mathematically: each of the n! possible orderings of the group is equally likely. Counting off or letting captains pick does not have this property.
Are random teams better than letting people choose their own?
For learning and fairness, often yes. A 2024 classroom field experiment found self-selected groups performed worse on group assignments, and education research finds randomly mixed (heterogeneous) groups tend to outperform homogeneous ones on tasks needing creativity and multiple perspectives — with the largest benefit for lower-performing members. Self-selection mainly wins on short-term comfort and satisfaction.
How do I make teams that are balanced in size?
Decide whether you are fixing the number of teams or the size per team, then deal people out round-robin after shuffling. With 23 people across 4 teams you get sizes of 6, 6, 6, 5 — as even as arithmetic allows — instead of a lopsided split. RandomHub’s group generator does this automatically.
Is counting off (“1-2-3-4, 1-2-3-4”) random?
No. Counting off preserves the order people are already standing in, so the result is fully determined by seating, not chance. Friends standing together get split predictably. It feels random but is not — only a shuffle produces a genuinely uniform, unpredictable assignment.
Should I ever override the random result?
Sometimes, but transparently. Separating two people who genuinely should not be paired, or balancing a known skill gap in a competitive setting, are legitimate. Announce the change (“I’m swapping these two for balance”) rather than doing it silently — the credibility of a random draw comes from being seen to respect it.