A team quiz at work: thirty minutes that a remote team actually looks forward to

How to run a quiz for colleagues that is short, optional, not about work, and survives a distributed team: timing, group size, question choice, the setup that takes one person five minutes, and the mistakes that turn it into a chore.

6 min readUpdated

Thirty minutes, in work time, on a day people are already together

The single decision that determines whether a team quiz survives past the second one is when it happens. An hour after work on a Thursday is an hour taken from people, and the ones with a commute, a family or a second job will stop coming without saying why. Thirty minutes inside the working day is a break with a game in it, and everybody can take a break.

Attach it to something that already exists. The end of the weekly team meeting, the slot before the Friday wrap-up, the half hour after a release — people are already on the call, the calendar already has the block, and nobody has to be persuaded to join a second thing. A quiz that needs its own invitation is a quiz that needs justifying every week.

Thirty minutes is two rounds of ten to twelve questions with a few minutes of talk between them. It is not one round of thirty. Long rounds go quiet in the middle, and the people who fell behind early check out. Two short rounds give everybody a fresh start halfway, and the second round has a lead to chase.

Make it genuinely optional, and mean it

A team quiz that people feel obliged to attend is a meeting with points. Optional has to be real: no attendance being noticed, no manager asking where someone was, no team-building framing that makes skipping it a statement. The people who come because they want to are the ones who make it fun for the rest; the ones who came because they had to are the ones who make it awkward.

That includes cameras and microphones. A quiz plays exactly the same with text only, so nobody needs to be on screen, and saying so out loud at the start removes a reason people quietly decline. On a team that is on video all day, a quiz with the cameras off is often the more relaxed version.

It also means the organiser should not be the manager, if that can be arranged. A quiz that the team lead runs is the team lead's thing, and people behave accordingly. A quiz that rotates — whoever won last week picks the categories this week — belongs to the team.

Do not make it about work

The temptation is a quiz about the company: product facts, who joined when, which client is which. It feels relevant, and it is a mistake. Work questions reward tenure and department, so the same people win, and they turn the game into an audit of who knows the company well enough. The new hire who would have been good at geography learns instead that they do not know the org chart.

General knowledge is the point. It is the one field where the intern and the director are on equal footing, where being good at sport trivia matters more than the job title, and where the person who never speaks in meetings turns out to know every capital city. Mix categories so that different people get their round: science and history for some, entertainment and sport for others. A round in which the quietest person on the team wins is the round that gets talked about on Monday.

A small amount of team flavour is fine as a joke, not as content: one question at the end about the office coffee machine, written by last week's winner. Anything more and it becomes work again.

Mixed groups, small rooms, and the distributed-team problem

Rooms here hold ten. A team of twenty-five is three rooms, not one — and that is a feature. Ten is the size at which everybody's answer is noticed; at twenty-five, a quiz is a broadcast with a scoreboard. Split the team across rooms, and mix the rooms: not one per department, not one per office, but deliberately scrambled so that people who never work together end up in the same round. Compare scores across rooms afterwards, if you want a winner.

For a team spread across time zones, the daily round solves what a live session cannot. It is five questions, the same five for everybody that day, playable at any hour without an account, and it produces a result that can be posted in a channel without giving the answers away. A team that cannot find a shared thirty minutes can still share a daily round: everyone plays when they get in, posts their grid, and the channel does the rest. It takes two minutes and it happens every day, which is more than any scheduled quiz manages.

For the live session itself, the host does not need to be the strongest connection or the loudest voice. The game handles the question display, the clock, the scoring and the reveal; the host presses start and reads out the reactions. If the host drops, the room continues.

The practical setup, in five minutes

One person opens a room and picks the categories. The code goes into the team channel a few minutes before the slot, and people join from the browser — no install, no account required to join by code. When enough people are in, the host starts the round; latecomers can join between rounds. At the end, the results screen is the closing conversation, and the room stays open for the second round with the same people.

Two things worth setting on purpose. The question count: twelve per round is right for a thirty-minute slot with talk in between; fifteen if the group is quick and quiet. And the categories: pick them per round rather than once, and let the two rounds be different — one broad, one narrow — so the second round has a different winner.

If the team wants questions about itself despite the advice above, the editor lets a colleague write a private set that nobody outside the room ever sees. The guide on writing questions is worth ten minutes first; the failure modes it lists (two right answers, the giveaway option, the question that takes the whole clock to read) are exactly the ones that show up in a first attempt.

The mistakes that turn it into a chore

Making it weekly before anybody asked for it. Start with one, ask whether people want another, and let the interval be whatever the team actually wants — every two weeks is more common than every week among the teams that keep it going.

Prizes. A prize turns a break into a competition and gives the people who did not win something to feel bad about. The leaderboard is enough; the streak on the daily round is enough. If there must be a prize, make it choosing next time's categories.

Recording it, posting it, reporting on it. A quiz that appears in a status update is work. The results stay in the room and in the channel where people post their grids, and that is the whole record.

And running it for too long. The right length is the one where somebody says "one more?" and the answer is "next time". A quiz that ends with people wanting more is a quiz that happens again.

Try it now

Make a room in 30 seconds and send the code to your friends.