Fireside chat: Team Civilization VII
summary
Development for Civilization VII centers on an explicit decision to restructure time into an ages system that forces design tradeoffs, requiring art and civ content to be produced per age so the team reports content tripled for that scope. Production treats roadmaps as facilitated consensus, leaning on full‑time historians and community/local partners (example: collaboration with the Shawnee and a native speaker) to vet leaders. The game ships day‑and‑date on consoles and PC with multi‑platform cross‑save/cross‑play, and iterative playtests drive which systemic ideas survive.
AI-written summary · about
chapters (24)
- 0:00Welcome
- 1:30Andrew Frederickson’s role
- 3:58New game systems
- 6:05Team experience
- 8:54Work-life balance
- 10:21Iterative design
- 13:32Ages system
- 15:40Ages reactions
- 17:26Civilizations selection
- 19:57Historical accuracy
- 22:45Multi-platform release
- 24:51Day-one decisions
- 26:15Team size
- 27:40Producer roles
- 31:13Proud achievements
- 33:20Passion for working on Civilization at Firaxis
- 36:32Q&A: Cloud saves
- 39:29Q&A: Roadmap decisions
- 40:53Q&A: Teaching players
- 43:00Q&A: Player agency
- 45:50Q&A: Min-maxing balance
- 47:13Q&A: Community growth
- 48:58Q&A: Founders Pack
- 51:46Q&A: Game pricing
related talks
17mFireside Chat: Best Practices in Developing Games
18mlive services game design with SimCity BuildIt
39mThe Inception of a Historical Strategy Game
01h 05mFireside Chat with Jakub Dvorský
18mFireside chat: Brands and indies
20mClimate Crisis and Video Games
19mHow premium games can succeed
51mBuilding Better Worlds through Game Culturalization