Contributed toa cross-functionalproject thatsurprised themFelt trulyaligned withanotherteam’s goalsParticipatedin a docsprint withsnacks andmusicWrote a fakechangelogfor AprilFool’s DayCelebrated across-teamachievementorrecognitionExperienced amoment ofmiscommunication—and resolved itTurned aconfusingfeature into aclear userguideWrotetheir firstuser guideor manualAttended across-teamtraining orworkshop thatthey enjoyedExperiencedacollaborationthat didn’t goas plannedShadowedor observedanotherteamCollaboratedwith ACEteams forquirky projectsor initiativesAdjustedtheirworkflow foranotherteamBenefitedfrom anotherteam’ssupportCollaboratedwith a teamthey hadnever workedwith beforeAdvocatedfor theirteam’sprioritiesCreated afun glossaryof teamjargonCo-presentedwithsomeonefrom anotherdepartmentCreated ameme or comicto explain atechnicalconceptGot creativewithplaceholdertextTurned aboringtopic into afun tutorialParticipated ina jointbrainstormingsession that ledto abreakthroughWrotedocumentationin rhyme orhaiku (just forfun!)Discovered atypo or errorin a high-profilereleaseMade ablooper reel ofdocumentationmistakesBuilt acollaborationthat turned intoa long-termpartnershipNavigateddifferentcommunicationstylesWrote a “dayin the life”story for auser personaSharedresources orknowledgeacrossteamsDesigned amascot orcharacter fora help siteUsed humor indocumentation(and got awaywith it)CreatedanimatedGIFs for userinstructionsWorked witha team in adifferenttime zoneCreated ascavengerhunt usinghelp articlesWrotedocumentationfor a productthey had neverusedHosted a“DocumentationKaraoke”sessionMediatedbetweenteams duringa conflictCreated afunonboardingguide fornew writersLearned anew tool orprocess fromanotherteamCollaboratedwith supportto write wittyauto-repliesFree!Helped inonboarding ortrainingsomeone froma different teamHandledconflictingfeedbackfrom multipleteamsLearnedabout anotherteam’s cultureor ritualsDiscoveredunexpectedcommonground withanother teamGotfeedbackfrom a non-technicalaudienceExplainedtheir team’swork toothersTurnedFAQs intoa comicstripReceivedunexpectedpraise froma developerWrote helpcontent for agame orgamified appAccidentallypublished adraft with anerror andscrambled to fixitContributed toa cross-functionalproject thatsurprised themFelt trulyaligned withanotherteam’s goalsParticipatedin a docsprint withsnacks andmusicWrote a fakechangelogfor AprilFool’s DayCelebrated across-teamachievementorrecognitionExperienced amoment ofmiscommunication—and resolved itTurned aconfusingfeature into aclear userguideWrotetheir firstuser guideor manualAttended across-teamtraining orworkshop thatthey enjoyedExperiencedacollaborationthat didn’t goas plannedShadowedor observedanotherteamCollaboratedwith ACEteams forquirky projectsor initiativesAdjustedtheirworkflow foranotherteamBenefitedfrom anotherteam’ssupportCollaboratedwith a teamthey hadnever workedwith beforeAdvocatedfor theirteam’sprioritiesCreated afun glossaryof teamjargonCo-presentedwithsomeonefrom anotherdepartmentCreated ameme or comicto explain atechnicalconceptGot creativewithplaceholdertextTurned aboringtopic into afun tutorialParticipated ina jointbrainstormingsession that ledto abreakthroughWrotedocumentationin rhyme orhaiku (just forfun!)Discovered atypo or errorin a high-profilereleaseMade ablooper reel ofdocumentationmistakesBuilt acollaborationthat turned intoa long-termpartnershipNavigateddifferentcommunicationstylesWrote a “dayin the life”story for auser personaSharedresources orknowledgeacrossteamsDesigned amascot orcharacter fora help siteUsed humor indocumentation(and got awaywith it)CreatedanimatedGIFs for userinstructionsWorked witha team in adifferenttime zoneCreated ascavengerhunt usinghelp articlesWrotedocumentationfor a productthey had neverusedHosted a“DocumentationKaraoke”sessionMediatedbetweenteams duringa conflictCreated afunonboardingguide fornew writersLearned anew tool orprocess fromanotherteamCollaboratedwith supportto write wittyauto-repliesFree!Helped inonboarding ortrainingsomeone froma different teamHandledconflictingfeedbackfrom multipleteamsLearnedabout anotherteam’s cultureor ritualsDiscoveredunexpectedcommonground withanother teamGotfeedbackfrom a non-technicalaudienceExplainedtheir team’swork toothersTurnedFAQs intoa comicstripReceivedunexpectedpraise froma developerWrote helpcontent for agame orgamified appAccidentallypublished adraft with anerror andscrambled to fixit

InfoDev Collaboration 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
49
50
51
  1. Contributed to a cross-functional project that surprised them
  2. Felt truly aligned with another team’s goals
  3. Participated in a doc sprint with snacks and music
  4. Wrote a fake changelog for April Fool’s Day
  5. Celebrated a cross-team achievement or recognition
  6. Experienced a moment of miscommunication—and resolved it
  7. Turned a confusing feature into a clear user guide
  8. Wrote their first user guide or manual
  9. Attended a cross-team training or workshop that they enjoyed
  10. Experienced a collaboration that didn’t go as planned
  11. Shadowed or observed another team
  12. Collaborated with ACE teams for quirky projects or initiatives
  13. Adjusted their workflow for another team
  14. Benefited from another team’s support
  15. Collaborated with a team they had never worked with before
  16. Advocated for their team’s priorities
  17. Created a fun glossary of team jargon
  18. Co-presented with someone from another department
  19. Created a meme or comic to explain a technical concept
  20. Got creative with placeholder text
  21. Turned a boring topic into a fun tutorial
  22. Participated in a joint brainstorming session that led to a breakthrough
  23. Wrote documentation in rhyme or haiku (just for fun!)
  24. Discovered a typo or error in a high-profile release
  25. Made a blooper reel of documentation mistakes
  26. Built a collaboration that turned into a long-term partnership
  27. Navigated different communication styles
  28. Wrote a “day in the life” story for a user persona
  29. Shared resources or knowledge across teams
  30. Designed a mascot or character for a help site
  31. Used humor in documentation (and got away with it)
  32. Created animated GIFs for user instructions
  33. Worked with a team in a different time zone
  34. Created a scavenger hunt using help articles
  35. Wrote documentation for a product they had never used
  36. Hosted a “Documentation Karaoke” session
  37. Mediated between teams during a conflict
  38. Created a fun onboarding guide for new writers
  39. Learned a new tool or process from another team
  40. Collaborated with support to write witty auto-replies
  41. Free!
  42. Helped in onboarding or training someone from a different team
  43. Handled conflicting feedback from multiple teams
  44. Learned about another team’s culture or rituals
  45. Discovered unexpected common ground with another team
  46. Got feedback from a non-technical audience
  47. Explained their team’s work to others
  48. Turned FAQs into a comic strip
  49. Received unexpected praise from a developer
  50. Wrote help content for a game or gamified app
  51. Accidentally published a draft with an error and scrambled to fix it