Hosted awebinar andsomeonejoined 15minutes late."Is therework?!" – Gotasked this EQquestion for the10th time today.Accidentallyforgot toupdate theinstructions...then panickedFound a CBdoing theexact oppositeof theguidelines.Discovered a"usefulfeature" in theAdmin Toolsby accident.A CB asked aquestion thatwas alreadyin theinstructions.Corrected aCB who wasconfident butwrong aboutthe guidelines.Received fivemessages ina row fromthe same CB.Got througha war roomwithoutlosingpatience.Lost a greatCB to anotherproject..again.Spent moretime on EQquestionsthan actualaudits.Explained thesameinstructionupdate to fivedifferent CBs.A CBmisunderstoodinstructions...spectacularly.Instructionsgotupdated...right afterCB training.Attended async where thesame problemwas discussedfor the 100thtime.Tried to usethe AdminTools and gotcompletelylost.Raised aissue knowingit won't beresolved oranswered.CB asks aquestion that'salreadyexplained in apinned post.Got a passive-aggressiveresponse inthe CommunityForum.Answered aCBs questionin a slightlymean tone andregretted it.Answered adumbquestionwithoutsarcasm.Had that oneday whereeverythingwent well!(Surprisingly...)Realized theSTO stillhasn’t clarifiedan importantquestion.Was toobusy to goover thereported CBissues.Attended ameeting thatcould havebeen a slackmessage.Got ameanmessagefrom a CB.Reminded aCB to readtheguidelines...againSTOs say thatyou need morereviewers...but that's allyou have.Finally gotan answerfrom theSTO... threedays later.Hosted awebinar andsomeonejoined 15minutes late."Is therework?!" – Gotasked this EQquestion for the10th time today.Accidentallyforgot toupdate theinstructions...then panickedFound a CBdoing theexact oppositeof theguidelines.Discovered a"usefulfeature" in theAdmin Toolsby accident.A CB asked aquestion thatwas alreadyin theinstructions.Corrected aCB who wasconfident butwrong aboutthe guidelines.Received fivemessages ina row fromthe same CB.Got througha war roomwithoutlosingpatience.Lost a greatCB to anotherproject..again.Spent moretime on EQquestionsthan actualaudits.Explained thesameinstructionupdate to fivedifferent CBs.A CBmisunderstoodinstructions...spectacularly.Instructionsgotupdated...right afterCB training.Attended async where thesame problemwas discussedfor the 100thtime.Tried to usethe AdminTools and gotcompletelylost.Raised aissue knowingit won't beresolved oranswered.CB asks aquestion that'salreadyexplained in apinned post.Got a passive-aggressiveresponse inthe CommunityForum.Answered aCBs questionin a slightlymean tone andregretted it.Answered adumbquestionwithoutsarcasm.Had that oneday whereeverythingwent well!(Surprisingly...)Realized theSTO stillhasn’t clarifiedan importantquestion.Was toobusy to goover thereported CBissues.Attended ameeting thatcould havebeen a slackmessage.Got ameanmessagefrom a CB.Reminded aCB to readtheguidelines...againSTOs say thatyou need morereviewers...but that's allyou have.Finally gotan answerfrom theSTO... threedays later.

QM 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
  1. Hosted a webinar and someone joined 15 minutes late.
  2. "Is there work?!" – Got asked this EQ question for the 10th time today.
  3. Accidentally forgot to update the instructions... then panicked
  4. Found a CB doing the exact opposite of the guidelines.
  5. Discovered a "useful feature" in the Admin Tools by accident.
  6. A CB asked a question that was already in the instructions.
  7. Corrected a CB who was confident but wrong about the guidelines.
  8. Received five messages in a row from the same CB.
  9. Got through a war room without losing patience.
  10. Lost a great CB to another project..again.
  11. Spent more time on EQ questions than actual audits.
  12. Explained the same instruction update to five different CBs.
  13. A CB misunderstood instructions... spectacularly.
  14. Instructions got updated... right after CB training.
  15. Attended a sync where the same problem was discussed for the 100th time.
  16. Tried to use the Admin Tools and got completely lost.
  17. Raised a issue knowing it won't be resolved or answered.
  18. CB asks a question that's already explained in a pinned post.
  19. Got a passive-aggressive response in the Community Forum.
  20. Answered a CBs question in a slightly mean tone and regretted it.
  21. Answered a dumb question without sarcasm.
  22. Had that one day where everything went well! (Surprisingly...)
  23. Realized the STO still hasn’t clarified an important question.
  24. Was too busy to go over the reported CB issues.
  25. Attended a meeting that could have been a slack message.
  26. Got a mean message from a CB.
  27. Reminded a CB to read the guidelines... again
  28. STOs say that you need more reviewers... but that's all you have.
  29. Finally got an answer from the STO... three days later.