Wrote a “dayin the life”story for auser personaDiscovered atypo or errorin a high-profilereleaseWrote helpcontent for agame orgamified appCreated afunonboardingguide fornew writersTurned aconfusingfeature into aclear userguideLearnedabout anotherteam’s cultureor ritualsFelt trulyaligned withanotherteam’s goalsWorked witha team in adifferenttime zoneCreated ameme or comicto explain atechnicalconceptAttended across-teamtraining orworkshop thatthey enjoyedAccidentallypublished adraft with anerror andscrambled to fixitTurnedFAQs intoa comicstripGot creativewithplaceholdertextExperienced amoment ofmiscommunication—and resolved itDiscoveredunexpectedcommonground withanother teamBuilt acollaborationthat turned intoa long-termpartnershipCollaboratedwith a teamthey hadnever workedwith beforeWrotedocumentationfor a productthey had neverusedExplainedtheir team’swork toothersHelped inonboarding ortrainingsomeone froma different teamCo-presentedwithsomeonefrom anotherdepartmentMediatedbetweenteams duringa conflictHandledconflictingfeedbackfrom multipleteamsBenefitedfrom anotherteam’ssupportMade ablooper reel ofdocumentationmistakesReceivedunexpectedpraise froma developerParticipated ina jointbrainstormingsession that ledto abreakthroughShadowedor observedanotherteamWrotetheir firstuser guideor manualAdvocatedfor theirteam’sprioritiesFree!Collaboratedwith supportto write wittyauto-repliesWrote a fakechangelogfor AprilFool’s DayCelebrated across-teamachievementorrecognitionCollaboratedwith ACEteams forquirky projectsor initiativesParticipatedin a docsprint withsnacks andmusicLearned anew tool orprocess fromanotherteamWrotedocumentationin rhyme orhaiku (just forfun!)NavigateddifferentcommunicationstylesCreated afun glossaryof teamjargonCreatedanimatedGIFs for userinstructionsExperiencedacollaborationthat didn’t goas plannedCreated ascavengerhunt usinghelp articlesHosted a“DocumentationKaraoke”sessionGotfeedbackfrom a non-technicalaudienceAdjustedtheirworkflow foranotherteamTurned aboringtopic into afun tutorialSharedresources orknowledgeacrossteamsUsed humor indocumentation(and got awaywith it)Contributed toa cross-functionalproject thatsurprised themDesigned amascot orcharacter fora help siteWrote a “dayin the life”story for auser personaDiscovered atypo or errorin a high-profilereleaseWrote helpcontent for agame orgamified appCreated afunonboardingguide fornew writersTurned aconfusingfeature into aclear userguideLearnedabout anotherteam’s cultureor ritualsFelt trulyaligned withanotherteam’s goalsWorked witha team in adifferenttime zoneCreated ameme or comicto explain atechnicalconceptAttended across-teamtraining orworkshop thatthey enjoyedAccidentallypublished adraft with anerror andscrambled to fixitTurnedFAQs intoa comicstripGot creativewithplaceholdertextExperienced amoment ofmiscommunication—and resolved itDiscoveredunexpectedcommonground withanother teamBuilt acollaborationthat turned intoa long-termpartnershipCollaboratedwith a teamthey hadnever workedwith beforeWrotedocumentationfor a productthey had neverusedExplainedtheir team’swork toothersHelped inonboarding ortrainingsomeone froma different teamCo-presentedwithsomeonefrom anotherdepartmentMediatedbetweenteams duringa conflictHandledconflictingfeedbackfrom multipleteamsBenefitedfrom anotherteam’ssupportMade ablooper reel ofdocumentationmistakesReceivedunexpectedpraise froma developerParticipated ina jointbrainstormingsession that ledto abreakthroughShadowedor observedanotherteamWrotetheir firstuser guideor manualAdvocatedfor theirteam’sprioritiesFree!Collaboratedwith supportto write wittyauto-repliesWrote a fakechangelogfor AprilFool’s DayCelebrated across-teamachievementorrecognitionCollaboratedwith ACEteams forquirky projectsor initiativesParticipatedin a docsprint withsnacks andmusicLearned anew tool orprocess fromanotherteamWrotedocumentationin rhyme orhaiku (just forfun!)NavigateddifferentcommunicationstylesCreated afun glossaryof teamjargonCreatedanimatedGIFs for userinstructionsExperiencedacollaborationthat didn’t goas plannedCreated ascavengerhunt usinghelp articlesHosted a“DocumentationKaraoke”sessionGotfeedbackfrom a non-technicalaudienceAdjustedtheirworkflow foranotherteamTurned aboringtopic into afun tutorialSharedresources orknowledgeacrossteamsUsed humor indocumentation(and got awaywith it)Contributed toa cross-functionalproject thatsurprised themDesigned amascot orcharacter fora help site

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