Coordinators are the harbingers of red tape and re-prioritization, a bureaucratic middle man that can be respected, but never entirely liked. And that’s exactly where you need to be.
Also known as an Associate Producer in teams that can afford such titles, a Coordinator’s lot in production is one of constant readjusting. The proud owner and operator of the master schedule, every week brings subtle transformations to your perfectly planned testing passes and animation blocking schedules. Game development is a process of constantly revising your prospects, as a thousand little variables are always in flux: Unity crashes and stubborn shoulder rigs, re-exports and complex renders. Add the fact that your entire team is satellite and around the world, and it makes the film production background you come seem like the most refreshing of breezes.
Luckily then, the day job of the Production Coordinator is to be everywhere at all times, or as close to it as humanly possible. One of the earliest things I learned is to remove the sound of Skype pings, my first few hours on staff was riddled with tiny chirps from a dozen conversations. You have an ear in every department during office hours, ready to rush in to solve any number of daily problems that can arise.
In between arranging and hosting all manners of department meetings and dailies (where everyone shows off their days work for their respective leads), you can be called upon to help get a recently approved prop into a character model’s hand or confirming a logic editor has the latest 3D layout of the scene he’s working on. It’s being on call on a phone line that’s always ringing. Given that we have departments in Italy and India, it also means daily midnight conferences on modeling procedures and approval processes.
Redmine: "From up here, you all look like little, compulsively organized ants."
Once (or if) you manage to quiet all immediate concerns for a moment, you shift from the microscopic back to the macroscopic. And at my position, that means going from firefighting to data entry. We at Phoenix Online use the SCRUM style of scheduling on a milestone delivery schedule – for at least one of our projects – all of which means a lot of organizing and updating spreadsheets and scheduling software documents. While each staff member sees their individual priorities in a shared “To Do List” Google doc, I primarily employ Hansoft for the grander plan. To my eyes, a game looks like a massive array of nodes and interconnected lines long before it takes manifests into something playable.
Once we establish a foundation of logic and everyone has a foothold in their department, minute bugs and polish assignments can be tracked using Redmine, a program which helps store and prioritize everything from a character with a spinning chest to a background that needs final shading. An average game project can run anywhere from 600 to a couple thousand of these little tasks, all of which come through your inbox at each stage of being fixed.
It’s certainly a mountainous amount of information to take in and process, be it day 1 or 1,000. But all Coordinators (or Associate Producers) learn fast on their feet, and I was impressed just how quickly I was employing a unique bag of tricks. Despite my intimidating introduction, my greatest asset is my team. If you have a wonderful assortment of people, your job becomes a whole lot smoother (if not less complex). The staff at Phoenix Online – my little schedule nodes – are a wonderful, truly dedicated bunch, with their own little brand of insanity that I’m proud to be contributing to.
Social Media Intern, Phoenix Online
(Also, everyone, remember to like our Facebook Page and check out our twitter :) )view gallery