The Process of Process

Making games is tough, it's a long and grueling cycle of creative input and iteration that hopefully culminates in a successful commercial product. We often get so caught up in the end product, that we forget the significance of the journey it takes to get there. But guess what? The process of making a game is an art form in itself. I recently discover how actual art (paintings) is made. Stupid as I am, thinking art was created by these genius artists on a whim…when in fact the genius is not necessarily just the painting itself but the process of producing it. (Funny enough this was recently voiced by Elon Musk when talking to Joe Rogan about manufacturing and how infinitely harder it is than designing the car)

Feel free to checkout one of the most inspiring YouTube channels, Great Art Explained and the video below about Van Gogh’s journey. 

Now the reason this video specifically stood out to me, is because I realized that Van Gogh’s style of art was in fact a process of developing the necessary tools, confidence, style, technique, knowledge and conditions that allowed for that specific art piece to be produced. Van Gogh spent years creating the exact same style of painting in various forms until reaching the point where we got the end result, “The Starry Night” among others. 

With that being said, the process of making games is an often neglected key part of making games. From forming the team behind the game, to the initial game concept, iteration and finally polish. All of these steps requires rigorous planning, execution and a clear vision of the end product. What is usually sad however is the lack of conversation about the processes we employ to hire people, or how we develop a concept, or how we iterate on design and development etc. 

How things get done is a vital part of production and I can’t help but think that many young and veteran developers pay little to no attention to this. Because ultimately, without a proper process in place, we can be stuck in loops of iteration or creative un-control that can result in a lot of damage and time wasted.

So with all that being said, here are a couple of pointers I think we should take with us when we are starting a new company, game or project.

1. There is a process before the process: Before we start creating a new process, how about we define what the process is to change and iterate on that process? This is probably the most important point here and should be on top of mind in everything we do.

2. Be precise when planning the process: Clearly define the steps and milestones in your process. A well-structured plan should provide a roadmap, which hopefully prevents aimless wandering in your development journey.

3. Transparent communication and getting people onboard: Discuss and document processes and ensure everyone involved understands their role and the overall objectives. If everyone has access to and understands the process, then people can operate under the same framework and contribute to its iteration.

4. Embrace iteration, but with actual purpose: Iteration is essential, but ensure each round serves a specific purpose. Avoid aimless revisions by tying iterations to clear goals and objectives. Also, how do you iterate? Se #1.

5. Learn and evolve from process: Continuously evaluate and learn from your processes. Be open to adaptation, refining your methods based on both successes and failures. But keep in mind, #1.

I hope you found value in this and that you also start thinking about the process of process before starting a new project.