Benefitedfrom anotherteam’ssupportHosted a“DocumentationKaraoke”sessionFelt trulyaligned withanotherteam’s goalsDesigned amascot orcharacter fora help siteDiscovered atypo or errorin a high-profilereleaseBuilt acollaborationthat turned intoa long-termpartnershipCreated ascavengerhunt usinghelp articlesParticipated ina jointbrainstormingsession that ledto abreakthroughMade ablooper reel ofdocumentationmistakesAdvocatedfor theirteam’sprioritiesExplainedtheir team’swork toothersShadowedor observedanotherteamWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerAccidentallypublished adraft with anerror andscrambled to fixitWrote a fakechangelogfor AprilFool’s DayAttended across-teamtraining orworkshop thatthey enjoyedDiscoveredunexpectedcommonground withanother teamContributed toa cross-functionalproject thatsurprised themWrotetheir firstuser guideor manualCreated afunonboardingguide fornew writersLearned anew tool orprocess fromanotherteamHandledconflictingfeedbackfrom multipleteamsAdjustedtheirworkflow foranotherteamCo-presentedwithsomeonefrom anotherdepartmentUsed humor indocumentation(and got awaywith it)NavigateddifferentcommunicationstylesCreated afun glossaryof teamjargonWrote a “dayin the life”story for auser personaWrote helpcontent for agame orgamified appExperienced amoment ofmiscommunication—and resolved itTurnedFAQs intoa comicstripCreatedanimatedGIFs for userinstructionsTurned aconfusingfeature into aclear userguideCollaboratedwith ACEteams forquirky projectsor initiativesParticipatedin a docsprint withsnacks andmusicExperiencedacollaborationthat didn’t goas plannedHelped inonboarding ortrainingsomeone froma different teamSharedresources orknowledgeacrossteamsWrotedocumentationfor a productthey had neverusedCollaboratedwith supportto write wittyauto-repliesCollaboratedwith a teamthey hadnever workedwith beforeFree!Turned aboringtopic into afun tutorialGotfeedbackfrom a non-technicalaudienceLearnedabout anotherteam’s cultureor ritualsMediatedbetweenteams duringa conflictWrotedocumentationin rhyme orhaiku (just forfun!)Celebrated across-teamachievementorrecognitionCreated ameme or comicto explain atechnicalconceptGot creativewithplaceholdertextBenefitedfrom anotherteam’ssupportHosted a“DocumentationKaraoke”sessionFelt trulyaligned withanotherteam’s goalsDesigned amascot orcharacter fora help siteDiscovered atypo or errorin a high-profilereleaseBuilt acollaborationthat turned intoa long-termpartnershipCreated ascavengerhunt usinghelp articlesParticipated ina jointbrainstormingsession that ledto abreakthroughMade ablooper reel ofdocumentationmistakesAdvocatedfor theirteam’sprioritiesExplainedtheir team’swork toothersShadowedor observedanotherteamWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerAccidentallypublished adraft with anerror andscrambled to fixitWrote a fakechangelogfor AprilFool’s DayAttended across-teamtraining orworkshop thatthey enjoyedDiscoveredunexpectedcommonground withanother teamContributed toa cross-functionalproject thatsurprised themWrotetheir firstuser guideor manualCreated afunonboardingguide fornew writersLearned anew tool orprocess fromanotherteamHandledconflictingfeedbackfrom multipleteamsAdjustedtheirworkflow foranotherteamCo-presentedwithsomeonefrom anotherdepartmentUsed humor indocumentation(and got awaywith it)NavigateddifferentcommunicationstylesCreated afun glossaryof teamjargonWrote a “dayin the life”story for auser personaWrote helpcontent for agame orgamified appExperienced amoment ofmiscommunication—and resolved itTurnedFAQs intoa comicstripCreatedanimatedGIFs for userinstructionsTurned aconfusingfeature into aclear userguideCollaboratedwith ACEteams forquirky projectsor initiativesParticipatedin a docsprint withsnacks andmusicExperiencedacollaborationthat didn’t goas plannedHelped inonboarding ortrainingsomeone froma different teamSharedresources orknowledgeacrossteamsWrotedocumentationfor a productthey had neverusedCollaboratedwith supportto write wittyauto-repliesCollaboratedwith a teamthey hadnever workedwith beforeFree!Turned aboringtopic into afun tutorialGotfeedbackfrom a non-technicalaudienceLearnedabout anotherteam’s cultureor ritualsMediatedbetweenteams duringa conflictWrotedocumentationin rhyme orhaiku (just forfun!)Celebrated across-teamachievementorrecognitionCreated ameme or comicto explain atechnicalconceptGot creativewithplaceholdertext

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