John K.Takesover themeetingBengoes ona tangent70%energyefficiencyReiteratessomethinghe saidevery weekpriorTASKFORCELaptopdies/losescommunicationmid meeting>5 chatmessagesduring themeeting withno follow-upsOver-explains aproject toeveryoneBringsupteslaMeetingruns >15minuteslateNo redPROJsfrom thetest teamJuliamentionedTechnicalissuesAvailabilitynumbersthat makeno senseAvoidtalkingaboutefficiencies>5 chatmessagesduring themeetingTypoonscreenBen is >5minuteslate“Be sure toupdateSmartsheet”Someone isunintentionallyunmutedAwkwardjokeOnlinefolks can’thear thosein the roomSomeone inthe 44hrbattery chatcalled out bynameNo redPROJs fromthe softwareteamBen isinterruptedby someoneelseFolks in theroom can’thear folksonlineBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Says “slash”3 times in asinglesentenceMeetingrunslateBeninterruptssomeoneBenremembersto send outthe minutespre-meetingSpends waytoo much timeexplainingsomethingvery simpleSomeonejuststraightup liesOneteam/personcalled out fornot updatingSmartsheetMakesa badjokeJohn K.Takesover themeetingBengoes ona tangent70%energyefficiencyReiteratessomethinghe saidevery weekpriorTASKFORCELaptopdies/losescommunicationmid meeting>5 chatmessagesduring themeeting withno follow-upsOver-explains aproject toeveryoneBringsupteslaMeetingruns >15minuteslateNo redPROJsfrom thetest teamJuliamentionedTechnicalissuesAvailabilitynumbersthat makeno senseAvoidtalkingaboutefficiencies>5 chatmessagesduring themeetingTypoonscreenBen is >5minuteslate“Be sure toupdateSmartsheet”Someone isunintentionallyunmutedAwkwardjokeOnlinefolks can’thear thosein the roomSomeone inthe 44hrbattery chatcalled out bynameNo redPROJs fromthe softwareteamBen isinterruptedby someoneelseFolks in theroom can’thear folksonlineBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Says “slash”3 times in asinglesentenceMeetingrunslateBeninterruptssomeoneBenremembersto send outthe minutespre-meetingSpends waytoo much timeexplainingsomethingvery simpleSomeonejuststraightup liesOneteam/personcalled out fornot updatingSmartsheetMakesa badjoke

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