Wrote a “dayin the life”story for auser personaBuilt acollaborationthat turned intoa long-termpartnershipFree!Collaboratedwith supportto write wittyauto-repliesLearnedabout anotherteam’s cultureor ritualsAttended across-teamtraining orworkshop thatthey enjoyedUsed humor indocumentation(and got awaywith it)CreatedanimatedGIFs for userinstructionsCreated ascavengerhunt usinghelp articlesParticipatedin a docsprint withsnacks andmusicCollaboratedwith ACEteams forquirky projectsor initiativesNavigateddifferentcommunicationstylesWrotedocumentationfor a productthey had neverusedHandledconflictingfeedbackfrom multipleteamsAdvocatedfor theirteam’sprioritiesWrotetheir firstuser guideor manualTurned aconfusingfeature into aclear userguideAccidentallypublished adraft with anerror andscrambled to fixitCreated ameme or comicto explain atechnicalconceptCo-presentedwithsomeonefrom anotherdepartmentDiscovered atypo or errorin a high-profilereleaseWrote helpcontent for agame orgamified appCelebrated across-teamachievementorrecognitionDiscoveredunexpectedcommonground withanother teamTurnedFAQs intoa comicstripLearned anew tool orprocess fromanotherteamExperiencedacollaborationthat didn’t goas plannedGotfeedbackfrom a non-technicalaudienceAdjustedtheirworkflow foranotherteamDesigned amascot orcharacter fora help siteSharedresources orknowledgeacrossteamsWorked witha team in adifferenttime zoneHelped inonboarding ortrainingsomeone froma different teamExplainedtheir team’swork toothersCreated afun glossaryof teamjargonReceivedunexpectedpraise froma developerParticipated ina jointbrainstormingsession that ledto abreakthroughBenefitedfrom anotherteam’ssupportMade ablooper reel ofdocumentationmistakesCollaboratedwith a teamthey hadnever workedwith beforeGot creativewithplaceholdertextCreated afunonboardingguide fornew writersMediatedbetweenteams duringa conflictWrote a fakechangelogfor AprilFool’s DayHosted a“DocumentationKaraoke”sessionContributed toa cross-functionalproject thatsurprised themWrotedocumentationin rhyme orhaiku (just forfun!)Experienced amoment ofmiscommunication—and resolved itTurned aboringtopic into afun tutorialFelt trulyaligned withanotherteam’s goalsShadowedor observedanotherteamWrote a “dayin the life”story for auser personaBuilt acollaborationthat turned intoa long-termpartnershipFree!Collaboratedwith supportto write wittyauto-repliesLearnedabout anotherteam’s cultureor ritualsAttended across-teamtraining orworkshop thatthey enjoyedUsed humor indocumentation(and got awaywith it)CreatedanimatedGIFs for userinstructionsCreated ascavengerhunt usinghelp articlesParticipatedin a docsprint withsnacks andmusicCollaboratedwith ACEteams forquirky projectsor initiativesNavigateddifferentcommunicationstylesWrotedocumentationfor a productthey had neverusedHandledconflictingfeedbackfrom multipleteamsAdvocatedfor theirteam’sprioritiesWrotetheir firstuser guideor manualTurned aconfusingfeature into aclear userguideAccidentallypublished adraft with anerror andscrambled to fixitCreated ameme or comicto explain atechnicalconceptCo-presentedwithsomeonefrom anotherdepartmentDiscovered atypo or errorin a high-profilereleaseWrote helpcontent for agame orgamified appCelebrated across-teamachievementorrecognitionDiscoveredunexpectedcommonground withanother teamTurnedFAQs intoa comicstripLearned anew tool orprocess fromanotherteamExperiencedacollaborationthat didn’t goas plannedGotfeedbackfrom a non-technicalaudienceAdjustedtheirworkflow foranotherteamDesigned amascot orcharacter fora help siteSharedresources orknowledgeacrossteamsWorked witha team in adifferenttime zoneHelped inonboarding ortrainingsomeone froma different teamExplainedtheir team’swork toothersCreated afun glossaryof teamjargonReceivedunexpectedpraise froma developerParticipated ina jointbrainstormingsession that ledto abreakthroughBenefitedfrom anotherteam’ssupportMade ablooper reel ofdocumentationmistakesCollaboratedwith a teamthey hadnever workedwith beforeGot creativewithplaceholdertextCreated afunonboardingguide fornew writersMediatedbetweenteams duringa conflictWrote a fakechangelogfor AprilFool’s DayHosted a“DocumentationKaraoke”sessionContributed toa cross-functionalproject thatsurprised themWrotedocumentationin rhyme orhaiku (just forfun!)Experienced amoment ofmiscommunication—and resolved itTurned aboringtopic into afun tutorialFelt trulyaligned withanotherteam’s goalsShadowedor observedanotherteam

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