How to split a group into fair teams
In short: To split a group into fair teams, choose the team size first, let the number of teams follow, and keep every team within one person of the others: 10 people in 3 teams are 4, 3 and 3. Make the teams at random where everyone can see, and explain any change you make afterwards.
Splitting a group into teams sounds simple until someone feels left out, the same friends always end up together, or one team is clearly stronger than the rest. Fair teams need a fair process as much as a fair result, because people accept a result they did not choose when they trust how it was made.
Decide what fair means for this group
Fair can mean different things:
- Random. Everyone has the same chance of landing in any team. Best when the goal is mixing people up.
- Balanced. Teams have a similar mix of skills or experience. Best for competitions and projects with an outcome.
- Mixed. Teams deliberately combine people from different departments, classes or backgrounds. Best for team building and networking.
Most of the time, random is the right starting point, because it is quick and nobody can argue that the teams were hand-picked. You can then adjust for balance in the open.
Random is also the one method nobody can steer. Twelve people can be split into three teams of four in 5,775 different ways, far too many for anyone to predict or arrange. The team generator takes its random numbers from the browser's crypto.getRandomValues(), which MDN describes as giving cryptographically strong random values, and shuffles the names so that every order is equally likely.
Choose the team size first
The size of each team matters more than the number of teams. For discussion, groups of three to five give everyone a chance to talk. Pairs suit peer review, practice and buddy systems. Teams of six or more need a clear role for each person or the quieter members drift.
For a team that will work together for weeks rather than an afternoon, stay at about ten or under. The Scrum Guide, which defines the framework many software teams work in, puts the size this way:
The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.
Google's study of 180 of its own teams found that team size did not significantly affect how effective they were, but its guide to team effectiveness adds that many researchers have found teams of fewer than 10 members do better than larger ones.
Decide the size, then let the number of teams follow. A team generator can split by people per team as well as by number of teams.
Handling odd numbers
Groups rarely divide evenly. The fairest approach keeps every team within one person of the others: 10 people in 3 teams becomes 4, 3 and 3, not 4, 4 and 2. For pairs with an odd number, make one group of three rather than leaving someone alone.
Make the process visible
Teams made in front of the group feel fairer than teams announced afterwards. Share your screen while you generate them, or read the names out as they come up. If you allow a reshuffle, decide that before you start and do it only once. Reshuffling until one person is happy undoes the fairness for everyone else.
Adjusting for balance without losing trust
Sometimes a random split puts all the experienced people in one team, or puts two people together who should not be. Make the random teams first, then make the smallest change that fixes the problem, and say what you changed and why. "I have swapped Sam and Priya so each team has someone who has used the software before" is easy to accept. Silent changes are not.
Mixing people up over time
If the same group meets regularly, such as a class or a team that pairs for code review, generate new teams each time. Over a few weeks, everyone works with most of the group, which builds wider relationships than fixed teams ever do.
Deciding who goes first
The same principle applies to turns. When teams present, or people give updates, a random order removes any sense that someone is always first or always last. A turn picker puts everyone in a random order where each person appears exactly once.
A checklist for fair teams
- Decide whether you need random, balanced or mixed teams.
- Pick the team size, then the number of teams follows.
- Generate the teams where everyone can see.
- Make any changes in the open, and explain them.
- Start the new teams off with an icebreaker question.
Questions people ask
What is the fairest way to pick teams?
A random split made in front of the group, with any adjustment made in the open afterwards. Two captains picking in turn is quick, but someone is always chosen last and everyone sees it. If skill matters, spread the experienced people across the teams first, then the rest, and keep any ratings to yourself.
How do you split a group into two teams?
Halve it, and when the number is odd one team has one more person: 23 people make teams of 12 and 11. A team generator set to two teams does this at random. If the two teams will compete, check the split for balance before the first round rather than after it.
How do you divide students into groups?
Choose the group size, then let the number of groups follow. 30 students in groups of 4 is not 7 groups with 2 students left over but 8 groups, 6 of 4 and 2 of 3, which is what the team generator gives when you choose people per team. New groups for each project mean every student works with most of the class over a term.
How do you divide people into groups in a fun way?
In a room without a screen, hand out mixed-up coloured cards and ask people to find the others with the same colour, or have everyone count off from 1 to 4 and group by number. Counting off is quick, though friends soon learn to stand apart so they end up together. Whatever the method, it feels fair when people can see the groups were not hand-picked.
How do you split people into groups on Zoom or Teams?
Make the teams first, paste the list into the meeting chat so everyone knows where they are going, then open breakout rooms with one team in each. Zoom's and Microsoft's help pages on breakout rooms both describe assigning people to rooms by hand, as well as automatically or by letting people choose.
Esta guía también está en español: Cómo dividir un grupo en equipos justos.
More guides
- How to run an icebreaker that people actually enjoyPicking the question, setting the tone and keeping it short, for meetings, classes and workshops.
- How to cut meeting costs and keep the useful meetingsMeasure what meetings cost, then trim invite lists, shorten defaults and review the recurring ones.
- How to calculate hours worked, with breaks and decimalsSubtracting breaks, handling night shifts, turning minutes into decimals and adding a week up without the usual slips.
- How to calculate overtime pay, with worked examplesTime and a half, double time, the 40 hour workweek, California's daily rules and the two-week trap, with the sums shown.
- How to organise a Secret Santa at work without emailA timeline that works, a budget people can live with, rules worth sending, remote teams, dropouts and keeping it voluntary.
- How to split expenses with friends and settle up fairlyAgree the method, keep one list, work out net balances with a full example and settle up from them.
- What a salary is per hour: the 2,080 hour ruleDividing a salary by the hours it covers, where 2,080 and 2,087 come from, shorter weeks, unpaid leave and the reasons two answers differ.
- How to count business days for a deadlineDay zero, weekends and observed holidays, what "within 10 business days" means, time zones, and why a spreadsheet counts one day more.
- How to split rent fairly by income, room size or bothEqual, room size with the shared space counted, income, or a blend: one $2,700 home worked four ways, couples, and the 30% check.
- How to calculate sprint capacity in hours and pointsDays per person, hours, a measured focus factor and a points forecast: one Thanksgiving sprint worked through.
- How PTO accrual works: the rate, the balance and capsThe rate per pay period, hours-worked accrual, pay stub rounding, 27-payday years, and a cap and a carryover limit worked through.