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

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