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