Team Building Ideas
Most teams have a set of small recurring decisions that nobody wants to make: who goes first, who facilitates, who writes it up, who pairs with whom. Individually they are trivial. Collectively they are where a surprising amount of low-grade friction lives, because they get resolved by default, and the default is almost always “whoever speaks up” or “whoever did it last time and did not complain”.
A wheel is useful here for a reason that has little to do with randomness: it moves the decision off a person. Nobody has to volunteer, nobody has to nominate a colleague, and nobody has to feel picked on. That is worth more to a team than the statistical properties of the draw.
Stand-up and demo order
Left alone, stand-up order calcifies. It settles into a fixed sequence within about two weeks, and the person who habitually goes first sets the tone and the level of detail for everyone after them. Going last, meanwhile, means summarising into a room that has already checked out.
Spinning for first speaker takes four seconds and breaks the pattern. You do not need to draw the whole order, since one name is enough and you can go clockwise or down the participant list from there. Keep the spin at one second, because nobody wants ceremony at 9:30am.
A caveat: if your stand-up has a real reason for its order, such as dependencies discussed before the people who depend on them, or a lead who frames the day, then randomising it will make the meeting worse. Randomise the parts that are genuinely interchangeable.
Rotating the retro facilitator
Facilitation is the clearest case for a draw. It is real work, it is unevenly distributed by default, and volunteering to do it repeatedly is how one person ends up owning a meeting they never chose to own.
Put the team on a wheel with elimination on and draw one facilitator per retro. Each person facilitates once before anyone repeats, and the draw history is the rota. That matters more than it sounds, because “have I done this recently?” is otherwise a question nobody can answer and everyone answers differently.
Draw for the next retro at the end of the current one, not the start of the next. The person drawn gets two weeks of notice instead of thirty seconds, which is the difference between a prepared session and an improvised one.
Pair and review rotations
Pairing and code review both drift toward the same combinations: people who sit near each other, work on the same area, or simply get along. That is efficient in the short run and it concentrates knowledge in exactly the way you do not want when somebody goes on holiday.
Drawing pairs periodically spreads context around. The method is the same as a gift exchange draw: draw the whole team in order with elimination on, then take them two at a time down the list. An odd number means one group of three, which is usually fine.
Do not randomise reviewers on work that needs a specific expert. A random reviewer on a change to a system only two people understand produces a rubber stamp, which is worse than no review because it looks like one happened. Random reviewer assignment works where the code is genuinely shared.
Hackathon and project teams
Self-selected hackathon teams re-create the existing org chart, which defeats most of the point. Random teams mix people who do not normally work together, and, as with a classroom, they mean nobody is visibly left until last.
Draw the full list in one pass with elimination on and deal the names out into teams. If you need each team to have at least one designer or one backend engineer, do it in pots: draw the designers into teams first, then the engineers, then everyone else. The constraint is satisfied by construction rather than by hoping, which is the same trick that keeps a constrained tournament draw from painting itself into a corner.
The boring decisions
Who orders lunch, who books the off-site, who takes notes, who chases the vendor. These are the ones where the wheel earns its keep, because the cost is not the task. It is the negotiation about the task, repeated weekly, with the same person quietly absorbing it because they are the one who cannot stand the silence.
The useful property here is that the wheel is something to blame. “You are taking notes because the wheel said so” ends a conversation that “can someone take notes?” extends by two minutes every single meeting.
Where a draw is the wrong tool
Worth being explicit, because a wheel is fun and that makes it tempting to use for things it should not decide.
- On-call. Needs predictability, fair spacing, and respect for holidays and time zones. Use a rota with rules, not a draw. Random on-call eventually gives somebody two weekends in a row, and it will be the wrong somebody.
- Task assignment where skill matters. Randomising interchangeable work is fine. Randomising work that needs a specific person is just a slower way of reassigning it later.
- Anything about pay, promotion or performance. Obvious, but worth writing down.
- Decisions somebody is avoiding. If a call is hard because the options are genuinely different, a wheel does not resolve it. It just launders the avoidance. The wheel is for choices where you would be content with any outcome, which is the line the decision maker guide draws.
Friday raffles and small perks
A small recurring draw, whether a voucher, an early finish, or first pick of the good conference, works better than it should, provided the prize is modest and the draw is public. Modest keeps it light; public keeps it credible.
Once anything of value is attached, the process starts to matter. Announce the entry list before drawing, draw where people can watch, and log what the winner actually received. It is the same discipline as any other prize draw, at a smaller scale. The full version is in how to run a raffle people trust.
Remote and distributed teams
Remote is where a shared wheel does something a physical method cannot. On a video call, one person rolling a dice off-camera is an assertion. A shared link that everyone opens and watches resolve at the same instant is an event the whole team witnessed. For a distributed team that never occupies the same room, that distinction is the difference between a draw and a claim about a draw.
For a team spread across time zones, a scheduled spin is better still. Arm the wheel to draw itself at a published time and it fires whether anyone is awake or not, with nobody at the keyboard. The result does not depend on which person happened to be online to run it, and the timestamp settles any question about when it happened.
Getting started
For stand-up order and the boring decisions, the free wheel on the home page is enough, and your team list stays in your browser. For a shared link everyone watches together, scheduled draws and a history that doubles as your rota, see the how-to guide or create a free SpinForFree account.