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

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