Got creativewithplaceholdertextMade ablooper reel ofdocumentationmistakesMediatedbetweenteams duringa conflictReceivedunexpectedpraise froma developerCreated afun glossaryof teamjargonWrote a “dayin the life”story for auser personaGotfeedbackfrom a non-technicalaudienceCreatedanimatedGIFs for userinstructionsFree!Experiencedacollaborationthat didn’t goas plannedCreated afunonboardingguide fornew writersBuilt acollaborationthat turned intoa long-termpartnershipTurnedFAQs intoa comicstripCollaboratedwith supportto write wittyauto-repliesDiscovered atypo or errorin a high-profilereleaseCo-presentedwithsomeonefrom anotherdepartmentAdvocatedfor theirteam’sprioritiesDesigned amascot orcharacter fora help siteFelt trulyaligned withanotherteam’s goalsLearnedabout anotherteam’s cultureor ritualsLearned anew tool orprocess fromanotherteamUsed humor indocumentation(and got awaywith it)Shadowedor observedanotherteamTurned aboringtopic into afun tutorialBenefitedfrom anotherteam’ssupportAdjustedtheirworkflow foranotherteamDiscoveredunexpectedcommonground withanother teamHosted a“DocumentationKaraoke”sessionTurned aconfusingfeature into aclear userguideHandledconflictingfeedbackfrom multipleteamsAccidentallypublished adraft with anerror andscrambled to fixitParticipatedin a docsprint withsnacks andmusicHelped inonboarding ortrainingsomeone froma different teamNavigateddifferentcommunicationstylesParticipated ina jointbrainstormingsession that ledto abreakthroughExplainedtheir team’swork toothersWrotedocumentationfor a productthey had neverusedCollaboratedwith ACEteams forquirky projectsor initiativesCreated ascavengerhunt usinghelp articlesAttended across-teamtraining orworkshop thatthey enjoyedCelebrated across-teamachievementorrecognitionWorked witha team in adifferenttime zoneWrote a fakechangelogfor AprilFool’s DayWrote helpcontent for agame orgamified appExperienced amoment ofmiscommunication—and resolved itSharedresources orknowledgeacrossteamsWrotetheir firstuser guideor manualCollaboratedwith a teamthey hadnever workedwith beforeCreated ameme or comicto explain atechnicalconceptWrotedocumentationin rhyme orhaiku (just forfun!)Contributed toa cross-functionalproject thatsurprised themGot creativewithplaceholdertextMade ablooper reel ofdocumentationmistakesMediatedbetweenteams duringa conflictReceivedunexpectedpraise froma developerCreated afun glossaryof teamjargonWrote a “dayin the life”story for auser personaGotfeedbackfrom a non-technicalaudienceCreatedanimatedGIFs for userinstructionsFree!Experiencedacollaborationthat didn’t goas plannedCreated afunonboardingguide fornew writersBuilt acollaborationthat turned intoa long-termpartnershipTurnedFAQs intoa comicstripCollaboratedwith supportto write wittyauto-repliesDiscovered atypo or errorin a high-profilereleaseCo-presentedwithsomeonefrom anotherdepartmentAdvocatedfor theirteam’sprioritiesDesigned amascot orcharacter fora help siteFelt trulyaligned withanotherteam’s goalsLearnedabout anotherteam’s cultureor ritualsLearned anew tool orprocess fromanotherteamUsed humor indocumentation(and got awaywith it)Shadowedor observedanotherteamTurned aboringtopic into afun tutorialBenefitedfrom anotherteam’ssupportAdjustedtheirworkflow foranotherteamDiscoveredunexpectedcommonground withanother teamHosted a“DocumentationKaraoke”sessionTurned aconfusingfeature into aclear userguideHandledconflictingfeedbackfrom multipleteamsAccidentallypublished adraft with anerror andscrambled to fixitParticipatedin a docsprint withsnacks andmusicHelped inonboarding ortrainingsomeone froma different teamNavigateddifferentcommunicationstylesParticipated ina jointbrainstormingsession that ledto abreakthroughExplainedtheir team’swork toothersWrotedocumentationfor a productthey had neverusedCollaboratedwith ACEteams forquirky projectsor initiativesCreated ascavengerhunt usinghelp articlesAttended across-teamtraining orworkshop thatthey enjoyedCelebrated across-teamachievementorrecognitionWorked witha team in adifferenttime zoneWrote a fakechangelogfor AprilFool’s DayWrote helpcontent for agame orgamified appExperienced amoment ofmiscommunication—and resolved itSharedresources orknowledgeacrossteamsWrotetheir firstuser guideor manualCollaboratedwith a teamthey hadnever workedwith beforeCreated ameme or comicto explain atechnicalconceptWrotedocumentationin rhyme orhaiku (just forfun!)Contributed toa cross-functionalproject thatsurprised them

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