Without Vision, you'd be blind
summary
Argues that a clear project identity—condensed into one-sentence vision and a physical memento—steers every design choice: choose tank controls when slowness creates vulnerability (classic Resident Evil) and standard controls when responsiveness serves action, use Kinect body-based mechanics as in Through (Xbox One) only if they reinforce the intended feeling, and keep reference artifacts (Naughty Dog-style boards, Last of Us live-action pitch) to resolve disputes. Advocates rapid playtests, short per-feature docs instead of huge GDDs, and designing to theme feeling aesthetics rather than generic “better” features.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:04Feature choices and game design
- 7:39Rethinking game features
- 10:39Defining vision for games
- 13:07Components of vision
- 19:26Challenges in maintaining vision
- 25:02Communicating vision effectively
- 28:13Overcoming fear in development
- 31:27Conclusion and Q&A
related talks
23mThe vitality of visual storytelling in games
32mDesigning with Heart and Head
38mThe ever-changing role of a Creative Director
53mDelivering Their Vision
01h 06mDreams of Electric Sheep - Aspirations for the Future of Game AI
28mUnseen: How Non-gamer Input can Change & Improve Art & Storytelling in Games
50mA Tale of Inspiration, Empathy & Totalitarian Powers
19mWhat do movie directors, motorcyclists and historians know about making games?