Running a Department-vs-Department Quiz Rivalry That Doesn't Get Petty

Put one quiz in front of a whole company and most people play it politely for ten minutes and forget it by lunch. Frame the exact same questions as engineering versus sales, and suddenly people are messaging their team channel to strategize. A rivalry gives a quiz a reason to matter beyond the questions themselves: there's a group identity to defend, a scoreboard that outlasts the session, and a story that keeps building each time you run it.

That extra stake is also what makes it risky. A single quiz night has no memory; if a question is unfair or a score gets disputed, the group shrugs and moves on. A rivalry has memory. A bad call in week one becomes 'the reason marketing never wins,' repeated for months. The format that makes this fun is the same one that makes it fragile, which is why it needs more structure than a normal quiz night, not less.

Done well, though, it's one of the highest-return things you can run company-wide. It doesn't need a budget, it works across a hybrid office without anyone traveling anywhere, and it gives people outside their own team a reason to actually talk to each other instead of just nodding in the kitchen.

The single biggest mistake in these rivalries is running them as a knockout between two departments and calling it done. Whoever loses walks away with nothing but the loss, and the whole exercise reads as 'we compared two teams and one of them lost,' which is a bad way to spend company goodwill. A league beats a grudge match every time: five or six departments, each playing a couple of the others across a few weeks, with a cumulative leaderboard and a final in the last week.

A league format also fixes the fairness problem before it starts. If team A only ever plays team B once, one unlucky round decides everything, and it's easy for the loser to write the whole result off as a fluke or a rigged question set. Spread it across multiple matchups and multiple weeks, and the leaderboard settles into something that actually reflects the season rather than one bad Tuesday.

Keep matches short, fifteen to twenty minutes including setup, so it slots into an existing all-hands or a dedicated slot right before lunch. A rivalry that demands an hour every week dies by week three because people quietly stop showing up; one that costs fifteen minutes survives because nobody has a real excuse to skip it.

The petty turn usually starts with a question that only one specific person in the room could reasonably answer, and their team wins on the back of it while everyone else feels like spectators. Design against that by keeping questions at the level of general knowledge, company trivia, and shared culture rather than deep specialist knowledge that lives in one person's head. A finance-only question about a spreadsheet formula isn't a fair test of the finance department; it's a test of whoever happens to be the department's Excel expert.

Company trivia works especially well here because it's genuinely level: how many people work in the Cape Town office, what year the company was founded, which product feature shipped last quarter, who's featured in last month's newsletter. Everyone has equal access to this information, and getting it right rewards people who actually pay attention to the company around them rather than whoever happens to specialize in the topic.

Split each round roughly into thirds: general knowledge, company trivia, and one lighter category (pop culture, sport, geography) that has nothing to do with work at all. That mix keeps any one department from having a structural advantage and gives people something to laugh about regardless of who's ahead on the scoreboard.

Name a neutral host for every match, ideally someone from HR, people ops, or a department not currently playing, and never let a captain from either competing team run the buzzer or read the questions. This single rule prevents almost every dispute before it happens, because there's no possible accusation of a friendly ref favoring their own side.

Handicap the standings, not the questions, if one department consistently dominates. Rather than dumbing down the quiz for a smaller team, give underdog departments a small standings bonus (an extra five points for winning as the smaller headcount, for instance) so the season stays interesting for everyone instead of turning into the same two teams trading the top spot every year.

Set one explicit ground rule out loud before the season starts: no personal callouts, ever. 'Support lost by two points' is fine banter; 'Dave from support cost us the match' is not, and a host should shut that down the moment it starts, the same way any healthy competitive environment draws a line between ribbing a team and targeting a person.

Resist the urge to make the prize expensive. A trophy that lives on the winning department's floor until the next season, a custom Slack emoji, bragging rights and a mention in the next all-hands: these work better than a cash prize or a fancy gift, because they don't create a financial incentive worth arguing over. The moment real money is on the line, the tolerance for a disputed question drops sharply, and disputes are exactly what this format is trying to avoid.

What actually drives repeat engagement is the story the league builds over a season: the underdog team that snuck into the final, the department that's held the trophy for three seasons running, the question everyone still argues about weeks later. Recap each match in a short company channel post with the score and one funny moment from it. That recap becomes the thing people actually look forward to, often more than the match itself.

Before it starts: pick five or six departments of roughly similar size, or group small ones together so no side is outnumbered; assign a neutral host for every match; and write or approve every question set before the season begins so no host is improvising on the day.

During the season: keep matches to fifteen or twenty minutes, publish a running leaderboard somewhere visible after every match, and post a short, upbeat recap the same day so momentum doesn't cool off before the next round.

At the final: invite the whole company to watch even if they're not playing, hand over whatever token prize the season built up to, and immediately announce that season two is coming. A rivalry that ends with no sequel just becomes a one-off memory; one that promises a rematch is what actually turns into a tradition people plan their quarter around.