CreatedanimatedGIFs for userinstructionsHandledconflictingfeedbackfrom multipleteamsLearned anew tool orprocess fromanotherteamCollaboratedwith supportto write wittyauto-repliesWrote helpcontent for agame orgamified appCreated ameme or comicto explain atechnicalconceptTurned aconfusingfeature into aclear userguideContributed toa cross-functionalproject thatsurprised themHosted a“DocumentationKaraoke”sessionWorked witha team in adifferenttime zoneWrotetheir firstuser guideor manualBenefitedfrom anotherteam’ssupportGot creativewithplaceholdertextExperienced amoment ofmiscommunication—and resolved itCreated afun glossaryof teamjargonCreated afunonboardingguide fornew writersNavigateddifferentcommunicationstylesWrote a fakechangelogfor AprilFool’s DayCollaboratedwith ACEteams forquirky projectsor initiativesSharedresources orknowledgeacrossteamsAccidentallypublished adraft with anerror andscrambled to fixitCelebrated across-teamachievementorrecognitionAttended across-teamtraining orworkshop thatthey enjoyedParticipated ina jointbrainstormingsession that ledto abreakthroughCo-presentedwithsomeonefrom anotherdepartmentExperiencedacollaborationthat didn’t goas plannedCollaboratedwith a teamthey hadnever workedwith beforeTurnedFAQs intoa comicstripDesigned amascot orcharacter fora help siteTurned aboringtopic into afun tutorialExplainedtheir team’swork toothersAdvocatedfor theirteam’sprioritiesMediatedbetweenteams duringa conflictReceivedunexpectedpraise froma developerHelped inonboarding ortrainingsomeone froma different teamCreated ascavengerhunt usinghelp articlesDiscoveredunexpectedcommonground withanother teamMade ablooper reel ofdocumentationmistakesBuilt acollaborationthat turned intoa long-termpartnershipGotfeedbackfrom a non-technicalaudienceUsed humor indocumentation(and got awaywith it)Wrote a “dayin the life”story for auser personaAdjustedtheirworkflow foranotherteamWrotedocumentationin rhyme orhaiku (just forfun!)Learnedabout anotherteam’s cultureor ritualsFree!Participatedin a docsprint withsnacks andmusicWrotedocumentationfor a productthey had neverusedDiscovered atypo or errorin a high-profilereleaseShadowedor observedanotherteamFelt trulyaligned withanotherteam’s goalsCreatedanimatedGIFs for userinstructionsHandledconflictingfeedbackfrom multipleteamsLearned anew tool orprocess fromanotherteamCollaboratedwith supportto write wittyauto-repliesWrote helpcontent for agame orgamified appCreated ameme or comicto explain atechnicalconceptTurned aconfusingfeature into aclear userguideContributed toa cross-functionalproject thatsurprised themHosted a“DocumentationKaraoke”sessionWorked witha team in adifferenttime zoneWrotetheir firstuser guideor manualBenefitedfrom anotherteam’ssupportGot creativewithplaceholdertextExperienced amoment ofmiscommunication—and resolved itCreated afun glossaryof teamjargonCreated afunonboardingguide fornew writersNavigateddifferentcommunicationstylesWrote a fakechangelogfor AprilFool’s DayCollaboratedwith ACEteams forquirky projectsor initiativesSharedresources orknowledgeacrossteamsAccidentallypublished adraft with anerror andscrambled to fixitCelebrated across-teamachievementorrecognitionAttended across-teamtraining orworkshop thatthey enjoyedParticipated ina jointbrainstormingsession that ledto abreakthroughCo-presentedwithsomeonefrom anotherdepartmentExperiencedacollaborationthat didn’t goas plannedCollaboratedwith a teamthey hadnever workedwith beforeTurnedFAQs intoa comicstripDesigned amascot orcharacter fora help siteTurned aboringtopic into afun tutorialExplainedtheir team’swork toothersAdvocatedfor theirteam’sprioritiesMediatedbetweenteams duringa conflictReceivedunexpectedpraise froma developerHelped inonboarding ortrainingsomeone froma different teamCreated ascavengerhunt usinghelp articlesDiscoveredunexpectedcommonground withanother teamMade ablooper reel ofdocumentationmistakesBuilt acollaborationthat turned intoa long-termpartnershipGotfeedbackfrom a non-technicalaudienceUsed humor indocumentation(and got awaywith it)Wrote a “dayin the life”story for auser personaAdjustedtheirworkflow foranotherteamWrotedocumentationin rhyme orhaiku (just forfun!)Learnedabout anotherteam’s cultureor ritualsFree!Participatedin a docsprint withsnacks andmusicWrotedocumentationfor a productthey had neverusedDiscovered atypo or errorin a high-profilereleaseShadowedor observedanotherteamFelt trulyaligned withanotherteam’s goals

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