Everyone's a player (in a mid-90s MUD)
summary
Claim: applying Player Type Theory to documentation increases contributions by matching strategies to motivations. Practical tools include templates and publishing workflows, public review stats and author visibility, a centralized knowledge base, lightweight gamification, and written follow-ups for accountability. The uploader reports decades‑old theory adapted to a 130‑person IT context, with 12 years of knowledge‑base work and concrete wins: filled persistent gaps, faster reviews, and fewer blocking delays when explorers, achievers, socializers and gatekeepers get targeted support.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 0:47Outline
- 1:25My accent
- 1:51My job
- 2:53Complexity
- 4:07Documentation Needs
- 5:22Personas
- 6:10Sprout
- 7:05Turnip
- 8:17Kale
- 9:20Broccoli
- 10:26Garden Path
- 10:48MUD
- 12:06Types of players
- 12:26Interaction and act
- 12:47Socializers
- 13:01Explorers
- 13:22Achievers
- 15:03Documentation
- 15:25Explorers vs Achievers
- 15:43Work Environments
- 16:50Competitors
- 17:12Sprouts
- 17:25Kale Broccoli
- 18:02Sprout Documentation
- 20:10Kale Documentation
- 20:59Broccoli Documentation
- 21:40Federal Drama
- 22:08Practical Solutions
- 22:28Twofront approach
- 23:05Advocate for them
- 23:24Public kudos
- 23:46Reframing strategies
- 24:49Templates
- 25:46Gamification
- 27:38Killers
related talks
52m"Is this fun?": Practical tactics to integrate player insight throughout development
33mCheat Code, Combo, or Power-Up? Why We Choose Someone Else's Code
31mMacGyvering your Docs
40mDocumentation as User Experience
49mHow To Support Learning in Multiplayer Games.
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
40mGames User Research Throughout the Development Process and Beyond!
37mFrameworks for developing developers