Gotfeedbackfrom a non-technicalaudienceWrotedocumentationfor a productthey had neverusedNavigateddifferentcommunicationstylesUsed humor indocumentation(and got awaywith it)Experienced amoment ofmiscommunication—and resolved itAccidentallypublished adraft with anerror andscrambled to fixitWrotedocumentationin rhyme orhaiku (just forfun!)Wrotetheir firstuser guideor manualWrote a “dayin the life”story for auser personaCollaboratedwith a teamthey hadnever workedwith beforeCreated afunonboardingguide fornew writersWorked witha team in adifferenttime zoneLearnedabout anotherteam’s cultureor ritualsWrote a fakechangelogfor AprilFool’s DayHandledconflictingfeedbackfrom multipleteamsBenefitedfrom anotherteam’ssupportHosted a“DocumentationKaraoke”sessionDiscoveredunexpectedcommonground withanother teamTurned aconfusingfeature into aclear userguideFelt trulyaligned withanotherteam’s goalsMediatedbetweenteams duringa conflictCollaboratedwith supportto write wittyauto-repliesCollaboratedwith ACEteams forquirky projectsor initiativesExperiencedacollaborationthat didn’t goas plannedCreated afun glossaryof teamjargonShadowedor observedanotherteamCreatedanimatedGIFs for userinstructionsFree!Explainedtheir team’swork toothersCo-presentedwithsomeonefrom anotherdepartmentTurnedFAQs intoa comicstripGot creativewithplaceholdertextMade ablooper reel ofdocumentationmistakesAttended across-teamtraining orworkshop thatthey enjoyedAdjustedtheirworkflow foranotherteamDiscovered atypo or errorin a high-profilereleaseTurned aboringtopic into afun tutorialBuilt acollaborationthat turned intoa long-termpartnershipDesigned amascot orcharacter fora help siteContributed toa cross-functionalproject thatsurprised themHelped inonboarding ortrainingsomeone froma different teamLearned anew tool orprocess fromanotherteamParticipated ina jointbrainstormingsession that ledto abreakthroughAdvocatedfor theirteam’sprioritiesWrote helpcontent for agame orgamified appCreated ascavengerhunt usinghelp articlesSharedresources orknowledgeacrossteamsParticipatedin a docsprint withsnacks andmusicReceivedunexpectedpraise froma developerCelebrated across-teamachievementorrecognitionCreated ameme or comicto explain atechnicalconceptGotfeedbackfrom a non-technicalaudienceWrotedocumentationfor a productthey had neverusedNavigateddifferentcommunicationstylesUsed humor indocumentation(and got awaywith it)Experienced amoment ofmiscommunication—and resolved itAccidentallypublished adraft with anerror andscrambled to fixitWrotedocumentationin rhyme orhaiku (just forfun!)Wrotetheir firstuser guideor manualWrote a “dayin the life”story for auser personaCollaboratedwith a teamthey hadnever workedwith beforeCreated afunonboardingguide fornew writersWorked witha team in adifferenttime zoneLearnedabout anotherteam’s cultureor ritualsWrote a fakechangelogfor AprilFool’s DayHandledconflictingfeedbackfrom multipleteamsBenefitedfrom anotherteam’ssupportHosted a“DocumentationKaraoke”sessionDiscoveredunexpectedcommonground withanother teamTurned aconfusingfeature into aclear userguideFelt trulyaligned withanotherteam’s goalsMediatedbetweenteams duringa conflictCollaboratedwith supportto write wittyauto-repliesCollaboratedwith ACEteams forquirky projectsor initiativesExperiencedacollaborationthat didn’t goas plannedCreated afun glossaryof teamjargonShadowedor observedanotherteamCreatedanimatedGIFs for userinstructionsFree!Explainedtheir team’swork toothersCo-presentedwithsomeonefrom anotherdepartmentTurnedFAQs intoa comicstripGot creativewithplaceholdertextMade ablooper reel ofdocumentationmistakesAttended across-teamtraining orworkshop thatthey enjoyedAdjustedtheirworkflow foranotherteamDiscovered atypo or errorin a high-profilereleaseTurned aboringtopic into afun tutorialBuilt acollaborationthat turned intoa long-termpartnershipDesigned amascot orcharacter fora help siteContributed toa cross-functionalproject thatsurprised themHelped inonboarding ortrainingsomeone froma different teamLearned anew tool orprocess fromanotherteamParticipated ina jointbrainstormingsession that ledto abreakthroughAdvocatedfor theirteam’sprioritiesWrote helpcontent for agame orgamified appCreated ascavengerhunt usinghelp articlesSharedresources orknowledgeacrossteamsParticipatedin a docsprint withsnacks andmusicReceivedunexpectedpraise froma developerCelebrated across-teamachievementorrecognitionCreated ameme or comicto explain atechnicalconcept

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