TechnicalissuesAwkwardjoke“Be sure toupdateSmartsheet”TypoonscreenAvailabilitynumbersthat makeno senseBengoes ona tangentJuliamentionedOnlinefolks can’thear thosein the roomNo redPROJs fromthe softwareteamFolks in theroom can’thear folksonlineSays “slash”3 times in asinglesentenceBen isinterruptedby someoneelseSomeone isunintentionallyunmutedAvoidtalkingaboutefficienciesNo redPROJsfrom thetest teamTASKFORCESomeone inthe 44hrbattery chatcalled out bynameMeetingrunslateSomeonejuststraightup liesBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Ben is >5minuteslateOneteam/personcalled out fornot updatingSmartsheetBringsupteslaMeetingruns >15minuteslateSpends waytoo much timeexplainingsomethingvery simpleBenremembersto send outthe minutespre-meetingOver-explains aproject toeveryone70%energyefficiency>5 chatmessagesduring themeetingMakesa badjokeReiteratessomethinghe saidevery weekprior>5 chatmessagesduring themeeting withno follow-upsBeninterruptssomeoneJohn K.Takesover themeetingLaptopdies/losescommunicationmid meetingTechnicalissuesAwkwardjoke“Be sure toupdateSmartsheet”TypoonscreenAvailabilitynumbersthat makeno senseBengoes ona tangentJuliamentionedOnlinefolks can’thear thosein the roomNo redPROJs fromthe softwareteamFolks in theroom can’thear folksonlineSays “slash”3 times in asinglesentenceBen isinterruptedby someoneelseSomeone isunintentionallyunmutedAvoidtalkingaboutefficienciesNo redPROJsfrom thetest teamTASKFORCESomeone inthe 44hrbattery chatcalled out bynameMeetingrunslateSomeonejuststraightup liesBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Ben is >5minuteslateOneteam/personcalled out fornot updatingSmartsheetBringsupteslaMeetingruns >15minuteslateSpends waytoo much timeexplainingsomethingvery simpleBenremembersto send outthe minutespre-meetingOver-explains aproject toeveryone70%energyefficiency>5 chatmessagesduring themeetingMakesa badjokeReiteratessomethinghe saidevery weekprior>5 chatmessagesduring themeeting withno follow-upsBeninterruptssomeoneJohn K.Takesover themeetingLaptopdies/losescommunicationmid meeting

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