28 May, 2016
The game industry is a strange place sometimes. I was musing about the nature of the industry the other day, thinking about this. Part of my motivation was to think about my own place in the industry, and another part was thinking about my slowly developing book Thinking Like a Game Designer. When I really thought about it, the one term I’d use to describe the game industry, particularly the triple-A side, is “hierarchies”.
Interested in a closer look?
The nature of hierarchies
I’ve seen arguments that people automatically form hierarchies. They point to nature where most mammals have some sort of hierarchy between them, and sometimes fierce battles to establish these hierarchies. They point to history where some people have held dominion over others. They argue that the weak want the protection of the strong, and the strong want to be recognized for their ability to protect others.
Are hierarchies the default mode for humans? I think the more interesting question is if humans can override specific desires, such as the desire for hierarchy, if they want. But, this might be a discussion for another time.
For now, let’s accept that people like hierarchies. They use it as a measurement, to see where they fit in, or to see if they fit in where they feel they should. They use hierarchies to measure others and compare themselves to others. They may be right or they may be wrong, but they exist.
Some people like to think of the game industry as a fun and friendly place. The idea of hierarchies can seem to go against that perception, and in a way it does. The book leadership book I’m reading, It’s Your Ship, talks a lot about how the rigid hierarchy of the U.S. Navy prevented a lot of useful work being done; senior members ignored junior members, even when the junior members had more practical knowledge of an issue.
But, multiple hierarchies exist in the computer game industry. This makes it feel a bit odd and alienating sometimes.
First order hierarchy: your employment
The first way game developers judge each other is by their history, which can be summed up in one question: what kinds of games have you made?
The lowest on this hierarchy are the wannabes. Anyone who thinks they’d like to make a game, but haven’t actually done it yet. Half-finished projects and big talk don’t get you anywhere in this level, you need to have finished a game. That kid who “is going to make WoW, but better”? Yeah, game developers look at him with pity, amusement, or scorn depending on their personality. Occasionally someone will want to help the guy.
The next level on the hierarchy is the amateur. Someone who has made a game, or contributed to a game, on a non-professional basis. This is the absolute lowest rung you have to be on in order to get a job as a professional game developer. You better have a game ready to demonstrate to someone if you want a job as a game developer and don’t have credits on a major game project.
The next step up are the professionals. People who have held a job are at this level. In some ways, this can blur with the previous level if you don’t actually have a credit on a game. Of course, credits and titles are ill-defined in the industry, so having a credit can be tricky; for example, it’s common to not be listed in the credits of an MMO if you aren’t around for launch, even if you worked on the game for multiple years.
So, the last level are the people with professional credits. However, what counts as a “credit” can differ based on the person, which I cover later. Because there’s no standard for credits and for what someone considers a “real game”, you might be considered lower on this hierarchy even if you’ve done more actual work in games than someone who has a credit on some big-name game. The usual check for what counts as a legitimate credit is by checking the person on MobyGames.
Second order hierarchy: your impact
This is really more of a specialization of the “professional credits” level in the history hierarchy. There is a hierarchy of “better” and “worse” games. For a while in the MMO industry, anyone who had their name in the credits of World of Warcraft was a living god. Investors fell over themselves to throw money at former WoW developers who wanted to start their own studio. We’ve seen how that turned out, but the fact remains that WoW was seen as a “great” game to work on.
The lowest are people who have worked on failed projects. Technically, if you’ve only worked on failed projects you wouldn’t have a credit to your name, so you might be relegated to merely “professional”.
Then there are people who work on lesser projects. Someone coding mid-grade (“shovelware”) games or ports might not be seen as really “credited”, but merely a professional. Someone who worked on “serious games” will probably be viewed at this level, as some don’t see “serious games” as games to be taken seriously. This can also apply to people who develop internal code, such as coding libraries used in a larger company. Library coders rarely get their name on the finished product, so again they may be seen as uncredited.
The the next level is for people who worked on obscure games that weren’t sleeper hits. Stuff that had was expected to be a hit but that was a critical and commercial bomb. The games that were hyped up until launch, then seemed to fade away.
Next up are the people who worked on typical games. This includes games that did okay, but that weren’t recognized as instant classics. Or games that were the regularly scheduled sequel to a game that did spectacular initially.
Near the top are people who worked on significant games, such as ones that became surprise hits. This could also include people who worked on historically significant games; for example, early online games such as Habitat. Of course, some people may see those older games as simply “old” and not worthy of respect; they would rank such people lower on the hierarchy.
Finally, at the top are major games. Ones that defined genres or broke sales records. As previously mentioned, World of Warcraft counts here, and anyone who worked on it was seen at a much higher level than others.
Having multiple games also puts you higher in the hierarchy. Long-time Blizzard employees are going to be seen as higher than someone who just shipped the most recent WoW expansion, regardless of quality. Also, not having credits recently will drop you in the hierarchy. This tends to be a bit subjective, of course.
Third order hierarchy: your position title
Another dimension is what position you might hold in a company. Larger companies like to rank people, so you under programming you have junior programmers, senior programmers, distinguished programmers, lead programmers, etc. I won’t go through all the levels, as they tend to be pretty self-explanatory.
Even though you might be tempted to see this as an indication of how long someone has worked in the industry, this is not necessarily the case. One senior programmer might have less than half the years in the industry as another. A “lead” might have less years of experience than a senior.
On the other hand, seniority can play a significant part. Even though a “lead” title might imply some management experience, it’s not unusual to see accomplished people in that position who simply have worked in the industry a long time; sometimes to the detriment of the people under them. Like in other industries, sometimes management is seen as a reward and retention tool to keep good people at companies and give them the control the desire. The better answer is that lead positions should be a way to let people who want to lead the opportunity to actually lead others, ideally with an eye toward letting them grow as developers.
Fourth order hierarchy: your recent history
Games are a hit-driven business, and part of what makes a hit is growth potential. For a long time, the fight was between PCs and consoles. For a while, a new generation of consoles would come along and PC developers were seen as inferior. Then PC tech would advance and console programmers were left behind… until the new generation of consoles.
These days, hits with the most growth potential tend to be in the fresh new fields. Taking online as an example: at one point it was MMOs, then it became social media games, then mobile, and now VR is on the cutting edge. In fact, people who are proficient at older forms are seen as inferior, unable to compete. When social media games were ascending, they looked at MMOs developers as “dinosaurs” who were hopelessly behind the times, even if WoW was still the dominant game. Now someone working as a social media game designer would be seen as backwards, perhaps threatening to be lost to obscurity.
Some developers will make the jump from one stage to another: MMO designers were able to take some lessons to social media games. The simplified interfaces for social media games lent themselves well to mobile interfaces. Mobile design philosophies are being carried forward into VR games. In these cases, being an expert in the previous generation can be seen as an asset, giving you valuable experience.
In other areas, it might be experience with a generation of consoles. A Wii programmer or PS3 programer isn’t going to be as high as a PS4 programmer.
Fifth order hierarchy: within the discipline
I can’t speak as much to art, but programming and design have their own hierarchies, which are individual.
One of the first things a company will do is give you a design test or a programming test to test your competency. Your experience often counts for little when judging your competence in most larger companies, and the skills test has become de rigueur. Even if you pass some pre-screening test, programmers are often expected to do whiteboard programming in a live interview as well to demonstrate their ability.
In programming, your position in the hierarchy depends on how specialized your knowledge is. A console programmer is generally seen as higher than a PC programmer, as console programming is “closer to the metal” to wring out the best possible performance. A generalist programmer is seen as lower on the hierarchy than a specialist programmer, such as a network programmer. In fact, a generalist programmer who is good at network programming is likely just to all themselves a “network programmer”.
And, of course, there is the new technology du jour. Knowing a popular language. like Lua, will count for more than knowing a language like Python that isn’t seen as feasible for developing games. Someone proficient in Unity is seen as higher than someone proficient with Flash, even some years ago before Flash fell sharply out of fashion.
On the design side, the hierarchy tends to be a combination of job title and impact. The owner of the company who takes the mantle of “Lead Designer” is unquestionably at the top of the heap; question his design decisions at your own peril. Between to designers, the one who has worked on the more significant projects tends to be viewed higher and given deference. And, of course, anyone without a “designer” title tends to be viewed as much lower than anyone who is an actual designer when it comes to design. This hierarchy can be very important as it can determine who gets creative ownership, and thus who will feel more fulfilled as a designer.
The special case: indie!
So, most of this deals with the mainstream, triple-A-focused game industry. What about indie? Oh, boy, that might be worth its own post, but let me summarize a bit.
In the olden days, being independent was seen as a joke. I like to snark that I was indie before indie was cool, but it’s really the truth. It was common for people who were unexpectedly let go from their jobs to “start their own company”. So, this was seen as a negative thing, because anyone who was skilled would be able to find a job immediately. And, of course, everyone puts themselves as “CEO” of “My Tiny Game Co.”, so that title became worthless unless you were at a huge company.
At some point in the late 2000s, indie was seen as kinda cool. Indie games started taking the industry by storm, and it wasn’t quite so negative to run your own small company. We saw hits like World of Goo which made respectable money, particularly for people who didn’t have giant corporate overhead sapping income. I’ll still note, however, that most triple-A industry people were slow to see indie developers as “real” developers. Of course, the rise of the indies also gave people the ability to jump away from their soul-sucking corporate jobs and risk their savings and houses on making their own games.
Still, the triple-A game industry tends to be very conservative, and I wouldn’t be surprised to still see people in the industry who view indies as “not having paid their dues” properly. Unless, of course, they’re superstars who have little need to work in the triple-A game industry; few triple-A developers would scorn Notch if he decided he wanted to work at a large company.
Putting it all together
So, we have a multi-dimensional measurement of someone’s capabilities based on multiple hierarchies. How does it work in practice? Let me use myself as an example, although self-evaluation is always hard.
For credits, I do have some credits to my name. Within the second order hierarchy, I’ve worked on a historically significant game, although a relatively minor one. However, I haven’t had a major credit to my name lately, so I get bumped down a bit there.
For title, I’ve been the co-founder of a company but since it was indie before indie was cool, that experience is seen as suspect. My 18 years in the industry would generally me at about a Senior or Lead position, depending on the team structure and size; one reason I’m interested in leadership is because I don’t want to stumble into a lead position without any ability to lead.
As for my recent history… well, I’m an MMO developer. As I said, that’s about four generations out of date right now. I’m definitely at the bottom of the heap here. Within programming, I tend to be lower on the heap as well, as I’m very much a generalist. My background as the primary programmer on Meridian 59 didn’t let me specialize, and my work as a consultant/contractor meant I did whatever was necessary at the time, even if that’s programming tools in MFC at one place. (Talk about truly outdated skills!) In design, it really depends. I’ve been Lead Designer on a few projects, but they never shipped. Since my background is mostly technical, designers look at me with suspicion; luckily “Technical Designers” are becoming a thing, which is probably the role I’m best suited for with my experience; since that’s new, I’m not sure how the hierarchy is set up yet for that discipline.
And, of course, I’ve been indie so that makes things extra weird. I don’t think many people put much stock in my experience with Near Death Studios since it wasn’t a runaway success despite surviving for nearly nine years. The other thing that doesn’t quite fit into standard measurements is my book on business and legal issues; since I didn’t write a chapter, though, I don’t think people appreciate the deep knowledge required to organize and edit the book. And, I could go on at more length about how reputation factors into this whole mess, but I won’t for now.
Anyway, hopefully this little glimpse into the game industry has been interesting. I didn’t expect this to get quite so long, but there’s a lot to this topic, I guess. Ask questions or leave your own thoughts in the comments below; I’m curious to see how other people think.