Unsaved Progress Will Be Lost: Why the Game Industry Forgot How to Make Games, and How to Fix It
summary
Argues the industry is failing because collective institutional memory erodes through restructures, layoffs, tool migrations and NDAs, producing bloated teams, churned builds and repeated mistakes; historical examples (original Fallout, Half‑Life, Tomb Raider teams) contrast with today. Recommends concrete fixes: smaller teams, shorter dev cycles, invest in producers who remove blockers, hire and train juniors, preserve project context with artifacts and repeat stories (research shows repetition up to six times aids retention), and practice intentional sharing so lessons survive beyond documents.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:32Why the title Unsaved Progress Will Be Lost
- 5:02Game industry today
- 8:54How games were made
- 11:05Why the industry forgot how to make games
- 14:17Memory and identity
- 17:27Institutions forget
- 21:39Memory in game dev
- 28:25Adapting memories
- 33:37Documentation pitfalls
- 36:30Team artifacts
- 38:36Forgotten lessons
- 42:12Production sanity
- 44:40Title chasing
- 46:25Tools and autonomy
- 48:51Department fallacy
- 51:00Hiring juniors
- 52:47Controlling behaviors
- 54:56Rivalry impact
- 57:43All-star teams risks
- 58:46Conclusion and Q&A
related talks
42mThe Games Industry 2024 Survival Guide
30mWorking with Independent Developers: Lessons Learned Over the Years
31mPanel: Tutorial Mode: What Every Developer Needs To Know Before Joining the Games Industry.
50mWhere do we go from here?
59mSustainable Game Development from a Game Producer's Perspective
40mPANEL: Learning from Mistakes: The Big 'NOs!' in Game Development.
17mMistakes With Data Made During Game Development
45mTruths From the Gaming Industry | UNFILTERED