Turned aconfusingfeature into aclear userguideBenefitedfrom anotherteam’ssupportBuilt acollaborationthat turned intoa long-termpartnershipWrotetheir firstuser guideor manualTurned aboringtopic into afun tutorialExperienced amoment ofmiscommunication—and resolved itDiscoveredunexpectedcommonground withanother teamCreated ascavengerhunt usinghelp articlesWorked witha team in adifferenttime zoneCo-presentedwithsomeonefrom anotherdepartmentCreated ameme or comicto explain atechnicalconceptShadowedor observedanotherteamAdvocatedfor theirteam’sprioritiesAccidentallypublished adraft with anerror andscrambled to fixitNavigateddifferentcommunicationstylesAttended across-teamtraining orworkshop thatthey enjoyedMediatedbetweenteams duringa conflictWrote helpcontent for agame orgamified appGot creativewithplaceholdertextParticipated ina jointbrainstormingsession that ledto abreakthroughCollaboratedwith a teamthey hadnever workedwith beforeHosted a“DocumentationKaraoke”sessionMade ablooper reel ofdocumentationmistakesLearned anew tool orprocess fromanotherteamWrotedocumentationin rhyme orhaiku (just forfun!)Collaboratedwith ACEteams forquirky projectsor initiativesCelebrated across-teamachievementorrecognitionLearnedabout anotherteam’s cultureor ritualsUsed humor indocumentation(and got awaywith it)Wrotedocumentationfor a productthey had neverusedHandledconflictingfeedbackfrom multipleteamsCreatedanimatedGIFs for userinstructionsSharedresources orknowledgeacrossteamsAdjustedtheirworkflow foranotherteamFree!Gotfeedbackfrom a non-technicalaudienceDiscovered atypo or errorin a high-profilereleaseHelped inonboarding ortrainingsomeone froma different teamWrote a “dayin the life”story for auser personaParticipatedin a docsprint withsnacks andmusicContributed toa cross-functionalproject thatsurprised themTurnedFAQs intoa comicstripFelt trulyaligned withanotherteam’s goalsReceivedunexpectedpraise froma developerCreated afun glossaryof teamjargonCreated afunonboardingguide fornew writersExplainedtheir team’swork toothersCollaboratedwith supportto write wittyauto-repliesDesigned amascot orcharacter fora help siteWrote a fakechangelogfor AprilFool’s DayExperiencedacollaborationthat didn’t goas plannedTurned aconfusingfeature into aclear userguideBenefitedfrom anotherteam’ssupportBuilt acollaborationthat turned intoa long-termpartnershipWrotetheir firstuser guideor manualTurned aboringtopic into afun tutorialExperienced amoment ofmiscommunication—and resolved itDiscoveredunexpectedcommonground withanother teamCreated ascavengerhunt usinghelp articlesWorked witha team in adifferenttime zoneCo-presentedwithsomeonefrom anotherdepartmentCreated ameme or comicto explain atechnicalconceptShadowedor observedanotherteamAdvocatedfor theirteam’sprioritiesAccidentallypublished adraft with anerror andscrambled to fixitNavigateddifferentcommunicationstylesAttended across-teamtraining orworkshop thatthey enjoyedMediatedbetweenteams duringa conflictWrote helpcontent for agame orgamified appGot creativewithplaceholdertextParticipated ina jointbrainstormingsession that ledto abreakthroughCollaboratedwith a teamthey hadnever workedwith beforeHosted a“DocumentationKaraoke”sessionMade ablooper reel ofdocumentationmistakesLearned anew tool orprocess fromanotherteamWrotedocumentationin rhyme orhaiku (just forfun!)Collaboratedwith ACEteams forquirky projectsor initiativesCelebrated across-teamachievementorrecognitionLearnedabout anotherteam’s cultureor ritualsUsed humor indocumentation(and got awaywith it)Wrotedocumentationfor a productthey had neverusedHandledconflictingfeedbackfrom multipleteamsCreatedanimatedGIFs for userinstructionsSharedresources orknowledgeacrossteamsAdjustedtheirworkflow foranotherteamFree!Gotfeedbackfrom a non-technicalaudienceDiscovered atypo or errorin a high-profilereleaseHelped inonboarding ortrainingsomeone froma different teamWrote a “dayin the life”story for auser personaParticipatedin a docsprint withsnacks andmusicContributed toa cross-functionalproject thatsurprised themTurnedFAQs intoa comicstripFelt trulyaligned withanotherteam’s goalsReceivedunexpectedpraise froma developerCreated afun glossaryof teamjargonCreated afunonboardingguide fornew writersExplainedtheir team’swork toothersCollaboratedwith supportto write wittyauto-repliesDesigned amascot orcharacter fora help siteWrote a fakechangelogfor AprilFool’s DayExperiencedacollaborationthat didn’t goas planned

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