Wrotedocumentationin rhyme orhaiku (just forfun!)Created afun glossaryof teamjargonUsed humor indocumentation(and got awaywith it)Handledconflictingfeedbackfrom multipleteamsCollaboratedwith a teamthey hadnever workedwith beforeWrotetheir firstuser guideor manualNavigateddifferentcommunicationstylesExperiencedacollaborationthat didn’t goas plannedCelebrated across-teamachievementorrecognitionBenefitedfrom anotherteam’ssupportShadowedor observedanotherteamExplainedtheir team’swork toothersParticipated ina jointbrainstormingsession that ledto abreakthroughCreated ameme or comicto explain atechnicalconceptAttended across-teamtraining orworkshop thatthey enjoyedAdvocatedfor theirteam’sprioritiesCo-presentedwithsomeonefrom anotherdepartmentLearned anew tool orprocess fromanotherteamCreated afunonboardingguide fornew writersCreatedanimatedGIFs for userinstructionsWrote a “dayin the life”story for auser personaBuilt acollaborationthat turned intoa long-termpartnershipDiscovered atypo or errorin a high-profilereleaseFelt trulyaligned withanotherteam’s goalsGotfeedbackfrom a non-technicalaudienceParticipatedin a docsprint withsnacks andmusicGot creativewithplaceholdertextSharedresources orknowledgeacrossteamsDiscoveredunexpectedcommonground withanother teamWrotedocumentationfor a productthey had neverusedFree!Learnedabout anotherteam’s cultureor ritualsWrote a fakechangelogfor AprilFool’s DayTurned aconfusingfeature into aclear userguideWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerAdjustedtheirworkflow foranotherteamTurnedFAQs intoa comicstripMediatedbetweenteams duringa conflictHosted a“DocumentationKaraoke”sessionWrote helpcontent for agame orgamified appCreated ascavengerhunt usinghelp articlesDesigned amascot orcharacter fora help siteCollaboratedwith supportto write wittyauto-repliesAccidentallypublished adraft with anerror andscrambled to fixitMade ablooper reel ofdocumentationmistakesCollaboratedwith ACEteams forquirky projectsor initiativesContributed toa cross-functionalproject thatsurprised themExperienced amoment ofmiscommunication—and resolved itHelped inonboarding ortrainingsomeone froma different teamTurned aboringtopic into afun tutorialWrotedocumentationin rhyme orhaiku (just forfun!)Created afun glossaryof teamjargonUsed humor indocumentation(and got awaywith it)Handledconflictingfeedbackfrom multipleteamsCollaboratedwith a teamthey hadnever workedwith beforeWrotetheir firstuser guideor manualNavigateddifferentcommunicationstylesExperiencedacollaborationthat didn’t goas plannedCelebrated across-teamachievementorrecognitionBenefitedfrom anotherteam’ssupportShadowedor observedanotherteamExplainedtheir team’swork toothersParticipated ina jointbrainstormingsession that ledto abreakthroughCreated ameme or comicto explain atechnicalconceptAttended across-teamtraining orworkshop thatthey enjoyedAdvocatedfor theirteam’sprioritiesCo-presentedwithsomeonefrom anotherdepartmentLearned anew tool orprocess fromanotherteamCreated afunonboardingguide fornew writersCreatedanimatedGIFs for userinstructionsWrote a “dayin the life”story for auser personaBuilt acollaborationthat turned intoa long-termpartnershipDiscovered atypo or errorin a high-profilereleaseFelt trulyaligned withanotherteam’s goalsGotfeedbackfrom a non-technicalaudienceParticipatedin a docsprint withsnacks andmusicGot creativewithplaceholdertextSharedresources orknowledgeacrossteamsDiscoveredunexpectedcommonground withanother teamWrotedocumentationfor a productthey had neverusedFree!Learnedabout anotherteam’s cultureor ritualsWrote a fakechangelogfor AprilFool’s DayTurned aconfusingfeature into aclear userguideWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerAdjustedtheirworkflow foranotherteamTurnedFAQs intoa comicstripMediatedbetweenteams duringa conflictHosted a“DocumentationKaraoke”sessionWrote helpcontent for agame orgamified appCreated ascavengerhunt usinghelp articlesDesigned amascot orcharacter fora help siteCollaboratedwith supportto write wittyauto-repliesAccidentallypublished adraft with anerror andscrambled to fixitMade ablooper reel ofdocumentationmistakesCollaboratedwith ACEteams forquirky projectsor initiativesContributed toa cross-functionalproject thatsurprised themExperienced amoment ofmiscommunication—and resolved itHelped inonboarding ortrainingsomeone froma different teamTurned aboringtopic into afun tutorial

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