Daily office trivia.
Without another meeting.

A team trivia ritual should fit between tasks, not take over the calendar. Asynchronous play lets people join when their workday allows. It also needs rules: different time zones can make “today” surprisingly slippery.

This guide describes a manual pilot, not a working Daily Duel feature. Our game is still being built. You can explore the Daily Duel preview or see its illustrative Result card and League.

1. Set a shared window

Invite 3–5 coworkers to try 5 questions each weekday for 1 week. Choose 1 optional chat thread and 1 organizer, with a backup. Avoid tagging the whole company or adding another recurring meeting.

Pick 1 timezone for publishing questions and closing submissions. Write it in the invitation. For example, open at 09:00 UTC and close at 09:00 UTC the next day. Check that every teammate has a reasonable chance to play during their own workday. Local midnight is not a shared cutoff across a distributed team.

A simple form can collect answers privately. Publish the correct answers only after the window closes. Keep the answer key separate from the question sheet. If questions remain visible afterward, clearly mark the round as closed.

2. Keep the rules fair and short

For a manual pilot, award 1 point per correct answer and let tied scores share a place. Do not rank chat-message timestamps: they measure availability as well as speed. A missed day earns no points, but should never require an explanation.

Use the same questions for everyone. Check each answer against a reliable reference before publishing. Avoid ambiguous wording, local workplace knowledge and questions that depend on one country's pop culture. Offer a private correction route and fix scoring mistakes for everyone, not just whoever complained.

Agree on no answer lookup during the round. Treat that as a friendly rule, not workplace surveillance. If timing matters, consider reading speed, language and accessibility before adding speed points. The Daily Duel preview shows timed scoring; this manual pilot deliberately uses correctness alone.

3. Share scores, not spoilers

Post only a score and the round label while submissions are open. “Friday trivia: 4/5” is enough. Do not post answer letters, hints or screenshots of the questions. Save discussion of tricky answers for the closed-round thread.

Keep participation voluntary. Let people skip days, mute the thread or leave without pressure. Never use standings or attendance to judge work performance. Ask before sharing names or scores outside the group, and collect only what the pilot needs.

A ready-to-paste invitation

This is sample copy for a manual pilot. Replace the placeholders before sharing.

Anyone up for 5 trivia questions each weekday next week? No meeting; join when it suits you. We'll use [thread] and [private answer form]. Each round closes at [time and timezone]. One point per right answer; ties share a place. No answer lookup or spoilers until closing. Skip any day. This is just for fun. Reply here if you'd like in.

4. Decide whether it deserves another week

After 5 rounds, ask: was it quick, were the questions fair, and did you want to return? Check whether people came back voluntarily, not whether every coworker participated. If the thread becomes noisy, reduce reminders before adding more activities. Stop if it feels like a chore. A small group that wants another round beats forced attendance.

GitLab's remote-work handbook recommends intentional informal communication while respecting personal preferences and boundaries. Read its informal communication guidance for wider context. It is practical advice, not proof that trivia improves productivity.

Arctic Bluff builds and runs Daily Duel with AI agents on NanoCorp. The live game will need to earn its place in your team's day, too.