I’m a bit late to the party here, but I just read the Eating Bees post about game companies that fail, and the people that cover for them. Her conclusion seems to be that it’s usually easy to find out who’s to blame, but I don’t think that’s true.
There are lots of times when games fail through no direct fault of any immediate employee. In MMO’s in particular, the blame game is infinitely more complex. A typical MMORPG is developed by a team of 50-100 people, many of whom then promptly leave the company. They are replaced by other folks who actually run the game from day to day. It’s these folks, the live team, who have to clean up the messes, take the blame for any poor designs, and work their butts off to keep the game running. Sometimes it is fair to say that the live team ruined the game, but that’s hardly the common case.
In an industry with high turnover rates like ours, it’s not usually very useful to blame individual employees for a games’ failure. There are exceptions, but it’s not the rule. Fortunately, most of the game industry understands this, and a failed game is not usually a mark against somebody. (Unless they have only a very long string of failures to their name.)
Even the cases we think we understand aren’t likely to be as obvious as they look. A very well-known MMO completely revamped its entire gameplay long after the game had shipped, and they’ve suffered fallout as a result. It would be easy to guess at the logic behind this, but if you go by just the visible facts, your guess would be completely wrong.
Of course, since money is involved in making games, the buck has to stop somewhere, and it stops with the company. At a very practical level, it’s the company’s mess. They’re the ones who took a risk on making the game, and their risk didn’t pan out for one reason or another, so the company may go bankrupt as a result. But that doesn’t tell us why a game failed, or whose fault it was. Without knowing all the details, we are very likely to reach the wrong conclusion.