deadlineis foryesterday"C is toocomplicated,we need tocircle back""I can'tdownloadthe SVG" -cit dev to uxreg. UI files"This screen hasbeen descoped"but you learn itfrom a screenshotof a 1:1 chat inoutlook after 4weeks"seen at16:10, 10days ago""Wewould likeit likeexcel""why are theretwo differentreq lists?""It's justdifferentnaming :)""We don't likethe complexfeel" - excellikewireframes"A wasactuallygood butsimplify it"yzx: "Askxyz" - xyzdoesn'tknowWrites req. onconflu, leavescompletelydifferentcomments onfigma"Scrap B,we needC" (but noreq.)"Users won'tunderstand ifwe don't doF" dev deemF impossible"This issomething weneed toconsider" - nosigns of life for3 weeks"But why not do itthis way"proceeds tosuggest the exactsame designfrom first review."Third pagewith differentreq. appearsin conflu"Proceedsto requestsD at thelast minute"We'll do it inpost-foundation"screen never tobe heard ofagain"No, weactually don'twant this" afterreq. showed itfor 3 months."Sorry what isthis for?" citoperationsduring theirnew platformpresentation"Scrap A, weneed B"(unclearrequirements)"I can getsomeone toemail you"sends acompletelydifferent topic"I don't knowbut I wouldlike it likethis" - cit nota stakeholder"This isno longerfor day 1"UX gathersrequirements- "Who toldyou this??""We don't havetime" - requeststo revert tooriginal uxdesign 5 monthsafter handover"we needto circleback onthis""We need A(limited req.,10 nice tohave)""We wouldlike it but wedon't know ifit'll work""It wouldtake toolong togather""We don't needthat edge case"3 weeks beforeyou are askedto design thatedge caseRequirementson confluwithoutrequirements"It'simpossibleto know it"NoconfluencerequirementsBusinessagreesbut devsdon't"do you havean epic for thischange" cit.dev on alreadyagreed ux"Why arewe in thiscall?""We don'thave infoon this""What coloris thissupposed tobe" - cit. devto UX"I know youare UX butwe don't likeit" - cit. not astakeholder"We realisedwe don't havean API for this"(handover was3 months ago)"I don't like it,I want it likemy bank" -cit. not astakeholder"why did youmake it likethis, no onedoes this" -cit. dev to UX"Whorequestedthis?""I knowresearchfound A butyou know howresearch is""Thisscreenhas beendescoped""Ask zyx"- zyxsends toyzx."I find thisconfusing"deadlineis foryesterday"C is toocomplicated,we need tocircle back""I can'tdownloadthe SVG" -cit dev to uxreg. UI files"This screen hasbeen descoped"but you learn itfrom a screenshotof a 1:1 chat inoutlook after 4weeks"seen at16:10, 10days ago""Wewould likeit likeexcel""why are theretwo differentreq lists?""It's justdifferentnaming :)""We don't likethe complexfeel" - excellikewireframes"A wasactuallygood butsimplify it"yzx: "Askxyz" - xyzdoesn'tknowWrites req. onconflu, leavescompletelydifferentcomments onfigma"Scrap B,we needC" (but noreq.)"Users won'tunderstand ifwe don't doF" dev deemF impossible"This issomething weneed toconsider" - nosigns of life for3 weeks"But why not do itthis way"proceeds tosuggest the exactsame designfrom first review."Third pagewith differentreq. appearsin conflu"Proceedsto requestsD at thelast minute"We'll do it inpost-foundation"screen never tobe heard ofagain"No, weactually don'twant this" afterreq. showed itfor 3 months."Sorry what isthis for?" citoperationsduring theirnew platformpresentation"Scrap A, weneed B"(unclearrequirements)"I can getsomeone toemail you"sends acompletelydifferent topic"I don't knowbut I wouldlike it likethis" - cit nota stakeholder"This isno longerfor day 1"UX gathersrequirements- "Who toldyou this??""We don't havetime" - requeststo revert tooriginal uxdesign 5 monthsafter handover"we needto circleback onthis""We need A(limited req.,10 nice tohave)""We wouldlike it but wedon't know ifit'll work""It wouldtake toolong togather""We don't needthat edge case"3 weeks beforeyou are askedto design thatedge caseRequirementson confluwithoutrequirements"It'simpossibleto know it"NoconfluencerequirementsBusinessagreesbut devsdon't"do you havean epic for thischange" cit.dev on alreadyagreed ux"Why arewe in thiscall?""We don'thave infoon this""What coloris thissupposed tobe" - cit. devto UX"I know youare UX butwe don't likeit" - cit. not astakeholder"We realisedwe don't havean API for this"(handover was3 months ago)"I don't like it,I want it likemy bank" -cit. not astakeholder"why did youmake it likethis, no onedoes this" -cit. dev to UX"Whorequestedthis?""I knowresearchfound A butyou know howresearch is""Thisscreenhas beendescoped""Ask zyx"- zyxsends toyzx."I find thisconfusing"

Nexus 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
42
43
44
45
46
47
48
  1. deadline is for yesterday
  2. "C is too complicated, we need to circle back"
  3. "I can't download the SVG" - cit dev to ux reg. UI files
  4. "This screen has been descoped" but you learn it from a screenshot of a 1:1 chat in outlook after 4 weeks
  5. "seen at 16:10, 10 days ago"
  6. "We would like it like excel"
  7. "why are there two different req lists?" "It's just different naming :)"
  8. "We don't like the complex feel" - excel like wireframes
  9. "A was actually good but simplify it"
  10. yzx: "Ask xyz" - xyz doesn't know
  11. Writes req. on conflu, leaves completely different comments on figma
  12. "Scrap B, we need C" (but no req.)
  13. "Users won't understand if we don't do F" dev deem F impossible
  14. "This is something we need to consider" - no signs of life for 3 weeks
  15. "But why not do it this way" proceeds to suggest the exact same design from first review.
  16. "Third page with different req. appears in conflu"
  17. Proceeds to requests D at the last minute
  18. "We'll do it in post- foundation" screen never to be heard of again
  19. "No, we actually don't want this" after req. showed it for 3 months.
  20. "Sorry what is this for?" cit operations during their new platform presentation
  21. "Scrap A, we need B"(unclear requirements)
  22. "I can get someone to email you" sends a completely different topic
  23. "I don't know but I would like it like this" - cit not a stakeholder
  24. "This is no longer for day 1"
  25. UX gathers requirements - "Who told you this??"
  26. "We don't have time" - requests to revert to original ux design 5 months after handover
  27. "we need to circle back on this"
  28. "We need A (limited req., 10 nice to have)"
  29. "We would like it but we don't know if it'll work"
  30. "It would take too long to gather"
  31. "We don't need that edge case" 3 weeks before you are asked to design that edge case
  32. Requirements on conflu without requirements
  33. "It's impossible to know it"
  34. No confluence requirements
  35. Business agrees but devs don't
  36. "do you have an epic for this change" cit. dev on already agreed ux
  37. "Why are we in this call?"
  38. "We don't have info on this"
  39. "What color is this supposed to be" - cit. dev to UX
  40. "I know you are UX but we don't like it" - cit. not a stakeholder
  41. "We realised we don't have an API for this" (handover was 3 months ago)
  42. "I don't like it, I want it like my bank" - cit. not a stakeholder
  43. "why did you make it like this, no one does this" - cit. dev to UX
  44. "Who requested this?"
  45. "I know research found A but you know how research is"
  46. "This screen has been descoped"
  47. "Ask zyx" - zyx sends to yzx.
  48. "I find this confusing"