All posts

Team building when it's nobody's job

At small companies, team building is nobody's job, so it either doesn't happen or lands on one tired person. Here's a small rotating role that keeps it going without either.

At a company of eight or twenty people, there’s no People team. Nobody’s job description says “make sure we still like each other.” So team building ends up in one of two places.

Either it doesn’t happen at all, or it quietly becomes one person’s job. Usually it’s the friendliest person on the team, the one who remembered a birthday once and has been the birthday person ever since.

Neither works for long. The good news is that the fix is small.

The two ways it goes wrong

Nobody owns it. Everyone agrees the team should do something together, and everyone assumes someone else will set it up. Months go by. The team keeps shipping, but people slowly stop knowing anything about each other. That’s how a remote team starts drifting apart.

One person owns it forever. This one looks like it’s working, until it isn’t. The organizer is doing unpaid extra work on top of their real job. Everyone else starts treating activities as that person’s thing, something they’re invited to rather than part of. And when the organizer burns out, goes on leave, or moves on, everything stops at once.

The answer sits between those two: a small job, with a clear limit, that moves around.

Make it a small, rotating role

Instead of an organizer, have an organizer of the month. One or two people hold the role for a month, then hand it on.

The key is to write down what the role includes and, just as important, what it doesn’t. Something like this:

The organizer of the month:

  • Picks one or two activities from the team’s list.
  • Puts them on the calendar and sends the invites.
  • Hosts them, or asks someone else to.
  • Posts a short wrap-up afterwards: a photo, the winner, a funny moment.

Not part of the job: getting everyone to attend, planning big events, or spending evenings on it. Aim for about an hour of effort across the month.

That last line matters most. A role with no limit grows until it eats someone’s week. A role with a clear limit is something people can say yes to.

Pair the hosts

Rotating works better in pairs. Two organizers per month means:

  • Nobody is stuck alone when a week gets busy or someone is out.
  • Quieter people get a co-host. Someone who’d never volunteer to run a game alone will often happily co-host.
  • Knowledge carries over. Overlap the pairs, so one person from this month stays on next month. The new person learns by doing, not by reading a handbook.

Make saying no easy

A rotation only works if it’s genuinely optional. Ask who’d like to be on the list rather than adding everyone by default. Let people swap months without explaining why. And if a month ends up quiet because nobody had the energy, that’s fine. Forcing it is how team building turns into homework, and mandatory fun backfires.

You’ll usually find that once the role is small and clearly defined, more people are willing to take a turn than you expected.

Give organizers a menu, not a blank page

The hardest part of organizing anything is deciding what to do. Don’t make each new organizer start from scratch. Keep a short shared list of formats that have worked before, and let organizers pick from it.

A few good places to start:

Add a reusable invite template to the same list, and the whole job gets easier for everyone who comes after.

What leaders still own

Rotating the organizer doesn’t mean leadership is off the hook. A few things only a founder or manager can do:

  1. Protect the time. Team activities should happen inside working hours, and a recurring slot on the calendar makes that official.
  2. Show up, and let others skip. When leaders join in, it signals the activities matter. When they don’t comment on who’s missing, it signals they’re truly optional.
  3. Cover the small costs. If something needs a subscription, a delivery, or a prize, the company should pay, not the organizer.
  4. Say thank you. Organizing is real work. A short public thanks at the end of each month keeps people willing to take a turn.

Where Teamopia fits

We built Teamopia for exactly this kind of team. The live games are ready to play, so the organizer of the month doesn’t need to prepare anything. The team calendar remembers birthdays and anniversaries, and a game can be launched straight from a calendar event. Weekly quests keep small things going between sessions, without anyone hosting at all.

But the rotating role works with any tools. Write the role card, find two volunteers for next month, and pass it on.

Keep reading

4 min read

Twelve small rituals for remote teams

Most of these take five minutes or less, none of them need a budget, and together they do more for a team than one big event a year.

3 min read

Why mandatory fun backfires

The fastest way to kill a team ritual is to require it. Here’s how to design team building people actually choose to join.

Start this week. Keep it going all year.

Set up in a few minutes. Free for up to 10 people.