“Be sure toupdateSmartsheet”MeetingrunslateSpends waytoo much timeexplainingsomethingvery simpleNo redPROJsfrom thetest teamOnlinefolks can’thear thosein the roomSomeone isunintentionallyunmutedTASKFORCESomeonejuststraightup lies>5 chatmessagesduring themeetingTechnicalissuesTypoonscreenMeetingruns >15minuteslateLaptopdies/losescommunicationmid meetingBen is >5minuteslateBen isinterruptedby someoneelseReiteratessomethinghe saidevery weekpriorFolks in theroom can’thear folksonlineBenremembersto send outthe minutespre-meetingOneteam/personcalled out fornot updatingSmartsheet>5 chatmessagesduring themeeting withno follow-upsAwkwardjokeJuliamentionedMakesa badjoke70%energyefficiencyBengoes ona tangentAvailabilitynumbersthat makeno senseBringsupteslaBeninterruptssomeoneSays “slash”3 times in asinglesentenceNo redPROJs fromthe softwareteamBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)John K.Takesover themeetingSomeone inthe 44hrbattery chatcalled out bynameAvoidtalkingaboutefficienciesOver-explains aproject toeveryone“Be sure toupdateSmartsheet”MeetingrunslateSpends waytoo much timeexplainingsomethingvery simpleNo redPROJsfrom thetest teamOnlinefolks can’thear thosein the roomSomeone isunintentionallyunmutedTASKFORCESomeonejuststraightup lies>5 chatmessagesduring themeetingTechnicalissuesTypoonscreenMeetingruns >15minuteslateLaptopdies/losescommunicationmid meetingBen is >5minuteslateBen isinterruptedby someoneelseReiteratessomethinghe saidevery weekpriorFolks in theroom can’thear folksonlineBenremembersto send outthe minutespre-meetingOneteam/personcalled out fornot updatingSmartsheet>5 chatmessagesduring themeeting withno follow-upsAwkwardjokeJuliamentionedMakesa badjoke70%energyefficiencyBengoes ona tangentAvailabilitynumbersthat makeno senseBringsupteslaBeninterruptssomeoneSays “slash”3 times in asinglesentenceNo redPROJs fromthe softwareteamBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)John K.Takesover themeetingSomeone inthe 44hrbattery chatcalled out bynameAvoidtalkingaboutefficienciesOver-explains aproject toeveryone

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