PGC 2020 Sessions @ PGC LONDON - Chris Kempt
summary
Building games depends on constant audit belief: stop projects that lack conviction and change direction early. Prioritize skills over tools and treat documentation as a one A4 summary plus face-to-face updates; meetings must open with objectives and close with recorded outcomes. Use T-shaped team members, enable people with clear boundaries, under-promise to avoid crunch, let ideas ferment then distill, prefer steady evolution with planned peaks, assign clear product or feature ownership and learn basic spreadsheets like pivot tables.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:10set clear objectives at the start of a meeting
- 3:54set clear boundaries
- 4:30mix the ingredients
related talks
18mGram Games on iterating your development pipeline as you grow
52mBuilding Game Studios that Last
52mGame Production: Helping your team succeed
59mSustainable Game Development from a Game Producer's Perspective
29mDriving clarity in ambiguous projects
22mHow to create agile teams and foster the culture of excellence while developing games
45mBetter ways of running your studio 2024
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success