Abstract
Problem: Why do some game development leaders fail to make good decisions during the prototype phase — and should that disqualify them from leadership?
Approach: Tim Cain draws on decades of experience (including The Outer Worlds) and an analogy to music production to illustrate why the ability to "see through" a rough prototype is a critical leadership skill.
Findings: Many people in decision-making roles cannot look past placeholder art and grey-boxed environments to evaluate the underlying mechanics and game feel. This makes them a "speed bump" on the road to making a good game. The ability to envision a finished product from raw ingredients is a litmus test for whether someone should be a game director.
Key insight: If you can't look at a grey-boxed prototype and imagine the final game, game development leadership is probably not for you.
What Is a Prototype?
A prototype is the phase where you implement all foundational features: walking, climbing, basic dialogue, and any unique core mechanic your game relies on. It also lets level designers lay down maps to test size, flow, and spatial arrangement.
What a prototype is not: it's not about art, lighting, or polished UI. Those exist only at the barest level of functionality — just enough to let you test the things that matter.
Why You Make One
A prototype exists purely to test your ideas — to see if you should proceed with them and how you should proceed. No one's idea springs perfectly formed from their brain requiring zero changes. This is the phase where you validate or kill concepts before committing massive resources.
The Problem: People Who Can't See Past the Grey Box
Throughout his career, Tim noticed that some people are completely incapable of making use of a prototype. They cannot look past the grey-boxed buildings, the T-posed characters, and the placeholder props to see the actual game underneath.
This is fine if you're not making important decisions. But by the time you reach lead level — and certainly at game director level and above — you must be able to look at a prototype and imagine the finished game well enough to make critical calls.
The Feedback Tim Actually Received
Tim recounts getting feedback on prototypes like:
- "This was awful"
- "No one would play something like this"
- "This is amateur hour"
He describes having to go into someone's office and explain: "Do you understand what that was? I was trying to show you how a mechanic would work. I don't care what the animation was. We had two different meetings in there — everyone else was judging mechanics from a prototype, and you were there thinking we were showing you a beautiful corner."
The Music Analogy
To explain this to non-game-dev friends, Tim drew a parallel to the music industry. When someone is working on a song and they've written the lyrics with a rough musical riff, there must be production people and managers who are supposed to greenlight songs — yet cannot tell from lyrics and a riff whether a song will be good.
The Lyrics Test
Tim demonstrates by reading lyrics stripped of music:
Number one song of 1987 — "The blonde waitresses take their trays, they spin around and they cross the floor. They've got moves. You drop your drink and they bring you more." That's "Walk Like an Egyptian" by The Bangles.
Number one song of 2025 — "Wherever you go, that's where I'll follow. Nobody's promised tomorrow. So I'm gonna love you every night like it's the last night." That's "Die With a Smile" by Bruno Mars and Lady Gaga.
His point: most people can't read bare lyrics and identify a hit song. That's not a character flaw — but if you can't do it, you probably shouldn't be making high-level decisions in music production. The same principle applies to game prototypes.
The Litmus Test for Game Directors
Tim frames this ability as a genuine litmus test for game direction:
- If you can look at a grey-boxed prototype and envision the final game → you have the foundational skill for game direction.
- If you cannot → you are "nothing but a speed bump on the road to making a good game."
He's seen this pattern repeatedly: games that hit massive speed bumps during prototyping because decision-makers couldn't see past the placeholder visuals, then those same people suddenly sounded "incredibly visionary" after the game shipped with polished art.
The Art Flip
Tim describes a common pattern among developer friends: they demonstrate a great mechanic in prototype form and get shut down. Then the exact same mechanic gets polished art — the character moves smoothly, the props are pretty — and suddenly everybody loves it. The mechanic didn't change. Only the visuals did. The people who couldn't evaluate it during prototype shouldn't have been the gatekeepers.
Takeaway
The ability to see the game in the prototype is not optional for leadership. It's a core competency. People who lack it and hold decision-making power create unnecessary friction and can kill good ideas before they have a chance to mature. Tim's advice: if you're considering a career in game direction, ask yourself honestly — can you look at a rough prototype and imagine the finished product? If not, there might be a better role for you elsewhere in the pipeline.
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=SwYr0vRyOtk