Random team generator.

Pairing people up sounds trivial. In practice, random pairings go sideways in two places. The same two colleagues end up paired four weeks in a row, or someone is always the odd one out. A good generator fixes both.

Why shuffle instead of assigning?

Assigned pairings feel fair for about a week. Then people start to notice patterns. The manager always puts the senior engineer with the newest hire, or two people who never work together keep getting skipped. A dice-roll sidesteps all of it. Everyone got the same coin flip.

What about the odd one out?

The generator handles odd counts by folding the extra person into one of the existing groups. A team of seven paired into 1:1s comes out as two pairs and one triad. Nobody gets a solo slot, and the triad usually works just as well as a pair for 1:1 conversations.

Why should the tool remember past pairings?

Truly random pairings will repeat. With a group of eight, the odds of at least one pair repeating next week are higher than you'd think. Keeping a history of the last few rounds lets the generator bias away from recent pairs, so the team gets to meet new partners faster without feeling like the shuffle has a pattern.

Pairs, triads, or larger groups?

For 1:1 catch-ups, pairs. For breakout rooms in an all-hands, triads are the safest default. Two-person breakouts can stall if both are quiet, and groups of four plus one person fades out. For project pods or workshop tables, four or five is the usual ceiling before you lose cohesion.

Example. A rotating coffee chat without repeat pairings

Paste your roster once, pick Pairs, and leave avoid repeats on. Shuffle, copy the result as text, and post it in your Slack or Teams channel with a one-line prompt like "book 15 minutes with your person this week." Then hit Save round. Next week, open the same page. Your roster and history are still here, so one shuffle gives you a fresh set that steers away from the last few weeks. With ten people and a few saved rounds you will almost always see the green no-repeats badge. On bigger teams or long streaks some repeats become unavoidable, and the badge tells you when that happens instead of pretending otherwise.

Example. Breakout rooms for a thirty-person all-hands

Paste the attendee list, choose groups of three, and shuffle while people are joining the call. Copy as markdown straight into the meeting doc, or read the groups out as you assign breakout rooms. Ten rooms of three beats fifteen rooms of two, since a triad keeps talking even when one person is quiet. Save the round afterwards and next month's all-hands mixes different people together.

Is my roster saved anywhere?

Only in your browser. The names list and pairing history live in local storage, not on a server. You can clear both with a single click. Nothing leaves this page.