John K.Takesover themeeting“Be sure toupdateSmartsheet”BeninterruptssomeoneBen isinterruptedby someoneelseSays “slash”3 times in asinglesentenceNo redPROJs fromthe softwareteamSpends waytoo much timeexplainingsomethingvery simpleAwkwardjokeAvailabilitynumbersthat makeno senseOneteam/personcalled out fornot updatingSmartsheetNo redPROJsfrom thetest teamSomeone inthe 44hrbattery chatcalled out bynameReiteratessomethinghe saidevery weekpriorTypoonscreenMakesa badjokeBenremembersto send outthe minutespre-meetingSomeone isunintentionallyunmutedOnlinefolks can’thear thosein the room>5 chatmessagesduring themeeting withno follow-ups>5 chatmessagesduring themeetingFolks in theroom can’thear folksonlineTASKFORCESomeonejuststraightup liesMeetingruns >15minuteslateOver-explains aproject toeveryoneAvoidtalkingaboutefficienciesJuliamentioned70%energyefficiencyBringsupteslaMeetingrunslateBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Bengoes ona tangentLaptopdies/losescommunicationmid meetingBen is >5minuteslateTechnicalissuesJohn K.Takesover themeeting“Be sure toupdateSmartsheet”BeninterruptssomeoneBen isinterruptedby someoneelseSays “slash”3 times in asinglesentenceNo redPROJs fromthe softwareteamSpends waytoo much timeexplainingsomethingvery simpleAwkwardjokeAvailabilitynumbersthat makeno senseOneteam/personcalled out fornot updatingSmartsheetNo redPROJsfrom thetest teamSomeone inthe 44hrbattery chatcalled out bynameReiteratessomethinghe saidevery weekpriorTypoonscreenMakesa badjokeBenremembersto send outthe minutespre-meetingSomeone isunintentionallyunmutedOnlinefolks can’thear thosein the room>5 chatmessagesduring themeeting withno follow-ups>5 chatmessagesduring themeetingFolks in theroom can’thear folksonlineTASKFORCESomeonejuststraightup liesMeetingruns >15minuteslateOver-explains aproject toeveryoneAvoidtalkingaboutefficienciesJuliamentioned70%energyefficiencyBringsupteslaMeetingrunslateBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Bengoes ona tangentLaptopdies/losescommunicationmid meetingBen is >5minuteslateTechnicalissues

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