How to split a group into fair teams

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. A fair process matters as much as the teams themselves, 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.

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.

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 quick checklist

1. Decide whether you need random, balanced or mixed teams.
2. Pick the team size, then the number of teams follows.
3. Generate the teams where everyone can see.
4. Make any changes in the open, and explain them.
5. Start the new teams off with an icebreaker question.

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.