Gamification without the Garbage
summary
Argues that scoreboards and leaderboards are corrosive and instead teams should design agency—concrete goals, rules, and abilities—using game design methods. Cites TryHackMe capture-the-flag (docker VMs, Discord group) as effective because of collaborative puzzles not points; recommends ensemble/mob programming, non-blocking or paired reviews, trunk-based development, observability and on-call as abilities that enable flow. Calls refactoring and DevOps automation engine building, warns OKRs/KPIs can cause value capture (events signup → useless leads).
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:03TryHackMe gamification turning point
- 4:19Scoreboards and leaderboards fail
- 7:11Gamification harms teamwork
- 9:19Work as a game
- 13:14Games designed agency
- 14:17Flow in teams
- 17:07Designing team abilities
- 19:10Rules shape interactions
- 22:00Team process examples
- 23:03Engineering team capabilities
- 26:14Value clarity challenge
- 28:40Accidental gamification dangers
- 30:24Balancing OKRs
- 31:50Contrasting team goals
- 33:16Atoms of work
- 35:40Single-player to multiplayer
- 36:43Heuristics in teams
- 37:47Software as learning
- 39:13Crafting agency at work
- 40:59Learning together
- 41:21Q&A
related talks
54mGoing Deep on Gamification
40mDesigning Gamification for Good
57mGame On! Gamifying Your Apps for Fun and Profit
29mFun Ways to Learn and Engage in Software Development
21mBeyond Metrics: Using Behavioral Design to Drive Quality in Software Projects
03mThe Cost of Reward: A Critical Reflection on the `What', `How', and `Why' of Gamification for...
47mPowerful gamification
11mGamification - Falling Down the Leader Board?