Before reading any further, watch this video. It’s roughly fifteen minutes, and worth every second. I’ll wait.
Rob Pardo shared this video at a recent team event at Blizzard. Like many TED videos, I really enjoyed this presentation, and it struck me as highly relevant to the gaming industry.
At a number of studios and across a variety of projects, I’ve repeatedly heard the question, “What are we making?” In fact, I’ve asked the question a fair number of times myself. After watching Mr. Sinek’s presentation, I am struck at how much more engaging a question “Why?” is over “What?”.
I am confident that most development studios know what they are making – even when most of us are flailing our arms trying to figure it out. I am significantly less confident that most studios (publishers and developers alike) know why they make their games. As Mr. Sinek says, “to make money” is an insufficient answer. For us, the money is the “connecting point” that permits the end of one cycle to connect to the next, thereby allowing the employees to continue to do what they love (whether it be game development or accounting).
Beyond the products we make (collective “we”), answering the why question in our industry requires a serious level of introspection. Having watched this video, I find myself convinced that the success of our top studios, and by association their products, is hinged on the organization’s ability to understand why. They can appreciate the composition of their teams, their values and their unique identity. As a result, they select the types of products that best leverage their talent, their experience, their unique identity and their limitations.
Here is a starter list of questions that I quickly assembled:
- What does your team value? And don’t give vague platitudes like “commitment” or “passion.” What does your team truly value? Technical expertise? Quick-and-dirty rapid prototyping? Artistic vision? Actually, you don’t have to answer this, just look at your staff (their talents, their expertise). The problem is solved bottom-up.
- Who do you hire? Largely, this answers the same question as the first. However, you need to make sure that why you’re doing (top-down) matches the previous question’s (bottom-up).
- How do you make your games? Process-driven? Agile and experimental?
- Very Important: What games have you made already? Regardless of the financial and/or critical success, games are developed for a reason. Why? Why did you make that game? The financial results will undoubtedly impact the next game you make, but should that be the prime deciding factor? If it is, then aren’t we saying our why is “to make money”?
- Why are you there? Are you there for the project? Projects end. Or are you there for the organization? What does the organization represent to you? That alone is a pretty big why.
These are all interesting and important questions. Candidly, I feel that being able to clearly answer them will give you far stronger forecasting ability than any form of “market research” or “end user analysis.” There will always be plenty of data that encourages studios to make Game A or Game B. All I’m suggesting is that the most significant data point comes from within the organization, not without.
Don’t tell me what your next game will be.
Tell me about why you’re next game will be.
