Spillingcoffee/tea onyour desk orequipment.Forgettingabout adeadline orsubmittingsomething late.Deleting oroverwritinga shareddocument.Relying tooheavily on asingle metric,ignoring thebigger pictureNot followingup with a clientafter a majorupdate ordecision point.Scheduling ameeting withoutrealizing itoverlaps withanother keyevent.Forgettingto attacha file to anemail."Rolling thedice" toomuch onpotential scaleor a forecastExplaininga featurewrong toa client.Accidentallychangingsettings inthe platform.Mutingyourself (or notmuting!) at thewrong time ina meeting.Accidentallyhitting "ReplyAll" insteadof "Reply."Forgetting togive credit toa teammatefor theirwork.Sharing thewrongscreenduring avideo call.Givingfeedback thatcame acrosstoo harsh orunclear.Recommendingsomething thatdidn't work inthe end.Forgetting tosaveprogress ona project ordocument.Failing toaccount forplatformlimitations ina proposal.Callingsomeone bythe wrongname in ameeting.Promising adelivery datewithoutconsultingthe team first.Overloadingclients withtoo muchtechnicaljargonOverpromisingsomething andrealizing it'snot achievable.Inviting toomany peopleunnecessarilyto a meeting.Misinterpretinga brief by notlistening or notasking enoughquestions.Spillingcoffee/tea onyour desk orequipment.Forgettingabout adeadline orsubmittingsomething late.Deleting oroverwritinga shareddocument.Relying tooheavily on asingle metric,ignoring thebigger pictureNot followingup with a clientafter a majorupdate ordecision point.Scheduling ameeting withoutrealizing itoverlaps withanother keyevent.Forgettingto attacha file to anemail."Rolling thedice" toomuch onpotential scaleor a forecastExplaininga featurewrong toa client.Accidentallychangingsettings inthe platform.Mutingyourself (or notmuting!) at thewrong time ina meeting.Accidentallyhitting "ReplyAll" insteadof "Reply."Forgetting togive credit toa teammatefor theirwork.Sharing thewrongscreenduring avideo call.Givingfeedback thatcame acrosstoo harsh orunclear.Recommendingsomething thatdidn't work inthe end.Forgetting tosaveprogress ona project ordocument.Failing toaccount forplatformlimitations ina proposal.Callingsomeone bythe wrongname in ameeting.Promising adelivery datewithoutconsultingthe team first.Overloadingclients withtoo muchtechnicaljargonOverpromisingsomething andrealizing it'snot achievable.Inviting toomany peopleunnecessarilyto a meeting.Misinterpretinga brief by notlistening or notasking enoughquestions.

F*CK UP - 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
  1. Spilling coffee/tea on your desk or equipment.
  2. Forgetting about a deadline or submitting something late.
  3. Deleting or overwriting a shared document.
  4. Relying too heavily on a single metric, ignoring the bigger picture
  5. Not following up with a client after a major update or decision point.
  6. Scheduling a meeting without realizing it overlaps with another key event.
  7. Forgetting to attach a file to an email.
  8. "Rolling the dice" too much on potential scale or a forecast
  9. Explaining a feature wrong to a client.
  10. Accidentally changing settings in the platform.
  11. Muting yourself (or not muting!) at the wrong time in a meeting.
  12. Accidentally hitting "Reply All" instead of "Reply."
  13. Forgetting to give credit to a teammate for their work.
  14. Sharing the wrong screen during a video call.
  15. Giving feedback that came across too harsh or unclear.
  16. Recommending something that didn't work in the end.
  17. Forgetting to save progress on a project or document.
  18. Failing to account for platform limitations in a proposal.
  19. Calling someone by the wrong name in a meeting.
  20. Promising a delivery date without consulting the team first.
  21. Overloading clients with too much technical jargon
  22. Overpromising something and realizing it's not achievable.
  23. Inviting too many people unnecessarily to a meeting.
  24. Misinterpreting a brief by not listening or not asking enough questions.