Receivedunexpectedpraise froma developerCollaboratedwith supportto write wittyauto-repliesDesigned amascot orcharacter fora help siteWrotedocumentationfor a productthey had neverusedHosted a“DocumentationKaraoke”sessionAttended across-teamtraining orworkshop thatthey enjoyedBenefitedfrom anotherteam’ssupportMediatedbetweenteams duringa conflictCreated ascavengerhunt usinghelp articlesGotfeedbackfrom a non-technicalaudienceExperiencedacollaborationthat didn’t goas plannedAccidentallypublished adraft with anerror andscrambled to fixitWrote a fakechangelogfor AprilFool’s DayCreated afun glossaryof teamjargonTurnedFAQs intoa comicstripWorked witha team in adifferenttime zoneNavigateddifferentcommunicationstylesWrotetheir firstuser guideor manualDiscoveredunexpectedcommonground withanother teamWrotedocumentationin rhyme orhaiku (just forfun!)Explainedtheir team’swork toothersAdjustedtheirworkflow foranotherteamCreated afunonboardingguide fornew writersCelebrated across-teamachievementorrecognitionExperienced amoment ofmiscommunication—and resolved itTurned aboringtopic into afun tutorialUsed humor indocumentation(and got awaywith it)Participatedin a docsprint withsnacks andmusicWrote a “dayin the life”story for auser personaHandledconflictingfeedbackfrom multipleteamsCo-presentedwithsomeonefrom anotherdepartmentBuilt acollaborationthat turned intoa long-termpartnershipSharedresources orknowledgeacrossteamsFree!Learned anew tool orprocess fromanotherteamFelt trulyaligned withanotherteam’s goalsDiscovered atypo or errorin a high-profilereleaseGot creativewithplaceholdertextCreated ameme or comicto explain atechnicalconceptCollaboratedwith ACEteams forquirky projectsor initiativesHelped inonboarding ortrainingsomeone froma different teamWrote helpcontent for agame orgamified appShadowedor observedanotherteamAdvocatedfor theirteam’sprioritiesTurned aconfusingfeature into aclear userguideLearnedabout anotherteam’s cultureor ritualsContributed toa cross-functionalproject thatsurprised themCreatedanimatedGIFs for userinstructionsParticipated ina jointbrainstormingsession that ledto abreakthroughMade ablooper reel ofdocumentationmistakesCollaboratedwith a teamthey hadnever workedwith beforeReceivedunexpectedpraise froma developerCollaboratedwith supportto write wittyauto-repliesDesigned amascot orcharacter fora help siteWrotedocumentationfor a productthey had neverusedHosted a“DocumentationKaraoke”sessionAttended across-teamtraining orworkshop thatthey enjoyedBenefitedfrom anotherteam’ssupportMediatedbetweenteams duringa conflictCreated ascavengerhunt usinghelp articlesGotfeedbackfrom a non-technicalaudienceExperiencedacollaborationthat didn’t goas plannedAccidentallypublished adraft with anerror andscrambled to fixitWrote a fakechangelogfor AprilFool’s DayCreated afun glossaryof teamjargonTurnedFAQs intoa comicstripWorked witha team in adifferenttime zoneNavigateddifferentcommunicationstylesWrotetheir firstuser guideor manualDiscoveredunexpectedcommonground withanother teamWrotedocumentationin rhyme orhaiku (just forfun!)Explainedtheir team’swork toothersAdjustedtheirworkflow foranotherteamCreated afunonboardingguide fornew writersCelebrated across-teamachievementorrecognitionExperienced amoment ofmiscommunication—and resolved itTurned aboringtopic into afun tutorialUsed humor indocumentation(and got awaywith it)Participatedin a docsprint withsnacks andmusicWrote a “dayin the life”story for auser personaHandledconflictingfeedbackfrom multipleteamsCo-presentedwithsomeonefrom anotherdepartmentBuilt acollaborationthat turned intoa long-termpartnershipSharedresources orknowledgeacrossteamsFree!Learned anew tool orprocess fromanotherteamFelt trulyaligned withanotherteam’s goalsDiscovered atypo or errorin a high-profilereleaseGot creativewithplaceholdertextCreated ameme or comicto explain atechnicalconceptCollaboratedwith ACEteams forquirky projectsor initiativesHelped inonboarding ortrainingsomeone froma different teamWrote helpcontent for agame orgamified appShadowedor observedanotherteamAdvocatedfor theirteam’sprioritiesTurned aconfusingfeature into aclear userguideLearnedabout anotherteam’s cultureor ritualsContributed toa cross-functionalproject thatsurprised themCreatedanimatedGIFs for userinstructionsParticipated ina jointbrainstormingsession that ledto abreakthroughMade ablooper reel ofdocumentationmistakesCollaboratedwith a teamthey hadnever workedwith before

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