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

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