AwkwardjokeTASKFORCEBenremembersto send outthe minutespre-meetingMakesa badjokeSays “slash”3 times in asinglesentenceSomeone inthe 44hrbattery chatcalled out bynameJohn K.Takesover themeetingReiteratessomethinghe saidevery weekprior70%energyefficiencyStaceyinsists onliving inrealityUnrealisticexpectationsTypoonscreenOneteam/personcalled out fornot updatingSmartsheetFolks in theroom can’thear folksonlineBen isinterruptedby someoneelse>5 chatmessagesduring themeetingBen askssomeone aquestion andthey don'tanswer“Be sure toupdateSmartsheet”Someone isunintentionallyunmutedBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Ben is >5minuteslateJuliamentionedMeetingrunslateBringsupteslaBeninterruptssomeone>5 chatmessagesduring themeeting withno follow-upsMeetingruns >15minuteslateTechnicalissuesOver-explains aproject toeveryoneLaptopdies/losescommunicationmid meetingRollingcleaningcyclesmentionedSpends waytoo much timeexplainingsomethingvery simpleYournamegetsmentionedBengoes ona tangentNo redPROJs fromthe softwareteamAvailabilitynumbersthat makeno senseNo redPROJsfrom thetest teamOnlinefolks can’thear thosein the roomAvoidtalkingaboutefficienciesSomeonejuststraightup liesBen sayssomethinginappropriateAwkwardjokeTASKFORCEBenremembersto send outthe minutespre-meetingMakesa badjokeSays “slash”3 times in asinglesentenceSomeone inthe 44hrbattery chatcalled out bynameJohn K.Takesover themeetingReiteratessomethinghe saidevery weekprior70%energyefficiencyStaceyinsists onliving inrealityUnrealisticexpectationsTypoonscreenOneteam/personcalled out fornot updatingSmartsheetFolks in theroom can’thear folksonlineBen isinterruptedby someoneelse>5 chatmessagesduring themeetingBen askssomeone aquestion andthey don'tanswer“Be sure toupdateSmartsheet”Someone isunintentionallyunmutedBrings upelectrolyte thatbreaks the lawsof solubility(3.5-4M Fe)Ben is >5minuteslateJuliamentionedMeetingrunslateBringsupteslaBeninterruptssomeone>5 chatmessagesduring themeeting withno follow-upsMeetingruns >15minuteslateTechnicalissuesOver-explains aproject toeveryoneLaptopdies/losescommunicationmid meetingRollingcleaningcyclesmentionedSpends waytoo much timeexplainingsomethingvery simpleYournamegetsmentionedBengoes ona tangentNo redPROJs fromthe softwareteamAvailabilitynumbersthat makeno senseNo redPROJsfrom thetest teamOnlinefolks can’thear thosein the roomAvoidtalkingaboutefficienciesSomeonejuststraightup liesBen sayssomethinginappropriate

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