All Aboard: Tools and Tactics for Building Team Consensus.
summary
Concrete methods for getting teams aligned: use a kickoff to set 3–5 design pillars, run short brainstorms with 2–8 people, capture results in simple docs or Google Slides and consolidate alone, then gather feedback via one-on-ones and a defined feedback cycle. Prototype the riskiest bits, playtest for actionable data, run fortnightly retrospectives, and treat big client pivots as trade-offs or change orders. Advice scales from pod leads (18–20 people threshold) to directors and focuses on measurable decisions not vague platitudes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:07Shared vision in game dev
- 5:13Creating the concept
- 12:33Pod lead duties
- 17:51Brainstorming for consensus
- 24:09Gathering feedback
- 28:22Pre-production best practices
- 33:33Managing up and across
- 36:42Entering production
- 40:09Late-project issues
- 42:53Summary
- 43:35Q&A
related talks
24mOperationalizing Design from the Ground Up
58mLet's Work Together!
01h 20mWorkshop - Teamwork Ain't Always Easy
01h 18mLeading teams to collaborate-when they really don't want to.
39mUsing Agile Techniques to Build a More Inclusive Team
29mDriving clarity in ambiguous projects
28mOne Team, One Dream? Gaining Cross-Functional Buy-in
32mBuild Teams as an Engineer