NavigateddifferentcommunicationstylesWrotetheir firstuser guideor manualHosted a“DocumentationKaraoke”sessionWrote helpcontent for agame orgamified appBenefitedfrom anotherteam’ssupportCreated afunonboardingguide fornew writersCo-presentedwithsomeonefrom anotherdepartmentLearnedabout anotherteam’s cultureor ritualsGot creativewithplaceholdertextTurned aboringtopic into afun tutorialShadowedor observedanotherteamCollaboratedwith a teamthey hadnever workedwith beforeParticipated ina jointbrainstormingsession that ledto abreakthroughGotfeedbackfrom a non-technicalaudienceUsed humor indocumentation(and got awaywith it)Made ablooper reel ofdocumentationmistakesFelt trulyaligned withanotherteam’s goalsWrotedocumentationin rhyme orhaiku (just forfun!)Created afun glossaryof teamjargonExperienced amoment ofmiscommunication—and resolved itExperiencedacollaborationthat didn’t goas plannedMediatedbetweenteams duringa conflictCreatedanimatedGIFs for userinstructionsCollaboratedwith supportto write wittyauto-repliesHelped inonboarding ortrainingsomeone froma different teamDesigned amascot orcharacter fora help siteCreated ameme or comicto explain atechnicalconceptCreated ascavengerhunt usinghelp articlesAdjustedtheirworkflow foranotherteamBuilt acollaborationthat turned intoa long-termpartnershipWrote a fakechangelogfor AprilFool’s DaySharedresources orknowledgeacrossteamsDiscoveredunexpectedcommonground withanother teamWrotedocumentationfor a productthey had neverusedFree!Wrote a “dayin the life”story for auser personaExplainedtheir team’swork toothersContributed toa cross-functionalproject thatsurprised themAccidentallypublished adraft with anerror andscrambled to fixitHandledconflictingfeedbackfrom multipleteamsWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerDiscovered atypo or errorin a high-profilereleaseAdvocatedfor theirteam’sprioritiesCelebrated across-teamachievementorrecognitionParticipatedin a docsprint withsnacks andmusicTurned aconfusingfeature into aclear userguideCollaboratedwith ACEteams forquirky projectsor initiativesTurnedFAQs intoa comicstripAttended across-teamtraining orworkshop thatthey enjoyedLearned anew tool orprocess fromanotherteamNavigateddifferentcommunicationstylesWrotetheir firstuser guideor manualHosted a“DocumentationKaraoke”sessionWrote helpcontent for agame orgamified appBenefitedfrom anotherteam’ssupportCreated afunonboardingguide fornew writersCo-presentedwithsomeonefrom anotherdepartmentLearnedabout anotherteam’s cultureor ritualsGot creativewithplaceholdertextTurned aboringtopic into afun tutorialShadowedor observedanotherteamCollaboratedwith a teamthey hadnever workedwith beforeParticipated ina jointbrainstormingsession that ledto abreakthroughGotfeedbackfrom a non-technicalaudienceUsed humor indocumentation(and got awaywith it)Made ablooper reel ofdocumentationmistakesFelt trulyaligned withanotherteam’s goalsWrotedocumentationin rhyme orhaiku (just forfun!)Created afun glossaryof teamjargonExperienced amoment ofmiscommunication—and resolved itExperiencedacollaborationthat didn’t goas plannedMediatedbetweenteams duringa conflictCreatedanimatedGIFs for userinstructionsCollaboratedwith supportto write wittyauto-repliesHelped inonboarding ortrainingsomeone froma different teamDesigned amascot orcharacter fora help siteCreated ameme or comicto explain atechnicalconceptCreated ascavengerhunt usinghelp articlesAdjustedtheirworkflow foranotherteamBuilt acollaborationthat turned intoa long-termpartnershipWrote a fakechangelogfor AprilFool’s DaySharedresources orknowledgeacrossteamsDiscoveredunexpectedcommonground withanother teamWrotedocumentationfor a productthey had neverusedFree!Wrote a “dayin the life”story for auser personaExplainedtheir team’swork toothersContributed toa cross-functionalproject thatsurprised themAccidentallypublished adraft with anerror andscrambled to fixitHandledconflictingfeedbackfrom multipleteamsWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerDiscovered atypo or errorin a high-profilereleaseAdvocatedfor theirteam’sprioritiesCelebrated across-teamachievementorrecognitionParticipatedin a docsprint withsnacks andmusicTurned aconfusingfeature into aclear userguideCollaboratedwith ACEteams forquirky projectsor initiativesTurnedFAQs intoa comicstripAttended across-teamtraining orworkshop thatthey enjoyedLearned anew tool orprocess fromanotherteam

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