Over-explains aproject toeveryone>5 chatmessagesduring themeeting withno follow-upsMeetingruns >15minuteslate70%energyefficiencyTechnicalissues>5 chatmessagesduring themeetingJuliamentionedBen is >5minuteslateTASKFORCE“Be sure toupdateSmartsheet”Ben isinterruptedby someoneelseOneteam/personcalled out fornot updatingSmartsheetAvailabilitynumbersthat makeno senseNo redPROJsfrom thetest teamBringsupteslaFolks in theroom can’thear folksonlineReiteratessomethinghe saidevery weekpriorTypoonscreenLaptopdies/losescommunicationmid meetingSays “slash”3 times in asinglesentenceJohn K.Takesover themeetingBenremembersto send outthe minutespre-meetingSomeone inthe 44hrbattery chatcalled out bynameAwkwardjokeMeetingrunslateBengoes ona tangentBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Onlinefolks can’thear thosein the roomMakesa badjokeNo redPROJs fromthe softwareteamAvoidtalkingaboutefficienciesBeninterruptssomeoneSomeonejuststraightup liesSomeone isunintentionallyunmutedSpends waytoo much timeexplainingsomethingvery simpleOver-explains aproject toeveryone>5 chatmessagesduring themeeting withno follow-upsMeetingruns >15minuteslate70%energyefficiencyTechnicalissues>5 chatmessagesduring themeetingJuliamentionedBen is >5minuteslateTASKFORCE“Be sure toupdateSmartsheet”Ben isinterruptedby someoneelseOneteam/personcalled out fornot updatingSmartsheetAvailabilitynumbersthat makeno senseNo redPROJsfrom thetest teamBringsupteslaFolks in theroom can’thear folksonlineReiteratessomethinghe saidevery weekpriorTypoonscreenLaptopdies/losescommunicationmid meetingSays “slash”3 times in asinglesentenceJohn K.Takesover themeetingBenremembersto send outthe minutespre-meetingSomeone inthe 44hrbattery chatcalled out bynameAwkwardjokeMeetingrunslateBengoes ona tangentBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Onlinefolks can’thear thosein the roomMakesa badjokeNo redPROJs fromthe softwareteamAvoidtalkingaboutefficienciesBeninterruptssomeoneSomeonejuststraightup liesSomeone isunintentionallyunmutedSpends waytoo much timeexplainingsomethingvery simple

NPI/Systems Meeting Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
  1. Over-explains a project to everyone
  2. >5 chat messages during the meeting with no follow-ups
  3. Meeting runs >15 minutes late
  4. 70% energy efficiency
  5. Technical issues
  6. >5 chat messages during the meeting
  7. Julia mentioned
  8. Ben is >5 minutes late
  9. TASK FORCE
  10. “Be sure to update Smartsheet”
  11. Ben is interrupted by someone else
  12. One team/person called out for not updating Smartsheet
  13. Availability numbers that make no sense
  14. No red PROJs from the test team
  15. Brings up tesla
  16. Folks in the room can’t hear folks online
  17. Reiterates something he said every week prior
  18. Typo on screen
  19. Laptop dies/loses communication mid meeting
  20. Says “slash” 3 times in a single sentence
  21. John K. Takes over the meeting
  22. Ben remembers to send out the minutes pre-meeting
  23. Someone in the 44hr battery chat called out by name
  24. Awkward joke
  25. Meeting runs late
  26. Ben goes on a tangent
  27. Brings up electrolyte that breaks the laws of solubility (3.5-4M Fe)
  28. Online folks can’t hear those in the room
  29. Makes a bad joke
  30. No red PROJs from the software team
  31. Avoid talking about efficiencies
  32. Ben interrupts someone
  33. Someone just straight up lies
  34. Someone is unintentionally unmuted
  35. Spends way too much time explaining something very simple