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

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