Accidentallypublished adraft with anerror andscrambled to fixitLearnedabout anotherteam’s cultureor ritualsCollaboratedwith a teamthey hadnever workedwith beforeHosted a“DocumentationKaraoke”sessionFree!Wrote a “dayin the life”story for auser personaBuilt acollaborationthat turned intoa long-termpartnershipWrotetheir firstuser guideor manualMediatedbetweenteams duringa conflictWrote a fakechangelogfor AprilFool’s DayBenefitedfrom anotherteam’ssupportGotfeedbackfrom a non-technicalaudienceReceivedunexpectedpraise froma developerContributed toa cross-functionalproject thatsurprised themCreated afun glossaryof teamjargonWrote helpcontent for agame orgamified appParticipated ina jointbrainstormingsession that ledto abreakthroughAdjustedtheirworkflow foranotherteamWorked witha team in adifferenttime zoneGot creativewithplaceholdertextHandledconflictingfeedbackfrom multipleteamsCollaboratedwith ACEteams forquirky projectsor initiativesExperiencedacollaborationthat didn’t goas plannedUsed humor indocumentation(and got awaywith it)CreatedanimatedGIFs for userinstructionsDiscovered atypo or errorin a high-profilereleaseMade ablooper reel ofdocumentationmistakesTurned aboringtopic into afun tutorialCreated afunonboardingguide fornew writersParticipatedin a docsprint withsnacks andmusicExperienced amoment ofmiscommunication—and resolved itShadowedor observedanotherteamWrotedocumentationin rhyme orhaiku (just forfun!)Collaboratedwith supportto write wittyauto-repliesDesigned amascot orcharacter fora help siteFelt trulyaligned withanotherteam’s goalsCreated ameme or comicto explain atechnicalconceptCo-presentedwithsomeonefrom anotherdepartmentTurnedFAQs intoa comicstripCreated ascavengerhunt usinghelp articlesHelped inonboarding ortrainingsomeone froma different teamWrotedocumentationfor a productthey had neverusedCelebrated across-teamachievementorrecognitionAttended across-teamtraining orworkshop thatthey enjoyedExplainedtheir team’swork toothersTurned aconfusingfeature into aclear userguideSharedresources orknowledgeacrossteamsDiscoveredunexpectedcommonground withanother teamAdvocatedfor theirteam’sprioritiesNavigateddifferentcommunicationstylesLearned anew tool orprocess fromanotherteamAccidentallypublished adraft with anerror andscrambled to fixitLearnedabout anotherteam’s cultureor ritualsCollaboratedwith a teamthey hadnever workedwith beforeHosted a“DocumentationKaraoke”sessionFree!Wrote a “dayin the life”story for auser personaBuilt acollaborationthat turned intoa long-termpartnershipWrotetheir firstuser guideor manualMediatedbetweenteams duringa conflictWrote a fakechangelogfor AprilFool’s DayBenefitedfrom anotherteam’ssupportGotfeedbackfrom a non-technicalaudienceReceivedunexpectedpraise froma developerContributed toa cross-functionalproject thatsurprised themCreated afun glossaryof teamjargonWrote helpcontent for agame orgamified appParticipated ina jointbrainstormingsession that ledto abreakthroughAdjustedtheirworkflow foranotherteamWorked witha team in adifferenttime zoneGot creativewithplaceholdertextHandledconflictingfeedbackfrom multipleteamsCollaboratedwith ACEteams forquirky projectsor initiativesExperiencedacollaborationthat didn’t goas plannedUsed humor indocumentation(and got awaywith it)CreatedanimatedGIFs for userinstructionsDiscovered atypo or errorin a high-profilereleaseMade ablooper reel ofdocumentationmistakesTurned aboringtopic into afun tutorialCreated afunonboardingguide fornew writersParticipatedin a docsprint withsnacks andmusicExperienced amoment ofmiscommunication—and resolved itShadowedor observedanotherteamWrotedocumentationin rhyme orhaiku (just forfun!)Collaboratedwith supportto write wittyauto-repliesDesigned amascot orcharacter fora help siteFelt trulyaligned withanotherteam’s goalsCreated ameme or comicto explain atechnicalconceptCo-presentedwithsomeonefrom anotherdepartmentTurnedFAQs intoa comicstripCreated ascavengerhunt usinghelp articlesHelped inonboarding ortrainingsomeone froma different teamWrotedocumentationfor a productthey had neverusedCelebrated across-teamachievementorrecognitionAttended across-teamtraining orworkshop thatthey enjoyedExplainedtheir team’swork toothersTurned aconfusingfeature into aclear userguideSharedresources orknowledgeacrossteamsDiscoveredunexpectedcommonground withanother teamAdvocatedfor theirteam’sprioritiesNavigateddifferentcommunicationstylesLearned anew tool orprocess fromanotherteam

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