An interview about Pragmata got me thinking about the line between a director's vision and the team's work. The director described starting with a broad concept, while the designers worked through how to make it playable. How should we think about credit in situations like that?
How much credit should a game director get for a team's ideas?
Answers
Both contributions matter, but they aren't the same contribution. Setting a direction gives the team something to work toward. Finding a mechanic that actually makes that direction fun is design work in its own right.
In the interview, the director described wanting simultaneous shooting and a second activity. The designers arrived at puzzles through trial and error, and the director approved the choice. That's a much more useful account than treating the finished idea as one person's invention.
Reply to this answer
Credit isn't just about who had the first idea. A director can contribute by making decisions, keeping a project focused and giving people room to test things. Saying the team did the detailed design doesn't erase that role.
Still, a good leader should be specific about what others contributed instead of accepting all the praise as the public face of the game.
Reply to this answer
Public praise is nice, but I'd also look at how a team handles disagreement and experimentation. Can designers raise problems with an idea? Do they get room to try alternatives? Those things affect whether a collaborative culture exists beyond an interview.
The account here tells us something about how this mechanic was developed, but it doesn't tell us everything about the studio's working culture.
GBAcartWedge:
That makes sense. Giving credit publicly is a good sign, but it doesn't tell us on its own how the whole team works.
Reply to this answer
Honestly, the interesting part is the gap between an idea and a playable system. Having two characters do different things at once sounds promising, but figuring out what the player actually does with that is a whole other problem.
Trial and error is real creative work, even when the final result looks obvious.
Reply to this answer
Add your answer
Answers are reviewed before publication.
stunGauge.Pocketwatch:
That distinction also helps explain why a pitch can sound simple after the hard design problems have been solved.