Meeting Bingo is one of those ideas that sounds genius at 11pm on a Tuesday and disastrous in the cold light of Friday morning. Done well, it’s a shared in-joke that pulls your team through another week of status meetings. Done badly, it’s a “we need to talk” email from your manager. This guide walks through how to make it work without making it memorable for the wrong reasons.
What Meeting Bingo actually is
Each player has a 5×5 grid filled with clichés, quirks and phrases that commonly occur in office meetings — “per my last email”, “let’s circle back”, “someone’s on mute”. As the meeting proceeds, players mark squares as the phrases come up. First to complete a line wins — usually bragging rights, occasionally a coffee.
It’s observational bingo: there’s no caller, no pacing, nobody announcing numbers. Squares get marked when the things happen organically. This makes it perfect background entertainment during meetings that don’t demand your full attention.
Which meetings are fair game
The target is meetings that are genuinely recurring, predictable, and low-stakes. The ones where you know before you join what the first three slides will look like.
Fair game:
- Weekly or monthly status meetings
- All-hands updates and town halls
- Onboarding week intros (fifth time you’ve heard the company history)
- Recurring vendor calls where you’re a silent attendee
- Internal comms presentations where you’re not decision-making
Not fair game:
- Performance reviews (yours or anyone else’s)
- Layoff calls, promotion calls, compensation conversations
- Meetings where a new hire is presenting for the first time
- Crisis comms or incident calls
- Any meeting involving real-time customer pain
If you can’t tell whether a meeting is fair game, it isn’t. Err on the side of not playing.
Designing a card people will actually enjoy
Good meeting bingo cards follow three rules:
- Universal, not personal. Squares should describe phenomena anyone on the call might cause — not specific individuals. “Someone’s on mute” is fine. “Dave is on mute again” is not.
- Observable, not interpretable. “Background noise” is an observable fact. “Speaker sounds condescending” is an interpretation — it’ll cause arguments and make people feel watched.
- Predictable, not aspirational. If a square requires someone to behave badly for you to win, you’re creating an incentive problem. Squares should describe things that happen naturally, not dares.
A rule of thumb: read your draft card aloud and imagine your most cautious colleague hearing you read it. If they’d wince at any square, cut it.
The “awkward silence” problem
A lot of first-draft meeting bingo cards include squares like “awkward silence” or “nobody answers the question”. These usually trigger two or three times per meeting, which makes wins feel cheap.
Either remove them, or balance them with rarer squares so a row requires you to mark some genuinely unusual things as well. A card that’s 24 gimmes and one unpredictable square isn’t really a game.
Playing publicly vs. privately
There are two valid models, and they have different etiquettes.
Private play is the safer default. You make a card for yourself, keep it open in a background tab, and mark squares silently as the meeting proceeds. Nobody else knows you’re playing. If you win, you celebrate internally.
Public play means the whole team is in on it. You share a card before the meeting, everyone marks their own, and you compare at the end. This only works when:
- The entire team is bought in (including any manager who attends).
- The meeting’s host is not the target of any specific square.
- There’s a clear agreement that nobody will “perform” to trigger squares.
If you’re running public play, make sure the card is designed by someone other than the person running the meeting. The only thing worse than meeting bingo targeting the speaker is meeting bingo targeting the speaker that the speaker designed.
The shuffled-cards trick
When playing with a group, giving everyone the same card leads to simultaneous wins. That’s not fun — you want staggered “oh!” moments through the meeting, not a collective shout when the first row fills.
BingoStamp’s shuffle option (on the share link) randomises the order of squares per player, so everyone has the same 24 prompts in different positions. First to a line still wins, but the timing is spread out.
Hosting a “meeting bingo night”
Some teams play meeting bingo as an event: a designated monthly all-hands, a quarterly town hall, a weekly team retro. Everyone has a card; a winner is announced at the end. This works because:
- It’s transparent and shared.
- Nobody’s being surveilled or judged.
- The meeting itself is predictable enough to support the game.
- There’s a clear start and end — no creeping into sensitive meetings.
If you want to make meeting bingo a team ritual, this is the way.
Three cards you can use today
Start with one of these if you don’t want to design from scratch:
- Classic Meeting Bingo — 30 generic clichés from every office meeting. Good baseline.
- Standup Bingo — 3×3 quick-play for daily engineering standups. Smaller grid, shorter meetings.
- Conference Call Bingo — 4×4 card for long all-hands and town halls.
The accidental-win problem
Occasionally — usually in a serious meeting — your bingo card completes a row while someone is describing something important. This is a moment of character: do not shout bingo, do not visibly react, do not mention it afterward unless the context allows. Close the tab. Pretend it never happened. Meeting Bingo is a joke; nothing about it is more important than the meeting.
If you find yourself frequently wanting to interrupt real work to announce a win, that’s a signal to stop playing. The whole point is that the game disappears when it needs to.
Etiquette cheat-sheet
- Never play during meetings that affect someone’s livelihood.
- Don’t make cards that target individuals by name.
- Don’t perform to trigger squares — that’s cheating, and the whole game rests on genuine observation.
- If a colleague is presenting for the first time, cancel your card for that meeting.
- Don’t let managers design cards about meetings they run — even in jest.
- Have an out. If a meeting gets serious, close the tab. The game isn’t worth more than the moment.
Play once, then iterate
Your first card will feel a bit off — too easy in some dimensions, too specific in others. That’s fine. After one round, you’ll know which squares trigger too often, which never do, and which squares don’t land with your specific team. Make a v2. The best meeting bingo cards are ones that have been revised three or four times by teams that actually use them.
And if after two rounds you realise the game isn’t landing — maybe the team doesn’t find it funny, or it creates weird side-effects like people avoiding certain phrases — just quietly stop. Meeting bingo should make your work week more bearable, not more complicated. If it’s not doing that, it’s not for your team, and that’s fine.