Wrotedocumentationin rhyme orhaiku (just forfun!)Experiencedacollaborationthat didn’t goas plannedCollaboratedwith ACEteams forquirky projectsor initiativesGotfeedbackfrom a non-technicalaudienceFelt trulyaligned withanotherteam’s goalsDesigned amascot orcharacter fora help siteCo-presentedwithsomeonefrom anotherdepartmentContributed toa cross-functionalproject thatsurprised themLearned anew tool orprocess fromanotherteamDiscovered atypo or errorin a high-profilereleaseParticipatedin a docsprint withsnacks andmusicAdvocatedfor theirteam’sprioritiesBenefitedfrom anotherteam’ssupportCreated afunonboardingguide fornew writersCreated ameme or comicto explain atechnicalconceptWorked witha team in adifferenttime zoneExplainedtheir team’swork toothersWrotetheir firstuser guideor manualMediatedbetweenteams duringa conflictDiscoveredunexpectedcommonground withanother teamSharedresources orknowledgeacrossteamsHelped inonboarding ortrainingsomeone froma different teamHosted a“DocumentationKaraoke”sessionAdjustedtheirworkflow foranotherteamAccidentallypublished adraft with anerror andscrambled to fixitGot creativewithplaceholdertextWrotedocumentationfor a productthey had neverusedAttended across-teamtraining orworkshop thatthey enjoyedCreated ascavengerhunt usinghelp articlesMade ablooper reel ofdocumentationmistakesParticipated ina jointbrainstormingsession that ledto abreakthroughTurned aboringtopic into afun tutorialCelebrated across-teamachievementorrecognitionNavigateddifferentcommunicationstylesHandledconflictingfeedbackfrom multipleteamsTurned aconfusingfeature into aclear userguideWrote a “dayin the life”story for auser personaReceivedunexpectedpraise froma developerCreated afun glossaryof teamjargonCreatedanimatedGIFs for userinstructionsCollaboratedwith supportto write wittyauto-repliesLearnedabout anotherteam’s cultureor ritualsBuilt acollaborationthat turned intoa long-termpartnershipCollaboratedwith a teamthey hadnever workedwith beforeUsed humor indocumentation(and got awaywith it)TurnedFAQs intoa comicstripWrote helpcontent for agame orgamified appExperienced amoment ofmiscommunication—and resolved itShadowedor observedanotherteamWrote a fakechangelogfor AprilFool’s DayFree!Wrotedocumentationin rhyme orhaiku (just forfun!)Experiencedacollaborationthat didn’t goas plannedCollaboratedwith ACEteams forquirky projectsor initiativesGotfeedbackfrom a non-technicalaudienceFelt trulyaligned withanotherteam’s goalsDesigned amascot orcharacter fora help siteCo-presentedwithsomeonefrom anotherdepartmentContributed toa cross-functionalproject thatsurprised themLearned anew tool orprocess fromanotherteamDiscovered atypo or errorin a high-profilereleaseParticipatedin a docsprint withsnacks andmusicAdvocatedfor theirteam’sprioritiesBenefitedfrom anotherteam’ssupportCreated afunonboardingguide fornew writersCreated ameme or comicto explain atechnicalconceptWorked witha team in adifferenttime zoneExplainedtheir team’swork toothersWrotetheir firstuser guideor manualMediatedbetweenteams duringa conflictDiscoveredunexpectedcommonground withanother teamSharedresources orknowledgeacrossteamsHelped inonboarding ortrainingsomeone froma different teamHosted a“DocumentationKaraoke”sessionAdjustedtheirworkflow foranotherteamAccidentallypublished adraft with anerror andscrambled to fixitGot creativewithplaceholdertextWrotedocumentationfor a productthey had neverusedAttended across-teamtraining orworkshop thatthey enjoyedCreated ascavengerhunt usinghelp articlesMade ablooper reel ofdocumentationmistakesParticipated ina jointbrainstormingsession that ledto abreakthroughTurned aboringtopic into afun tutorialCelebrated across-teamachievementorrecognitionNavigateddifferentcommunicationstylesHandledconflictingfeedbackfrom multipleteamsTurned aconfusingfeature into aclear userguideWrote a “dayin the life”story for auser personaReceivedunexpectedpraise froma developerCreated afun glossaryof teamjargonCreatedanimatedGIFs for userinstructionsCollaboratedwith supportto write wittyauto-repliesLearnedabout anotherteam’s cultureor ritualsBuilt acollaborationthat turned intoa long-termpartnershipCollaboratedwith a teamthey hadnever workedwith beforeUsed humor indocumentation(and got awaywith it)TurnedFAQs intoa comicstripWrote helpcontent for agame orgamified appExperienced amoment ofmiscommunication—and resolved itShadowedor observedanotherteamWrote a fakechangelogfor AprilFool’s DayFree!

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