Quiz games for team meetings

Most work quizzes are trivia rounds hosted by the one person who enjoys hosting. They fill ten minutes, the same three people answer, and everybody else waits politely for the meeting to resume. That is not a disaster. It is just a much lower ambition than the format can carry.

A quiz is a retrieval mechanic. It asks people to produce something from memory or judgment in front of others, which is why it can be genuinely useful and also why it can quietly humiliate the newest person in the room. The difference sits entirely in what you ask and how you score it.

The three honest reasons to run one

• A break with a shape. Attention has gone and the group needs three minutes that are not the agenda. Trivia is fine here. Just do not file it under development.
• Retrieval practice. Having to produce an answer from memory makes it stick better than reading it again. This only counts if the questions cover material the team was actually taught and needs to retain.
• Surfacing disagreement cheaply. A question everyone answers privately and reveals at once exposes a split the meeting would otherwise talk around for a month.

Everything else on the usual list, bonding and culture and morale, is a side effect. It turns up when the quiz is well made and stays away when it is not, and you cannot commission it directly.

What each quiz mechanic rewards

Choose the mechanic after you know which of those three jobs you are doing. Every one of them has a bias, and the bias is usually invisible to whoever is hosting.

Six rules for writing team quiz questions

1. Nobody should be unable to score. If the newest joiner cannot answer a single question, you have not run a quiz, you have run an initiation.
2. Cut anything whose answer is a date. Dates test memory for trivia. Ask what changed, not what year it changed.
3. Watch the passport problem. In an international team, general knowledge means the host's general knowledge. A round on British sitcoms scores nationality.
4. Prefer questions with two defensible answers. Then score the reasoning rather than the answer. It is the only kind of question that tells you anything about how the team thinks.
5. Stop at five to eight questions. Ten minutes in total. A quiz that outstays its welcome poisons the next one before it starts.
6. Write one question you cannot answer either. It says out loud that not knowing is survivable, which is psychological safety in miniature.

A quiz measures who already knew. If you want to find out who can think, ask something with two defensible answers and score the reasoning instead.

Six formats worth running

1. The team sheet

Four to six people per team, one answer sheet, eight questions, phones face down. Teams swap sheets to mark. Twelve minutes, works from eight people to eighty. What it surfaces is not knowledge: it is who says the right answer quietly and gets overruled. Watch for that and you will learn more than the scores tell you. Ask afterwards: "which answer did your team get wrong that somebody had right?"

2. The estimation round

Five questions with numerical answers nobody knows precisely. How many customers we onboarded last quarter. How many steps a refund takes end to end. The population of the city we are opening in. Closest wins, no half marks. Six minutes, any size. It surfaces whether a team reasons towards a number or simply guesses one. Ask afterwards: "how did you get to that figure, and what would have made it better?"

3. The confidence quiz

The same questions, but each team writes a confidence level beside every answer. Right and confident scores three, right and unsure scores one, wrong and confident loses two. Ten minutes. It rewards calibration rather than knowledge, and the results are uncomfortable in a useful way, because the team that wins is rarely the team that knew the most. Ask afterwards: "where were we certain and wrong, and where else does that happen?"

4. The two-answer round

Four short scenarios lifted from your actual work, each with two defensible responses. Teams pick one and write a single sentence of reasoning. No points for the choice, points for the reasoning, awarded by the other teams rather than the host. Fifteen minutes, best under thirty people. It surfaces the decision rules people are really using. Ask afterwards: "what did the other team weigh that we did not?"

5. The prediction round

Before you put the monthly numbers on screen, ask everyone to write down their prediction. Reveal the predictions first, then the data. Three minutes, and it changes the temperature of the whole meeting: somebody who has committed to a guess listens to the results very differently from somebody being read to. Ask afterwards: "who was closest, and what were they looking at that the rest of us were not?"

6. The how-does-this-work-here round

Five questions about your own processes. Who approves this. Where that document lives. What happens when a customer asks for the thing we do not officially do. Score teams, never individuals. When most of the room gets a question wrong, that is a documentation problem rather than a training problem, and you should say so out loud before anyone feels caught. Ask afterwards: "which of these should not have been hard?"

Remote and hybrid meetings

• Use the poll, not the microphone. Everyone answers at once and the results appear together. Verbal answers simply hand the round to the fastest unmuter.
• Run open questions as a chat waterfall. Everyone types an answer, nobody presses enter, the host says go. It stops the first answer anchoring the rest.
• Never score the room against the remote half. People sitting together have side channels, and it will look like cheating even when it is not.
• Cut the length. Six minutes on a video call feels like twelve in a room, and the drop-off is much steeper.

The same principle runs through most remote team activities: simultaneous beats sequential, because sequential is where the quiet people go to hide.

When a quiz makes the meeting worse

Five situations where the honest move is to skip it.

1. You are using it to check compliance. A quiz on the policy people were told to read is an audit in a party hat. Everyone in the room can tell, and it costs you the format for months.
2. Scores are individual and public in a team that already has a pecking order. You have just published the pecking order and given it a number.
3. The meeting needed a conversation. A quiz is a remarkably effective way to spend the ten minutes in which somebody was going to raise the difficult thing.
4. The same person hosts every time. It stops being the team's ritual and becomes one person's slot, and the questions drift steadily towards their interests.
5. Something has just gone wrong. Trivia in the week of a restructure or a failed launch reads as the company changing the subject, and that reading is usually correct.

Ten minutes you can run on Monday

1. Write five questions about your own work with numerical answers nobody knows exactly. Look them up first, so you have the real figures.
2. In the meeting, split into teams of three or four. One minute per question, one answer plus a confidence level: high, medium or low.
3. Reveal all five answers at once rather than one at a time, so nobody adjusts their story on the way through. Score high and right as three, low and right as one, high and wrong as minus two.
4. Spend the last three minutes on one question only: where were we confident and wrong?
5. Write down what the group says. If the same overconfidence turns up in a real decision within the month, you now have something concrete to point at.

That is the entire method in a small box. The activity produces evidence, the debrief turns evidence into a conversation about how the team works. Debriefing is the part that separates a quiz from a game, and it deserves more preparation than the questions do. If you have never run one properly, how to debrief an activity covers the structure in about five minutes of reading.

When a quiz is not the right instrument

A quiz tests what people already know. It cannot show you how they behave when information is incomplete, the pressure is real and the answer is not in anybody's head. When that is the actual objective, the format has to change: scenarios instead of questions, decisions instead of answers, scoring against judgment rather than accuracy, and a facilitator who can slow the room down at the right moment. That is what a gamified learning app is for. It is a different instrument from a Friday quiz rather than a bigger one, and plenty of teams need the quiz.

If all you want is a meeting that starts better, icebreaker questions do that job with far less machinery, and running the meeting well beats any activity you put inside it.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.