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

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