Mediatedbetweenteams duringa conflictCreatedanimatedGIFs for userinstructionsExplainedtheir team’swork toothersCollaboratedwith a teamthey hadnever workedwith beforeAdvocatedfor theirteam’sprioritiesTurned aconfusingfeature into aclear userguideDiscovered atypo or errorin a high-profilereleaseCreated afun glossaryof teamjargonSharedresources orknowledgeacrossteamsGot creativewithplaceholdertextCreated ameme or comicto explain atechnicalconceptMade ablooper reel ofdocumentationmistakesAccidentallypublished adraft with anerror andscrambled to fixitGotfeedbackfrom a non-technicalaudienceParticipatedin a docsprint withsnacks andmusicDiscoveredunexpectedcommonground withanother teamTurned aboringtopic into afun tutorialHosted a“DocumentationKaraoke”sessionContributed toa cross-functionalproject thatsurprised themUsed humor indocumentation(and got awaywith it)Wrote helpcontent for agame orgamified appBenefitedfrom anotherteam’ssupportCreated ascavengerhunt usinghelp articlesNavigateddifferentcommunicationstylesParticipated ina jointbrainstormingsession that ledto abreakthroughShadowedor observedanotherteamHandledconflictingfeedbackfrom multipleteamsLearned anew tool orprocess fromanotherteamWrote a fakechangelogfor AprilFool’s DayFelt trulyaligned withanotherteam’s goalsExperienced amoment ofmiscommunication—and resolved itWrote a “dayin the life”story for auser personaDesigned amascot orcharacter fora help siteCollaboratedwith supportto write wittyauto-repliesCelebrated across-teamachievementorrecognitionHelped inonboarding ortrainingsomeone froma different teamWrotedocumentationin rhyme orhaiku (just forfun!)Attended across-teamtraining orworkshop thatthey enjoyedExperiencedacollaborationthat didn’t goas plannedWrotedocumentationfor a productthey had neverusedWrotetheir firstuser guideor manualAdjustedtheirworkflow foranotherteamBuilt acollaborationthat turned intoa long-termpartnershipCollaboratedwith ACEteams forquirky projectsor initiativesLearnedabout anotherteam’s cultureor ritualsFree!TurnedFAQs intoa comicstripWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerCo-presentedwithsomeonefrom anotherdepartmentCreated afunonboardingguide fornew writersMediatedbetweenteams duringa conflictCreatedanimatedGIFs for userinstructionsExplainedtheir team’swork toothersCollaboratedwith a teamthey hadnever workedwith beforeAdvocatedfor theirteam’sprioritiesTurned aconfusingfeature into aclear userguideDiscovered atypo or errorin a high-profilereleaseCreated afun glossaryof teamjargonSharedresources orknowledgeacrossteamsGot creativewithplaceholdertextCreated ameme or comicto explain atechnicalconceptMade ablooper reel ofdocumentationmistakesAccidentallypublished adraft with anerror andscrambled to fixitGotfeedbackfrom a non-technicalaudienceParticipatedin a docsprint withsnacks andmusicDiscoveredunexpectedcommonground withanother teamTurned aboringtopic into afun tutorialHosted a“DocumentationKaraoke”sessionContributed toa cross-functionalproject thatsurprised themUsed humor indocumentation(and got awaywith it)Wrote helpcontent for agame orgamified appBenefitedfrom anotherteam’ssupportCreated ascavengerhunt usinghelp articlesNavigateddifferentcommunicationstylesParticipated ina jointbrainstormingsession that ledto abreakthroughShadowedor observedanotherteamHandledconflictingfeedbackfrom multipleteamsLearned anew tool orprocess fromanotherteamWrote a fakechangelogfor AprilFool’s DayFelt trulyaligned withanotherteam’s goalsExperienced amoment ofmiscommunication—and resolved itWrote a “dayin the life”story for auser personaDesigned amascot orcharacter fora help siteCollaboratedwith supportto write wittyauto-repliesCelebrated across-teamachievementorrecognitionHelped inonboarding ortrainingsomeone froma different teamWrotedocumentationin rhyme orhaiku (just forfun!)Attended across-teamtraining orworkshop thatthey enjoyedExperiencedacollaborationthat didn’t goas plannedWrotedocumentationfor a productthey had neverusedWrotetheir firstuser guideor manualAdjustedtheirworkflow foranotherteamBuilt acollaborationthat turned intoa long-termpartnershipCollaboratedwith ACEteams forquirky projectsor initiativesLearnedabout anotherteam’s cultureor ritualsFree!TurnedFAQs intoa comicstripWorked witha team in adifferenttime zoneReceivedunexpectedpraise froma developerCo-presentedwithsomeonefrom anotherdepartmentCreated afunonboardingguide fornew writers

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