Outlast the Tools: A Game Producer's Field Guide to AI
Production craft doesn't change when the tools do.
AI collaboration rewards producers who already manage context, decompose work, and evaluate output. This book explains why, and what to do with it.
Twelve chapters covering the five transferable producer skills, operational infrastructure, constraint theory, flow metrics, and how to read AI output like a status update.
Every framework here outlasts any model release. Nothing is built around a named tool.
Written by a producer with thirty years in the industry, across mobile F2P, live service, and AAA.
Game producers already have most of what AI collaboration requires. They have been managing context, decomposing work, and evaluating output for years. This book is the map from where they are to where the work is going.
The tools are moving faster than any book can track. That is not the problem this book solves.
The problem is the translation gap. Working game producers already have most of what effective AI collaboration requires. They have been managing context, decomposing work, and evaluating output from human collaborators for years. The distance between where producers are and where they need to be is shorter than the industry is making it sound.
What is missing is the map.
Outlast the Tools is that map. Across twelve chapters, it covers the five transferable producer skills, how to build an AI operational harness that runs at 98.4 per cent deterministic infrastructure, how to manage context so that work does not disappear between sessions, and how to apply constraint theory, forecasting discipline, and flow metrics to AI-integrated delivery. The final chapters cover reading AI output with the same investigative habit that experienced producers apply to status updates. Confident, fluent, and wrong is a failure mode that looks identical whether the source is a team member or a language model.
The book is deliberately tool-agnostic. No chapter is built around a named product. The field moves too fast for named recommendations to hold. Producers who build their AI workflows around a framework will outlast every model release. Producers who build around a specific tool will be rebuilding every eighteen months.
The authority here comes from the seat, not the whiteboard. Thirty years shipping games. The argument is not that AI will change everything. The argument is that the producers best positioned to lead that change are already in the building, and they are closer to ready than anyone has told them.
Table of Contents
Chapter 1: Your Expertise Is Invisible. AI Just Made It Visible.
Chapter 3: The System Is the Work
Chapter 4: The Model Will Change. Build Accordingly.
Chapter 5: Before the Idea Hardens
Chapter 6: Requirements Are Hypotheses
Chapter 7: The Constraint Is Not Where You Think It Is
Chapter 8: Design the Environment, Not the People
Chapter 9: Quote a Probability, Not a Promise
Chapter 10: Assume Nothing
Chapter 11: Make Competence Legible
Chapter 12: The Loop With a Human in It
Closing Bookend: Is It Actually Better?
About the Author
